Dedicated 1.5 Oculus Rift DK2 thread

[pittlebelge]

Hi pittlebelge,

 

If steam is getting in the way, just download the standalone client. All your steam keys will work in the standalone so you can just ship them all over to that with no hassle. As long as you are on SDK 0.7.0 you should find a much easier experience.

 

Thx, i'll give it a shot.

[Gunja]

I'm on old i7 920 and ati HD7980. Windows 8.1 and amd drivers with 0.7 SDK Support.

I only tried F-15 quick mission several times. It always loaded, and never crashed during game play. Game freezes when i escape and click exit but that is sometimes the case even without the rift on that mission.

Vsync is off but i still have heavy judder which is to be expected with my GPU so i cant play for long before i get sick :puke:

I think that people should try same testing scenario with and without the rift, to make sure that the rift is responsible for CTD or other errors before reporting.

[Tellurico]

Hi all!

DCS 1.5.0.45208.37 ON W7 64bit and DK2 with Runtime 0.7 here, no luck starting any mission :(

Without Oculus everything runs nice and super smooth (I have a GTX Titan X with latest drivers).

 

The interface shows up in the Rift and mission starts loading, then DCS quits without any advice.

 

Crash log here:

 

# -------------- 20151003-105735 --------------

# C0000005 ACCESS_VIOLATION at DE23FE93 00:00000000
00000000 00000000 0000:00000000 
DE23FE93 0024E0C0 0000:00000000  ?createRasterizerState@DX11Renderer@RenderAPI@@UEAA?AV?$Ptr@UIRasterizerState@RenderAPI@@UDefaultDeleter@ed@@@ed@@AEAURasterizerStateDesc@2@@Z()+2103
E0598894 0024E110 0000:00000000  ?addMSAAShaderDefine@PostEffectBase@PostEffects@@IEAA_NAEBVTexture@render@@AEAV?$vector@VDefinePair@render@@V?$allocator@VDefinePair@render@@@ed@@@ed@@@Z()+5EA4
E0D88D6B 0024E350 0000:00000000  ?RenderUI@SceneManager_Implement@@UEAAXXZ()+72B
E0D90CAF 0024E3B0 0000:00000000  ?ShowProgress@SceneManager_Implement@@UEAAXMAEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@ed@@@std@@@Z()+9F
E0D90FA1 0024E410 0000:00000000  ?DrawWaitScreen@SceneManager_Implement@@UEAAXM@Z()+B1
3FFFC9C6 0024E6F0 0000:00000000 
3FFF62D6 0024E9B0 0000:00000000 
E27C5B5A 0024E9E0 0000:00000000  ?sendOutputSymbol_@FSM@Common@@AEAAXI@Z()+2A
E27C5B18 0024EA20 0000:00000000  ?enterToState_@FSM@Common@@AEAAXI@Z()+C8
E27C591B 0024EA60 0000:00000000  ?onSymbol_@FSM@Common@@AEAAXI@Z()+1CB
3FFF525B 0024EB60 0000:00000000 
EB5F7254 0024EBA0 0000:00000000  luaD_growstack()+7A4
EB606FB5 0024ED20 0000:00000000  luaS_newlstr()+49C5
EB5F7541 0024ED50 0000:00000000  luaD_growstack()+A91
EB5F684F 0024EED0 0000:00000000  lua_getinfo()+11AF
EB5F785E 0024EF10 0000:00000000  lua_yield()+9E
EB5F2440 0024EF60 0000:00000000  lua_pcall()+60
DEB8287B 0024EF90 0000:00000000 
E0086D79 0024EFE0 0000:00000000  ?callWidgetCallbacks_@Widget@gui@@MEAAXH@Z()+69
E0066AF3 0024F010 0000:00000000  ??0ListBoxSkinBase@skin@gui@@QEAA@PEAVListBoxBase@2@@Z()+3D3
E0047518 0024F040 0000:00000000  ??_FModalWindow@gui@@QEAAXXZ()+1308
E0040560 0024F090 0000:00000000  ?processMessages@GUI@gui@@QEAAXXZ()+70
40011AF7 0024F0C0 0000:00000000 
400BB4BC 0024F770 0000:00000000 
400BD365 0024F7B0 0000:00000000 
776C59CD 0024F7E0 0000:00000000  BaseThreadInitThunk()+D
777FB981 0024F830 0000:00000000  RtlUserThreadStart()+21

 

If anybody found a solution please share it :)

 

Giuliano (Italy)

Edited October 3, 2015 by Tellurico

[CookPassBabtridge]

Hi Tellurico

 

The only thing I found that I could suggest is to try lots of different missions and scenarios - it seems some will cooperate more than others. YMMV though.

[frank7006]

It looks so white washed. Any fix for this currently?

[metalnwood]

It looks so white washed. Any fix for this currently?

 

Doesnt seem to be. I had a quick poke around the lua files and changed some HDR parameters to tone it down but didnt notice any change.

[smirkza]

OK, so when it works - it's incredible.

 

I mean, truly awesome! The sense of actually flying, the smoothness, the quality of the visuals. I can't believe how the dials are actually clearer now, the writing easier to see.

 

I haven't found any benefit to using alt-enter to frame rates. No change at all that I can see.

 

The 'washed out' look is apparent, and a fix will be welcome, but it most certainly does not interfere with the experience to a point of distraction.

 

The crashes are a problem, and I've found the only sure way to get it working is with a reboot. It seems the first game load of each reboot works without a hitch, but any further attempts crashes on loading or the tracking doesn't work properly. And of course, it crashes every time I quit a mission.

 

No individual aircraft seems not to work - as long as it's first go of reboot they all load.

 

Deeply, deeply enjoyable experience. Only downside (other than the extra time I'm going to lose to DCS) is the ground textures seem extra flat when flying low and slow - but meh, small price to pay. Flying the Huey Falcon style through a dense city actually made me laugh out loud - such a great experience.

 

Smirks

[LuSi_6]

Doesnt seem to be. I had a quick poke around the lua files and changed some HDR parameters to tone it down but didnt notice any change.

 

It's a SDK thing

 

 

API Changes

 

This release represents a major revision of the API. Changes to the API include:

The SDK now uses sRGB-aware rendering instead of making assumptions. Unless you update your code, rendered scenes will appear brighter than before. For more information, see Migrating from SDK 0.6.x to SDK 0.7.

 

[djbordie]

Ouch, that is rough if its sdk based.

 

we probably wont see a fix for that for some time

 

wow, some pretty intense technical reading

https://developer.oculus.com/documentation/pcsdk/latest/concepts/release-migration/

[Frusheen]

I don't think we'll see any oculus update for a while. I'll be pleasently surprised if they do fix it soon. It's ominous that the dk2 crash thread hasn't been marked as reported yet.

[LuSi_6]

ED needs to update their Code (image color format). It depends how the rest of the processing works this either just one or two lines of code or a major rewrite. Lets all hope for the first option

 

it's like converting strings and chars in c++ (it works like a charm or it ruins your day :D )

Edited October 5, 2015 by LuSi_6

[CookPassBabtridge]

Is the white wash thing not something that could be fixed if we had access to the gamma/ brightness settings though? 0.7 hides the rift from nvidia settings, is there no way to preserve the benefits of direct mode but get back the ability to tweak?

[djbordie]

anyone want to post some lua edits?

[Frusheen]

Id personally prefer to wait for a fix from the devs. It's a beta so I don't want to start editing files plus with the amount of attempts it takes to get into a mission it's hardly worth the hassle.

[LuSi_6]

that's the way. No way to fix this with lua or shaders, pictures get rendered differently

[djbordie]

how about sweetfx?

[Carabassa]

I think SweetFx is not going to work ever with direct mode (the way Oculus is working since SDK 0.7). The increased resolution of the consumer version sould be "enough" to play without it.

 

The only thing that developers can do is to put some kind of image processing in the render code. For example Elite Dangerous lets you configure some supersampling resolutions but don't know if it will work once they introduce direct mode with SDK 0.7.

[djbordie]

interesting, I keep forgetting direct mode doesnt allow adjustments as if it were a separate screen.

 

pros and cons, however extended mode should never have existed...

[frank7006]

I think SweetFx is not going to work ever with direct mode (the way Oculus is working since SDK 0.7). The increased resolution of the consumer version sould be "enough" to play without it.

 

The only thing that developers can do is to put some kind of image processing in the render code. For example Elite Dangerous lets you configure some supersampling resolutions but don't know if it will work once they introduce direct mode with SDK 0.7.

 

SweetFX substantially increases clarity. I would choose SweetFX over direct mode any day. We need SweetFX and the higher resolution of the Rift CV1. I would guess that the increased clarity you get from SweetFX is more substantial than the increase in clarity you get from the higher resolution of CV1.

[LuSi_6]

for me it's the opposite: Image is much much better in direct mode compared to old extended with sweetfx...

[smirkza]

For all of you who may have missed this, hellking found a fix for the crashes.

 

After testing, it seems to totally resolve all crash issues related to the DK2 - even letting you get back to the menu after a game without crashing. I can spawn every single time now, even training missions.

 

Nice work hellking!

 

Link to his post - http://forums.eagle.ru/showpost.php?p=2507760&postcount=58

[djbordie]

I came across this in case anyone needs to switch back and forth runtime for other games/demos.

works perfectly!

 

Edited October 7, 2015 by djbordie

[Revelation]

Yeah hellking's "fix" did the trick for me. I am very surprised at how high my framerate is with DK2 and max settings to include DSR at 4k.

 

Now I just need CV1 or Vive to come out with a higher resolution.

[McDeth187]

So ya, running in Windows compatibility mode definitely fixed my inability to start and get into game without crashing. Yay!

 

That being said, it seems as if the tracking is limited to the original DK1 30hz and not the 120hz (or whatever the DK2 runs) so the view is pretty jerky and unsustainable. I had to take the DK2 after a few minutes as I was getting a little sick.

 

Has anybody else encountered that?

[Frusheen]

So ya, running in Windows compatibility mode definitely fixed my inability to start and get into game without crashing. Yay!

 

That being said, it seems as if the tracking is limited to the original DK1 30hz and not the 120hz (or whatever the DK2 runs) so the view is pretty jerky and unsustainable. I had to take the DK2 after a few minutes as I was getting a little sick.

 

Has anybody else encountered that?

 

Yes but only when within view of the positional camera. If I move outside its range I have silky smooth orientation tracking but of course no positional. Could you test this on your system and see if the results are the same?

 

Seems to happen irrespective of frame rate for me but need to do more testing in that regard.

 

On other news the colour saturation issue has been fixed and is coming in a future patch.