Troubleshooting: Difference between revisions

From ΔV: Wiki
m (Typos)
(Added workaround information for crashes on M1 Mac systems)
Line 17: Line 17:
*Rarely, on some system configurations, Bloom causes huge performance loss.
*Rarely, on some system configurations, Bloom causes huge performance loss.
*Some users reported that disabling Steam Overlay improves performance a lot for them.
*Some users reported that disabling Steam Overlay improves performance a lot for them.
*On some Mac M1 systems, game will crash when you attempt to switch full-screen mode or resize a window. This is an engine bug that developers have filed against the Godot Engine and are awaiting fix; however, there is a workaround available. Adding --render-thread safe to the game launch options (command line options) will cause it to not use multi-threading and fix the crashes, but will degrade the performance, as rendering will not be using all the available CPU cores anymore.

Revision as of 08:47, 7 September 2023

There are a couple of things that we know can crash Delta V, which aren't in our reach:

  • Please make sure your system meets the minimum hardware requirements for the game.
  • At the top of the list, of course, are outdated drivers. Often a bug report circles around to outdated drivers, so check your drivers first, particularly video drivers. When running AMD cards, ensure that you have at least driver version 22.7.1 which contain significant performance enhancements.
  • AMD Software: PRO Edition drivers have been reported to perform much worse than AMD Software: Adrenalin Edition. Players reported performance improvements from 10-15 fps to 60fps after changing the driver flavour.
  • Some AMD cards can't handle OpenGL if the video is tunneled through integrated GPU. If you can't launch the game at all with a "unsupported driver" message, check if your monitor is plugged in directly into your GPU.
  • Corrupted Windows files. Try to verify your system for corrupted files using the Windows System File Checker tool.
  • The Godot engine just doesn't like controllers that have over 22 buttons. You may have to disconnect a HOTAS or similar controller. Please verify that your system no longer detects the controller.
  • Some users have reported crashes while using OSD software. We have specific reports of crashes that are resolved when turning off "Riva Statistics Server" or disabling OSD components of ASUS's "GPU Tweak 2".
  • Nahimic OSD service is known to cause crashes when enabled.
  • NVIDIA Control Panel can be set up to override any setting the game makes and, in the case of dV and a few other games, freezes the display. Go to your NVIDIA Control Panel and in "Manage 3D settings" set "Let the 3D application decide".
  • The NVIDIA Control Panel setting for vertical sync is known to cause random crashes, it should also be set to "Let the application decide".
  • Using GSync, FreeSync or similar variable refresh rate monitor will have unexpected effects with VSync option turned on, as the game will struggle to understand what is the actual refresh rate of your monitor. Disable VSync and use frame rate limit option instead.
  • GSync and FreeSync are reported to cause the game to flash occasionally on some configurations. If you are experiencing game flashing darkened frames or static, try disabling them for this game.
  • Running Razer Cortex software in background was reported to cause worse performance.
  • If your audio is distorted (ticking at game launch and on dive, opening cinematic sounds like a bad voice changer), check your device (not game) audio output selection. The game could be trying to push audio through a channel designed for voice communication only.
  • Rarely, on some system configurations, Bloom causes huge performance loss.
  • Some users reported that disabling Steam Overlay improves performance a lot for them.
  • On some Mac M1 systems, game will crash when you attempt to switch full-screen mode or resize a window. This is an engine bug that developers have filed against the Godot Engine and are awaiting fix; however, there is a workaround available. Adding --render-thread safe to the game launch options (command line options) will cause it to not use multi-threading and fix the crashes, but will degrade the performance, as rendering will not be using all the available CPU cores anymore.