| >complete lack of visual feedback you've actually launched FS... It's at least 30 seconds on a fast SSD Eh, splash screen wouldn't hurt but I'm surprised that anybody is strongly bothered by that. Maybe even it is caused by some DRM-silliness. >One major issue is that sitting in the menu seems to use 100% GPU. Without vsync? I guess its shifts from being more GPU-bound to more CPU-bound when running simulation proper, thus changing load percentages. >Turning on vsync tanks frame rate by about 6 or 7 fps for me. "Popping out" a navigation window and putting it onto my second screen also causes around a 4 to 6 FPS drop. Vsync delays game loop to next screen refresh, so excluding these newfangled Freesync/Gsync monitors framerate reduction is expected. Also managing multiple windows/contexts from single applications is quite inconvinient, might clash with system compositor, etc, so I wouldn't hold that against them. Note that I didn't actually play the game and cannot comment on game performance itself. Certainly omission of DX12/Vulkan rendering backend is rather disappointing. |
Yes, without vsync, idling in the main menu uses 100% GPU in task manager. GPU fan confirms this. Clearly a bug, as nothing in the menu looks to me to tax the GPU in even the slightest.
> Vsync delays game loop to next screen refresh, so excluding these newfangled Freesync/Gsync monitors framerate reduction is expected.
Interesting - my setup has freesync screens and GPU, although admittedly I'm not too sure about any of these newfangled display things. I have 2 displayed enabled, tomorrow I'll try it with just 1 display in case that helps.
And absolutely agreed, lack of DX12/Vulkan is a real shame and missed opportunity.
Regards lack of splash screen, perhaps I'm getting old, but this is a regression from older versions - FSX took a while to load but had a progress bar. If I had to ship a game in this state, I'd quickly write a shim executable to show a loading bar immediately. There's an exe that loads it (without startup intro videos) in the SDK, so clearly possible.
I guess maybe my expectations are out of line with the modern "release broken, patch often" mindset, but it seems disappointing they didn't optimise for multi core CPU, or handle regressions in basic UX, or do performance optimisation. But nonetheless, there's clearly some great work in this sim, and hopefully they'll have the confidence to try address some of these issues in patches - perhaps even moving to Vulkan or DX12. Nothing is impossible in a world where the entire game is downloaded and updatable, I guess.