[1.0.1.8] CTD - Zoom in

[actrade]

Be happy to...if that patch was posted lol. It's not on the matrix website and I get an error when trying to update via the program.

EDIT: just got it, it finally came up on this site.

[Nilma]

In 1.0.2.4 I'm still getting CTD with lens flare on and an increased zoom speed (it doesn't seem to happen when lens flare is set to zero and the zoom speed set to 1), no crash dump file is created but event viewer shows two "errors":

EDIT: It seems to happen in either scenario now, always when zooming into a system.

.NET Runtime error:
Application: DistantWorlds2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFE09A8981A

Then an application error:
Faulting application name: DistantWorlds2.exe, version: 1.0.2.4, time stamp: 0xb6d3ffb5
Faulting module name: nvwgf2umx.dll, version: 30.0.15.1179, time stamp: 0x620471aa
Exception code: 0xc0000005
Fault offset: 0x000000000007981a
Faulting process ID: 0x3ec
Faulting application start time: 0x01d83f2f82b2e2a7
Faulting application path: C:\Games\DW2\DistantWorlds2.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nvaci.inf_amd64_50ffce48b1e8519d\nvwgf2umx.dll
Report ID: e7a64025-ace9-47a5-9780-de96af5f1852
Faulting package full name:
Faulting package-relative application ID:

[Nilma]

I think I may have fixed my issue... I've played a couple of sessions with everything such as lens flare turned on and had no issues what so ever.

I noticed that whilst Distant Worlds 2 was running, Desktop Window Manager was using a lot of resources including my onboard Intel GPU. The Intel GPU is obviously not good and doesn't support dynamic range rendering for instance and it seems DWM is running some of the processes in the background for DW2. Whilst trying to force DWM to use my NVIDA GPU (it won't by the way, there are complaints going back years about it) I discovered that Windows has been lying to me about the status of the drivers on my Intel GPU! I'd not thought that the Intel GPU was important for DW2 so I'd used Device Manager which told me that the drivers were up to date, however there is a much newer version on the Intel website which I installed, and since then I've had no issues at all.

I wasn't aware that the Intel GPU was being used for DW2 but clearly DWM has been using it to run some of the processes. It's not possible to stop DWM from using an integrated GPU so if someone is using a platform with multiple GPUs they need to make sure they get the latest drivers directly from the manufacturer for all GPUs!

I feel like an idiot for not noticing that the driver on the Intel GPU was so out of date, but it's resolved now (or at least I think it is!), I hope this helps other people too.

[firemad]

I think I may have fixed my issue... I've played a couple of sessions with everything such as lens flare turned on and had no issues what so ever.

I noticed that whilst Distant Worlds 2 was running, Desktop Window Manager was using a lot of resources including my onboard Intel GPU. The Intel GPU is obviously not good and doesn't support dynamic range rendering for instance and it seems DWM is running some of the processes in the background for DW2. Whilst trying to force DWM to use my NVIDA GPU (it won't by the way, there are complaints going back years about it) I discovered that Windows has been lying to me about the status of the drivers on my Intel GPU! I'd not thought that the Intel GPU was important for DW2 so I'd used Device Manager which told me that the drivers were up to date, however there is a much newer version on the Intel website which I installed, and since then I've had no issues at all.

I wasn't aware that the Intel GPU was being used for DW2 but clearly DWM has been using it to run some of the processes. It's not possible to stop DWM from using an integrated GPU so if someone is using a platform with multiple GPUs they need to make sure they get the latest drivers directly from the manufacturer for all GPUs!

I feel like an idiot for not noticing that the driver on the Intel GPU was so out of date, but it's resolved now (or at least I think it is!), I hope this helps other people too.

Very good find but it isn't normal for a game to use the integrated graphic cards instead of the primary specified. Dev need to investigate it.

[Erik Rutins]

I think I may have fixed my issue... I've played a couple of sessions with everything such as lens flare turned on and had no issues what so ever.

I noticed that whilst Distant Worlds 2 was running, Desktop Window Manager was using a lot of resources including my onboard Intel GPU. The Intel GPU is obviously not good and doesn't support dynamic range rendering for instance and it seems DWM is running some of the processes in the background for DW2. Whilst trying to force DWM to use my NVIDA GPU (it won't by the way, there are complaints going back years about it) I discovered that Windows has been lying to me about the status of the drivers on my Intel GPU! I'd not thought that the Intel GPU was important for DW2 so I'd used Device Manager which told me that the drivers were up to date, however there is a much newer version on the Intel website which I installed, and since then I've had no issues at all.

I wasn't aware that the Intel GPU was being used for DW2 but clearly DWM has been using it to run some of the processes. It's not possible to stop DWM from using an integrated GPU so if someone is using a platform with multiple GPUs they need to make sure they get the latest drivers directly from the manufacturer for all GPUs!

I feel like an idiot for not noticing that the driver on the Intel GPU was so out of date, but it's resolved now (or at least I think it is!), I hope this helps other people too.

I'm glad things are working for you. What you describe is one of the problems we've been trying to solve on dual GPU systems. This can also cause poor performance at times.

If you are willing to try an experimental build, I'd like to see if it fixes the issue on your system of DW2 using the integrated GPU some of the time. Please e-mail me at erikr@matrixgames.com and I'll share it with you and send some instructions.

Regards,

- Erik

[Erik Rutins]

Please try the new 1.0.6.2 beta update, especially this new game setting which we think may resolve the remaining crashes, especially battle crashes:

IMPORTANT NOTE: If you still experience crashes with 1.0.6.2 or later, especially crashes in battle, please try the new DXVK rendering option in the game settings. This can be found under "Rendering Mode", which can be switched from DirectX 11 to DXVK. This will likely resolve many issues caused by driver bugs or incompatibilities. If you try this setting and the game does not launch, please note the command line option in the changes below to switch back to DirectX 11.