[REPORTED] DK2 Crashes

[joebloggs]

I have very bad judder still as well but only when the dk2 is within view of the camera. If I move out of range I have silky smooth head tracking (but then of course no positional tracking). Not sure if it is related to frame rate. I'll lower graphics settings to check (gtx 780).

 

Could others with high frame rates and judder test this camera theory and let me know what they find please.

 

I would have thought having positional tracking is going to use more processing power, hence the reason you get better FPS in the Rift without positional tracking. I'm not certain about this though so someone who's has a better knowledge of this might help.

[Deano87]

I have found that the FPS performance very much dependent on the module I am using. Some modules get max FPS and 0 judder no matter where I am on the map. I see the grass, buildings far away, etc... But some other modules have judder even when I am far from bases or cities. The two modules: MIG-21 and UH-1 show very low performance, while almost all of the others (including KA-50 with it's large and complicated cockpit) are silky smooth.. I think developers need to optimize the low performing modules, or at least have an option in graphics settings to dial things down.

 

I experience the same issue with the Mig-21, constant judders which makes it completely unplayable in the rift.

[joebloggs]

I have found that the FPS performance very much dependent on the module I am using. Some modules get max FPS and 0 judder no matter where I am on the map. I see the grass, buildings far away, etc... But some other modules have judder even when I am far from bases or cities. The two modules: MIG-21 and UH-1 show very low performance, while almost all of the others (including KA-50 with it's large and complicated cockpit) are silky smooth.. I think developers need to optimize the low performing modules, or at least have an option in graphics settings to dial things down.

 

I think they'll optimize the low performing modules in time. Remember this is a beta and there will be lots of fixes over the coming weeks. But what do you mean by an option to dial things down? There are already plenty of options to dial things down in the DCS settings. Do you mean dial things down in the cockpit and what could you dial down in there if you do? You've already said the Ka-50s complicated cockpit works so I would have thought the others would after some tweaks.

[Frusheen]

My judder problems are caused by frame rate. I have confirmed it after some testing. Using the FPS counter display anything below 150 is a juddery mess. Given the rifts refresh rate is 75 it seems that the counter is counting frames rendered per eye (75x2).

 

It does not appear asynchronous time warp is implemented in the beta yet.

 

Worst performance is at airports. Once I get into the sticks and back to 150 all is good. Hopefully further optimisation and time warp implementation will help things. I'm using a gtx780 OC edition but will need a new graphics card. That frame rate requirement needs to jump to 180 in a few months!

Edited October 8, 2015 by Frusheen

[joebloggs]

I'm using a gtx780 OC edition but will need a new graphics card. That frame rate requirement needs to jump to 180 in a few months!

 

Yeah, I'm glad I got the DK2 because you might struggle to get the 180 FPS you need for CV1. I can't wait to see DCS in CV1 though, I bet it will be awesome.

[DerekSpeare]

I updated to the 0700 runtimes and set DCS to run in Vista Compatibility mode (kudos hellking). I fired up DCS and got on right away. I don't have my modules installed, but I dropped into the SU27 and all is good. There's some judder, but this is a BIG improvement over v1.2.

[Wynthorpe]

Yeah, I'm glad I got the DK2 because you might struggle to get the 180 FPS you need for CV1. I can't wait to see DCS in CV1 though, I bet it will be awesome.

 

So you're going to need 180fps not 75fps in CV1?! We're going to need 2 cards at least for new games.

[Frusheen]

So you're going to need 180fps not 75fps in CV1?! We're going to need 2 cards at least for new games.

 

CV1 refresh rate will be 90Hz. Given that the dcs fps display counts total frames rendered it means we will need to render 180fps or 90fps for each eye versus 75fps (150 total on dcs counter) for DK2.

 

It's a jump from 75 to 90 not 75 to 180.

 

Given the increase in resolution with CV1 it will still require a beast of a system for dcs.

Edited October 9, 2015 by Frusheen

[Deano87]

So the new update (1.5.0.45655) now breaks oculus support again for me. Crashes while loading even with the compatibility mode set to vista.

 

:(

 

Interestingly it crashes when it gets to the end of the loading bar, not in the middle like it did before. I will attempt to get some crash logs etc and upload them here.

Edited October 10, 2015 by Deano87

[Frusheen]

So the new update (1.5.0.45655) now breaks oculus support again for me. Crashes while loading even with the compatibility mode set to vista.

 

:(

 

Interestingly it crashes when it gets to the end of the loading bar, not in the middle like it did before. I will attempt to get some crash logs etc and upload them here.

 

Mine was doing the same after the update. Restarted the PC and got in first time.

 

I am still having occasional crashes on load screen but not as bad as without running in vista compatibility mode. Whatever is causing the dk2 crashes it is still present after hot fix 2.

[joebloggs]

So the new update (1.5.0.45655) now breaks oculus support again for me. Crashes while loading even with the compatibility mode set to vista.

 

:(

 

Interestingly it crashes when it gets to the end of the loading bar, not in the middle like it did before. I will attempt to get some crash logs etc and upload them here.

 

Same here, I just wish ED would confirm this is a bug like they have with other bugs in this section of the forum. This would stop people suggesting hundreds of different things to try and fix it. They have confirmed other crash bugs, so why not this one? The only one fix that did help before the latest patch was to change to Visa compatibility. Unfortunately, it no-longer works now and I crash right at the end of mission loading screen most of the time. I will send another log, but I'm not sure if it will do any good with no word from ED that it is a bug.

 

Edit: @Frusheen - The hot fix mentions no fix for Oculus Rift crashes, it just mentions the color fixes, unless I'm mistaken.

Edited October 10, 2015 by joebloggs

[bongodriver]

I have found that going in to the settings menu and poking around (I used controller setup menu) sometimes allows me in to the game afterwards.

[joebloggs]

DK2 Crash Log.

 

0.7 Runtime.

Windows 64 bit fully updated.

Latest Nvidia drivers.

DK2 Crashes.rar

[Mt5_Roie]

Since the last update I've had more luck going back offline in order to use the Rift. I did do a FPS test today to compare all the graphic settings and see which one works better. While Low was the best with no Judder...Ultra was pretty sweet.