[resolved] Oculus DK2 Crashes with 1.5.1.47025.99

After I updated to 1.5.1.47025.99 version, DCS started crashing with Oculus DK2 all the time when loading reaches 100% for all missions.

When I reverted back to 1.5.1.46722.87, it started working again.

# C0000005 ACCESS_VIOLATION at EEB251F2 00:00000000

00000000 00000000 0000:00000000

EEB251F2 001EEF90 0000:00000000 ?DrawObjects@DXRenderer@Graphics@@UEAAXPEAPEAVRenderObject@2@I@Z()+52

EBA6FE69 001EEFD0 0000:00000000 ?DrawZWrited@RenderParserImpl@@QEAAXXZ()+B9

EBA7333E 001EF030 0000:00000000 ?isEmpty@RenderParserImpl@@QEAA_NXZ()+2E1E

EBA8CF20 001EF500 0000:00000000 ?Render@SceneManager_Implement@@UEAAXXZ()+E40

3F9FDD7E 001EF570 0000:00000000

3FA01BE2 001EF5A0 0000:00000000

3FA17E14 001EF5D0 0000:00000000

3FA17D64 001EF600 0000:00000000

3FAC25CC 001EFCB0 0000:00000000

3FAC5785 001EFCF0 0000:00000000

76AD5A4D 001EFD20 0000:00000000 BaseThreadInitThunk()+D

76D0B831 001EFD70 0000:00000000 RtlUserThreadStart()+21

This is the exact problem I have. It gets to 100% and then takes a dump. I will post my log files soonest.

No idea what this difference is, but it's been fine for me with version 1.5.1.47025.99 (been online for several hours tonight),

Currently running, Windows 10, Oculus Runtime for Windows V0.8.0.0-beta, & GameWorks VR Driver Support version 358.78 (GTX TITAN X).

...Same problem here!!! I am on a Titan X oculus 8.0 and 358.87. Crash in DXrenderer.dll ...any thoughts on how I can revert to previous version?

Same problem.

Guys, can anybody try to reinstall 1.5 and put here DXrenderer.dll from older versions?

Same problem.

Guys, can anybody try to reinstall 1.5 and put here DXrenderer.dll from older versions?

...that... or a hot fix from the devs please!

Same problem for me (see attached logs)

My config :

Windows 10

GTX 670 (358.91)

Oculus sdk 0.8.0.0

Triple screen (tried with and without surround)

Logs.zip

Interestingly both me and my Cous played tonight , both got the update message , both updated and played fine for several hours . We then both bought another plane and then things crashed . It would be intersting to see if the people having problems have all bought or loaded up planes after the update . I have re-installed and done all updates and back to square one where it crashes all the time when loading anything using the oculus .

x-posting this in case it helps

Just a tip for anyone experiencing crashes with the Rift.

I can only speculate about the bug causing the crashes but I do know

• if there is only one aircraft slot in a mission (and it is the designated as player) then you try to spawn straight into the cockpit BUT this seems to cause a crash.
   
  
• if you add a second aircraft (as a client) to the mission then when you run the mission you initialise outside the cockpit with a world view and the slot menu and when choose to spawn into the aircraft you do not crash.
   
  
• if you have CA and add a CA slot to the mission this is also true; when you run the mission you initialise outside the cockpit with a world view and the slot menu , and when you choose to spawn into the aircraft you do not crash.
  

Basically setup the mission to initialise with a world view instead of straight into the cockpit in VR. (You will have to edit MOST missions to temporarily fix them or wait for ED to fix the bug)

If other people want to confirm that would be great.

That seems to make sense since it also works fine in multiplayer, only single player missions have issues. also seems to be three monitor setups or the rift having issues

Just a tip for anyone experiencing crashes with the Rift.

 

I can only speculate about the bug causing the crashes but I do know

 

• if there is only one aircraft slot in a mission (and it is the designated as player) then you try to spawn straight into the cockpit BUT this seems to cause a crash.
  
• if you add a second aircraft (as a client) to the mission then when you run the mission you initialise outside the cockpit with a world view and the slot menu and when choose to spawn into the aircraft you do not crash.
  
• if you have CA and add a CA slot to the mission this is also true; when you run the mission you initialise outside the cockpit with a world view and the slot menu , and when you choose to spawn into the aircraft you do not crash.
  

 

Basically setup the mission to initialise with a world view instead of straight into the cockpit in VR. (You will have to edit MOST missions to temporarily fix them or wait for ED to fix the bug)

 

If other people want to confirm that would be great.

Two thumbs up - this is legit. :thumbup: :thumbup:

How do these patches get the all clear without first testing them on the Oculus Rift to see if they work? I thought we had seen the last of the crash bug for Oculus Rift after waiting some weeks for the last one to be fixed. Seems like where back to square one only this time I cannot connect at all with the Rift now. I havn't used the ditor yet so I have no idea how to do the temp fix. Plus I don't want to mess with the beta game when I thought we weren't supposed to.

When can we expect a fix for this? I was hoping to play Neveda at the end of the month in the Rift.

Crunchy, it's not just the Rift with problems, this bug may also be affecting others. It has been reported. Not sure that more than that can be done. Use the provided work around and you can keep playing.

It's strange, My standalone Beta works fine on my rift but Steam version won't go past loading mission stage. Has the latest update been pulled ? Because my Standalone version doesn't update with the .99 hotfix.

Tony

It's strange, My standalone Beta works fine on my rift but Steam version won't go past loading mission stage. Has the latest update been pulled ? Because my Standalone version doesn't update with the .99 hotfix.

 

Tony

I'm confused by your post are you saying there is a hotfix for the Rift on the stand alone version? You also say your stand alone version works fine, but I use the stand alone version and it doesn't get past the mission loading screen. You then say you can't update the stand alone version?

Hi Crunchy, sorry for the confusion mate. My standalone 1.5 beta tried to update to latest but failed for some unknown reason. I'm on the version before the .99 patch and it works fine. Every time I start the game now it tries to update with something but always says servers busy. I then start the game and all works fine. Hope that's a bit clearer?

Tony

Same problem here.

When i start a mision created by mision editor, DCS crash in oculus rift

When i start a "rapid mision" , it works normally

Sorry by me english...:huh:

Same problem here.

 

When i start a mision created by mision editor, DCS crash in oculus rift

 

When i start a "rapid mision" , it works normally

 

Sorry by me english...:huh:

A quick mission doesn't work for me, it just crashes at the end of the mission loading screen :mad:, I saw that some guy said it worked for him up until he installed another module, but after that he can no-longer get it to work now and he to crashes on the mission loading screen.

i have just updated to win 10, im running 0.8 beta and it crashes every time i try a mission of any kind, or in mission editor unless i select (client). doing this works ever time.

i hope they fix this soon :(

I think my issue is related so linked it here:

http://forums.eagle.ru/showthread.php?t=153054

The latest patch has resolved this issue for me, hope there is no regression so i can get some quality ka 50 and mig 21 action going on!! :joystick:

Confirmed, it is fixed and DK2 works great now as of today, whereas before it would crash at 100%.

Now to solve judder...