[REPORTED] DK2 Crashes

[Wynthorpe]

Loads 1 time in 10 then crashes, no error or dont know where to find error

 

R9 290X

i5 4690K

16GB RAM

 

7.0 Runtime

 

Beta Drivers for AMD

[KaspeR32]

Same problem. Just getting a CTD when loading the Su-25t Mission ( Anti-Radar Missile Practice). I have latest nvidia drivers ( 355.98 ) and the Oculus 0.7.0.0 runtime. Menu loads fine for me.

[Wynthorpe]

Menu loads quite often, have flown once with the DK2 and looked superb! Never worked since.

[NineLine]

Include logs please. Read the FAQ for what makes a good bug report. Thanks

[Badyk]

Crash to desktop with Oculus Rift

 

Hi Folks,

 

Problem:

Getting a regular CTD when loading flights.

 

It happens after I press FLY. I get the loading bar and I get a "DCS has stopped working" error in Windows shortly after. It doesn't seem to fail in the same place every time and I have managed to get in-game once.

 

Also the GUI loads behind me in my 4 o'clock and I haven't figured out how to center it (I can center in-game by pressing 5.

 

It happens in both the TF-51 and SU-25. I haven't been able to download other modules to test as yet.

 

I have attached logs and nfo file in a single zip.

 

Thanks for the late nights over the last while and what I have seen looks AWESOME! :)

dcs logs.zip

[Kegetys]

I get this as well, my logs attached. Interesting bit is this:

 

 

00003.685 ERROR Lua::Config: Lua error [string "BinocularCameraDialog = require('BinocularCameraDialog')"]:1: module 'BinocularCameraDialog' not found:

no field package.preload['BinocularCameraDialog']

no file '.\BinocularCameraDialog.lua'

no file 'C:\Pelit\DCS World OpenBeta\bin\lua\BinocularCameraDialog.lua'

no file 'C:\Pelit\DCS World OpenBeta\bin\lua\BinocularCameraDialog\init.lua'

no file 'C:\Pelit\DCS World OpenBeta\bin\BinocularCameraDialog.lua'

no file 'C:\Pelit\DCS World OpenBeta\bin\BinocularCameraDialog\init.lua'

no file './Scripts/BinocularCameraDialog.lua'

no file './Scripts/Common/BinocularCameraDialog.lua'

no file './Scripts/UI/BinocularCameraDialog.lua'

no file './Scripts/UI/F10View/BinocularCameraDialog.lua'

...

Possibly the file BinocularCameraDialog.lua is missing from the distribution?

Logs.zip

[Wynthorpe]

I'll attach mine shortly.

[KaspeR32]

DK2 Crash

 

Logs attached. Crashes when mission is loading. 9 out of 10 times. Latest Nvidia Drivers ( 355.98 ) and Oculus 0.7 runtime.

logs.zip

[Wynthorpe]

Logs attached

Logs.zip

[DerekSpeare]

I get the mirror on the main screen showing head tracking, etc, but there's nothing displayed on the Oculus. I'm running 0.6.0.0 runtimes and 355.92 nvidia drivers. The Oculus is in Direct mode.

 

I prefer the old method in DCS where the GUI was on the main screen and the flying would come on the Oculus. This new system is not optimal and should be changed back to the other method.

[erussellcfi]

dk2 crash

 

Same as others have posted The menu displays correctly on DK2 every time however when I try to launch a mission IE instant action it crashes a little over halfway through the loading process.

Logs.rar

[RaXha]

I get the mirror on the main screen showing head tracking, etc, but there's nothing displayed on the Oculus. I'm running 0.6.0.0 runtimes and 355.92 nvidia drivers. The Oculus is in Direct mode.

 

I prefer the old method in DCS where the GUI was on the main screen and the flying would come on the Oculus. This new system is not optimal and should be changed back to the other method.

 

 

0.7.0.0 Rift support with Direct Display mode and VR front end GUI, but still very much work-in-progress until hardware reaches consumer release versions

 

I'm fairly sure you need to update to runtime 0.7.0.0 for Oculus support to work in DCS 1.5.

[DerekSpeare]

I'm fairly sure you need to update to runtime 0.7.0.0 for Oculus support to work in DCS 1.5.

 

This is good advice, and I think this is it. However, it's my understanding that the 0.7.0.0 runtimes are backwards compatible with those who are running 0.6.0.0 - some official word on this would help, and it would be guiding to know if the 0.7.0.0 runtimes are mandatory for v1.5.

 

I'm looking forward to what comes down the line. I know they worked hard on this.

[vicx]

I'm running 0.6.0.0 runtimes

 

Pretty sure DCS 1.5 is built to support, and requires, Rift 0.7 runtime.

[Frusheen]

This is good advice, and I think this is it. However, it's my understanding that the 0.7.0.0 runtimes are backwards compatible with those who are running 0.6.0.0 - some official word on this would help, and it would be guiding to know if the 0.7.0.0 runtimes are mandatory for v1.5.

 

I'm looking forward to what comes down the line. I know they worked hard on this.

 

 

0.7 runtime is required. Rift support in the current release of 1.5 is bugged and the runtime is not meant to be backwards compatible so your best bet is to hold off till the next update.

[DerekSpeare]

Thank you, gents...that pretty much is that...unfortunately I can't go to 0700 right now b/c some programs I am testing require 0.6.0.0 :/

[Frusheen]

DK2 Crash

 

Windows 7 64

Nvidia GTX780

Driver 355.98

Oculus Runtime 0.7

 

 

Front end GUI is working with head tracking. Crash on mission load screen - 'DCS has stopped responding' See dcs.zip

 

Edit: Successful mission load and flight with Huey module followed by crash on exit - see logs.zip

dcs.zip

Logs.zip

Edited October 1, 2015 by Frusheen
Added log for sucessfull mission load with crash on exit

[metalnwood]

Derek, I am unsure if compatibility goes that way. I .e. Not sure sdk 6 will work. Usually the new SDK will support games compiled on a previous sdk version but in this case you are asking a game compiled with 0.7 to sun on sdk 0.6.

[Frusheen]

Lets keep this thread to reporting the issue with logs and appropriate info as requested by mods. The cleaner we keep it for devs the easier it will be for them to work it out. General DK2 discussion should be in the rift thread:

 

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

[Nanard421]

Windows 10 64bits

NVidia GTX 670

Driver 356.04

Oculus Runtime v0.7

Triple screen + DK2

 

I was able to launch P51, TF51 and BF109 after many tries.

 

I was never able to launch Huey or Hawk after many tries.

Huey without oculus works but Hawk without oculus didn't worked.

Logs.zip

[DerekSpeare]

Derek, I am unsure if compatibility goes that way. I .e. Not sure sdk 6 will work. Usually the new SDK will support games compiled on a previous sdk version but in this case you are asking a game compiled with 0.7 to sun on sdk 0.6.

 

Yes, that's it now that I have had time to think on it :joystick:

 

 

• If a game is compiled with the v7 SDK, users running v6 runtimes are out;
  
• If a game is compiled with the v6/6.1 SDK, users running v7 runtimes are in
  

I'm in the first one :noexpression:

[metalnwood]

Call me stupid, I would like to get the log file but I read the faq and I have no directory called 'logs', 'saved games' etc under my DCS directory. I can find it in my documents directory or any where else that I guessed it could be?

[Nanard421]

It is under <drive>:\Users\<username>\Saved Games

[hellking]

I have found a work around.

 

Right after you launch the mission, before crash happens, quickly maximize another fullscreen window (iexplorer, etc.) to cover the DCS window (so that DCS window remains hidden under the other window).

 

I think something is going wrong during render of the window on the monitor (not on the Oculus).

 

I am currently a bit disappointed with the DK2 graphics performance, but I haven't tweaked it yet.

 

EDIT: After seeing saigai's message, I tried turning Vsync off. It improves the performance to at least equivalent of 1.2 version, which is great news! Now the only problem is it crashes 95% of the time during mission load. It is like playing dice and trying to get double 6'es. I am still doing the window switching, but I have no idea if this has anything to do with successful loads.

Edited October 2, 2015 by hellking

[hellking]

I played with the graphics settings and workaround doesn't work anymore... I guess I will have to wait for the fix...

 

Here is my log

 

# C0000005 ACCESS_VIOLATION at E96AFE8A 00:00000000

00000000 00000000 0000:00000000

E96AFE8A 001BE5C0 0000:00000000 ?createRasterizerState@DX11Renderer@RenderAPI@@UEAA?AV?$Ptr@UIRasterizerState@RenderAPI@@UDefaultDeleter@ed@@@ed@@AEAURasterizerStateDesc@2@@Z()+20FA

EAE18894 001BE610 0000:00000000 ?addMSAAShaderDefine@PostEffectBase@PostEffects@@IEAA_NAEBVTexture@render@@AEAV?$vector@VDefinePair@render@@V?$allocator@VDefinePair@render@@@ed@@@ed@@@Z()+5EA4

EB5F8D6B 001BE850 0000:00000000 ?RenderUI@SceneManager_Implement@@UEAAXXZ()+72B

EB600CAF 001BE8B0 0000:00000000 ?ShowProgress@SceneManager_Implement@@UEAAXMAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@ed@@@std@@@Z()+9F

EB600FA1 001BE910 0000:00000000 ?DrawWaitScreen@SceneManager_Implement@@UEAAXM@Z()+B1

3F76C9C6 001BEBF0 0000:00000000

3F7662D6 001BEEB0 0000:00000000

EC045A3A 001BEEE0 0000:00000000 ?sendOutputSymbol_@FSM@Common@@AEAAXI@Z()+2A

EC0459F8 001BEF20 0000:00000000 ?enterToState_@FSM@Common@@AEAAXI@Z()+C8

EC0457FB 001BEF60 0000:00000000 ?onSymbol_@FSM@Common@@AEAAXI@Z()+1CB

3F76525B 001BF060 0000:00000000

F4F67254 001BF0A0 0000:00000000 luaD_growstack()+7A4

F4F76FB5 001BF220 0000:00000000 luaS_newlstr()+49C5

F4F67541 001BF250 0000:00000000 luaD_growstack()+A91

F4F6684F 001BF3D0 0000:00000000 lua_getinfo()+11AF

F4F6785E 001BF410 0000:00000000 lua_yield()+9E

F4F62440 001BF460 0000:00000000 lua_pcall()+60

E920287B 001BF490 0000:00000000

EA936D79 001BF4E0 0000:00000000 ?callWidgetCallbacks_@Widget@gui@@MEAAXH@Z()+69

EA916AF3 001BF510 0000:00000000 ??0ListBoxSkinBase@skin@gui@@QEAA@PEAVListBoxBase@2@@Z()+3D3

EA8F7518 001BF540 0000:00000000 ??_FModalWindow@gui@@QEAAXXZ()+1308

EA8F0560 001BF590 0000:00000000 ?processMessages@GUI@gui@@QEAAXXZ()+70

3F76EE67 001BF5C0 0000:00000000

3F76B44E 001BF620 0000:00000000

3F781BE4 001BF650 0000:00000000

3F781B34 001BF680 0000:00000000

3F82B4BC 001BFD30 0000:00000000

3F82D365 001BFD70 0000:00000000

76D65A4D 001BFDA0 0000:00000000 BaseThreadInitThunk()+D

76F9B831 001BFDF0 0000:00000000 RtlUserThreadStart()+21

 

My system:

2 x GeForce GTX980 (NVIDIA driver version 355.98)

32 GB RAM

Intel core i7-3930K * 3.2 GHz

Windows 7 64-bit

 

I tried in both SLI and no-SLI.

Edited October 2, 2015 by hellking