3 ms·
There are some basic things broken in the graphics engine: 1) Turning vsync "on" doesn't have the intended effect. There's still very visible tearing half way
by jiggawatts 4y ago
There are some basic things broken in the graphics engine:
1) Turning vsync "on" doesn't have the intended effect. There's still very visible tearing half way down the screen.
2) Turning vsync on in combination with full-screen mode results in a hideous stuttering when turning the viewport with the mouse. It looks like you got the swap chain sequence.. backwards? As in... swapping the "most recent" frame.. and then an older frame!? Or something like that. It's literally stuttering back-and-forth making my eyes bleed. It is also inconsistent: switching in and out of borderless windowed mode changes the behaviour.
3) The GUI scale setting is weird by default (140%!?), and is ignored for some UI elements. Do you test with 4K monitors?
4) Lots of GUI glitches. E.g.: clicking the tabs in the settings window will make it disappear for a moment and reappear.
5) The game continues to use 100% GPU even when I alt-tab out to the desktop
6) I have a 60 Hz monitor. The game generates more GPU load (75% vs 60%) with vsync enabled than if I use the "limit to 60 fps" mode, which confirms that the vsync setting is doing something very wrong. These two modes should produce identical GPU load.
7) Hovering the cursor over some in-game UI elements causes alternating-frame flicker. E.g. the "Right click & drag to remove existing designations" orange mouse icon thing.
As a former game engine developer, my advice is that with both DirectX and OpenGL there is generally only "one right way" to do certain things such as managing a swap chain. Yet, somehow, game developers manage to get this consistently wrong and never seem to test/fix it.
Test, test, test! Plug in multiple monitors. With different resolutions. Drag your game around between them. Try laptops with hybrid (NVIDIA+Intel) GPUs. Use a HDR monitor. Use one of those laptops with a hybrid card and unplug the power while your game is running. Plug the power back in. Change your desktop resolution while your game is running. Try to get 10-bit working. Try to get the game to look identical even on wide-gamut monitors. Etc...
Iron out these bugs through acid tests. You will never notice real bugs otherwise, because it's too easy to get stuck in some "happy path" rut, such as testing with a single 1080p monitor.
Non-graphics related feedback:
"Unsaved progress will be lost!"
"What year is this!? Am I stuck in 1990 again?"
- BlueTemplar 4y agoWhat games even do continuous saving ?? Otherwise I've noticed annoying flickering of far away molten metal, but that was on a Twitch stream, which might be the cause ?
- jiggawatts 4y agoNo need to do continuous saving. Just have "exit" also save the game state at the same time.
- kbelder 4y agoNo, better to give the choice to "exit" or "save and exit".
- animal531 4y ago>"As a former game engine developer, my advice is that with both DirectX and OpenGL there is generally only "one right way" to do certain things such as managing a swap chain. Yet, somehow, game developers manage to get this consistently wrong and never seem to test/fix it. >Test, test, test! Plug in multiple monitors. With different resolutions. Drag your game around between them. Try laptops with hybrid (NVIDIA+Intel) GPUs. Use a HDR monitor. Use one of those laptops with a hybrid card and unplug the power while your game is running. Plug the power back in. Change your desktop resolution while your game is running. Try to get 10-bit working. Try to get the game to look identical even on wide-gamut monitors. Etc..." Some good feedback, but remember they're using Unity, so they're not directly controlling anything on a low level. As for the 2nd part, this is really hard in a small team. For example I'm a solo dev, so I only have access to 2 monitors, 2 graphics cards etc. BUT there are paid for services that provide testing, although that costs money; so when they've made a bit of cash and have a bigger user base then they can probably afford those.
- jiggawatts 4y agoI’ve played three Unity games recently and one had working vsync and two (including this one) didn’t. I suspect that there’s some trick to making it work properly that’s poorly documented. That, or the “get started with Unity” sample gets it wrong and everyone just blindly copies it.