|
|
|
|
|
by actionfromafar
1163 days ago
|
|
Every real-time game ever defies these arguments. It sounds reasonable until you load a game and start using it. Effectively no lag, counted in the milliseconds. No, the reason that UIs are slow are because they are often a web browser, running a Javascript bloatware UI with it's shadow DOM or whatever, and there's a heaps of bullshit going on before anything happens on screen at all. And this is fine! For many use-cases, comparatively beefy PCs, web pages etc. But for what is effectively an embedded product which will get updated seldom if ever, THIS is the time to take a step and rethink what you are doing. For a non-smart TV you definitely don't need Linux, (but you could!) and you don't need to care if it's realtime or not. There should be only one or two processes running anyway, so there shouldn't be any competition between different threads. It's should all be coded like a classic, tight game-loop. AI upscaling and Android... dear lord. Just give me something which isn't fucking slow and frustrating to use. I thought I was in the thread which discussed non-smart TVs, did I miss something? |
|