2.1.1 Bad VR Performance and Crashes

[dburne]

Installed 2.1.1 this morning.

 

Gamma slider very nice, a big help especially for VR!

 

Performance - for me in VR, way worse than 2.1.0. I can barely even hit 30 fps over Normandy, previously I was at least maintaining 45 fps for the most part over Normandy. Over water, previously I would maintain 90 fps, now only 45 fps over water. 30 FPS in VR will not work for me.

 

Crashes - Tried 4 flights, Instant Action Spit takeoff mission twice, and a Spit takeoff mission twice I had created ( modified from original to get rid of fog). Have yet to exit any mission cleanly, each time I click on exit from the mission screen, it freezes up and get a DCS.exe has stopped responding error message. Click OK to close the program then at desktop.

 

All logs attached.

DCS.openalpha-Crash-20170621-114538.zip

Edited June 21, 2017 by dburne

[OnlyforDCS]

dburne did you check whether some graphics settings were reset with the patch? With the GUI changes maybe some settings even got changed without being updated in the new GUI?

[dburne]

dburne did you check whether some graphics settings were reset with the patch? With the GUI changes maybe some settings even got changed without being updated in the new GUI?

 

Yes, none of them were reset, and they were already set pretty darn lean to where I could fly in 2.1.0 reasonably ( 45 fps).

The only change was of course the new gamma slider, which I lowered to 1.3 ( it was set to 2.1) to get rid of the brightness on Normandy with deferred shading on - which was a very nice addition.

[BIGNEWY]

00291.975 INFO EDCORE: # -------------- 20170621-114538 --------------

00291.977 INFO EDCORE: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvwgf2umx.dll

00291.978 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 95A1A1EC 00:00000000

00292.082 INFO EDCORE: Minidump created.

00292.085 INFO EDCORE: try to write track file

 

 

Have you tried a clean install of your display driver?

 

use a tool like DDU cleaner and do a fresh install of the latest driver.

 

see if it helps

[lemoen]

They may have tweaked what the different settings mean again. Also, did you clear your shader cache?

[dburne]

Have you tried a clean install of your display driver?

 

use a tool like DDU cleaner and do a fresh install of the latest driver.

 

see if it helps

 

I will give that a try and report back later today.

Odd that it would only start happening after updating to 2.1.1 though...

Edited June 21, 2017 by dburne

[badaboom]

They may have tweaked what the different settings mean again. Also, did you clear your shader cache?

 

Where can I find that Please?

[BIGNEWY]

also make sure you remove all user modifications that you have done to your install and do a clean up and repair.

[dburne]

Uninstalled Display Drivers with latest version DDU in safe mode.

Installed latest Nvidia drivers clean.

Deleted all DCS Open Alpha shader files.

 

Loaded up Spitfire Normandy Instant Action Take Off Mission.

Performance identical to my post above, terrible. 30 fps over land with dips into upper 20's in VR, lots of stuttering. Barely achieving 45 fps over water only.

Landed and exited the mission.

DCS crashed once again on exit, same as in my post above.

 

Logs attached.

 

Again DCS was running without crashes with 2.1.0, only after updating to 2.1.1 this morning did the crashes start upon exiting the mission.

Will hold off for now and see what others report for VR performance in Normandy.

DCS.openalpha-Crash-20170621-131414.zip

[Art-J]

Where can I find that Please?

 

C:\Users\[your user name]\Saved Games\DCS 2 Open Alpha (or whatever it's called)\metashaders folder. Delete the content, let the game rebuild it on the first mission loading afterwards.

 

While you're there, go into \config subfolder and delete options.lua file as well (then re-do your game settings). It's a good habit to do so after every major game update.

[dburne]

C:\Users\[your user name]\Saved Games\DCS 2 Open Alpha (or whatever it's called)\metashaders folder. Delete the content, let the game rebuild it on the first mission loading afterwards.

 

I did that...

Ah never mind I should look closer, see you were replying to someone else sorry.

Edited June 21, 2017 by dburne

[badaboom]

C:\Users\[your user name]\Saved Games\DCS 2 Open Alpha (or whatever it's called)\metashaders folder. Delete the content, let the game rebuild it on the first mission loading afterwards.

 

While you're there, go into \config subfolder and delete options.lua file as well (then re-do your game settings). It's a good habit to do so after every major game update.

:thumbup: Thank You:thumbup:

[dburne]

I can enter and exit 2.1.1 fine if I do not fly a mission, only after flying a mission and trying to exit out of it does DCS stop responding.

[Krupi]

Have that issue with 2.1.0 :(

[dburne]

also make sure you remove all user modifications that you have done to your install and do a clean up and repair.

 

Clean up and Repair performed.

 

No change at all, VR Performance still very low as described, DCS still stops responding when trying to exit a mission in the Spit.

 

2.1.0 - VR Performance in same mission over Normandy I could maintain 45 fps with only occasional dips to upper 30's. Never crashed trying to exit the mission.

2.1.1 - VR Performance dropped to 30 fps over Normandy with dips into upper 20's.

Always crashes trying to exit mission. Does not crash if I don't fly a mission.

 

Same mission - Spit Take Off , same graphics settings between 2.1.0 and 2.1.1.

Edited June 21, 2017 by dburne

[bart]

Have that issue with 2.1.0 :(

 

Same here. When exiting a server after a multi player session, or any mission. I haven't tried 2.1.1 yet but will report back if there is any change. I also get bad stuttering when on the aircraft selection screen on a server, particularly if there's a lot of slots to choose from.

 

Hoping for an improvement in 2.1.1 but we'll see.

[dburne]

Loaded up the KA-50 Free Flight Mission Normandy.

 

Performance was a slight improvement - not much but mid to upper 30's , still not able to reach 45 fps except when over nothing but water.

 

Man that water is gorgeous, landed the chopper out in the harbor by a ship, beautiful and the sounds were awesome.

 

Also got a crash exiting this mission as well, DCS stopped responding when I clicked to exit the mission.

 

Crash and log files for last two crashes attached.

DCS.openalpha-Crash-20170621-160124.zip

Edited June 21, 2017 by dburne

[SkateZilla]

For Crashes: please attach logs and crash files for devs...

 

Are You Running the latest Windows 10 (Creators Update)??

[dburne]

For Crashes: please attach logs and crash files for devs...

 

Are You Running the latest Windows 10 (Creators Update)??

 

Attached to my last crash report.

 

Yes, Windows 10 Creators Update. Have had it for several weeks.

[dburne]

Ok tried one more time, Spit Instant Action Take Off at Normandy in VR.

 

Same result, clicking on exit mission results in DCS not responding. Each attempt has resulted in the same. I can enter DCS menu and exit fine, only when entering a mission and trying to exit the mission does this happen.

 

Log Files attached. I will stop there for now, hopefully all I have posted will help shed some light on the issue.

DCS.openalpha-Crash-20170621-172019.zip

Edited June 21, 2017 by dburne

[SkateZilla]

Attached to my last crash report.

 

Yes, Windows 10 Creators Update. Have had it for several weeks.

 

W10/CU + Game Mode has Issues with VR, and Gaming as a whole due to setting involved w/ Gaming Mode and Power Saving Profiles/Modes.

 

Double Check your profile is set to max performance, and make sure the gaming mode is disabled.

[dburne]

W10/CU + Game Mode has Issues with VR, and Gaming as a whole due to setting involved w/ Gaming Mode and Power Saving Profiles/Modes.

 

Double Check your profile is set to max performance, and make sure the gaming mode is disabled.

 

Yes, gaming mode has been disabled since shortly after getting the Creators Update ( and still is), and profile is set for Max Performance.

 

Thanks,

[Snails161]

Hi guys, I don't know if this helps anyone but was getting really bad stutter in dcs, on all maps. That was however until I turned my internet connection off???? It's now a stable(ish) 90 Fps in vr with no stutter to be seen! I don't know if it's just my system but worth a try.

I'm running a MSI ge72 laptop with 1070 graphics card and 16gb of ram.

[dburne]

Hi guys, I don't know if this helps anyone but was getting really bad stutter in dcs, on all maps. That was however until I turned my internet connection off???? It's now a stable(ish) 90 Fps in vr with no stutter to be seen! I don't know if it's just my system but worth a try.

I'm running a MSI ge72 laptop with 1070 graphics card and 16gb of ram.

 

Do you get 90 fps on Normandy Map?

[dburne]

Well this is strange. Not seeing reports from others at least on the crashing when trying to exit a mission issue, except maybe one or two.

 

I am not sure what is going on with this for me. 2.00 was great for me, 2.05 was great for me. 2.1.0 was good as well, 2.1.0 Update 1 was good at least regarding the crashing on exit issue.

 

Only after this morning's update , 2.1.1 can I not exit any mission cleanly, always stops responding shortly after clicking the exit button.

 

Not sure what else I could try. Removed Nvidia drivers in safe mode with latest version of DDU. Clean installed latest Nvidia drivers installing only Driver and PhysX as I usually do.

Did a clean and repair of DCS. Deleted all shader files, even deleted the fxo files for good measure.

 

For whatever reason only after today's update, I can not exit a mission cleanly at all. Crashes every time.

I am sure loving that gamma slider in VR though, made a world of difference. I settled on 1.3 and Normandy is stunning with deferred shading.

 

Going to sleep on this one, who knows maybe tomorrow it will work fine - after all this is PC's we're talking about lol. If not, maybe the next update will magically correct it.