hellking

Anybody else observing major differences in Oculus performance with different openbeta version? 1.5.1.46722.87 was the best in terms of performance and stability. 1.5.1.46722.99 was completely broken, not able to launch missions 1.5.1.46722.10? was stable, but frame rate dropped by ~25%, making most planes stutter at medium graphic settings with a high end graphics card My GPU utilization is at 30% or so, and my system is limited by CPU. I think it is because of the DK2 graphical projections that are taking place. They need to find a good solution to this (move DK2 projections to GPU, or efficient multi-threaded CPU) especially since CV1 is coming.

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

All, there is a workaround to the crashing problem. See http://forums.eagle.ru/showpost.php?p=2507760&postcount=79

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 believe I have found a workaround. See http://forums.eagle.ru/showpost.php?p=2507760&postcount=58

WORKAROUND FOUND! All, after experimenting with it for 3 hours I have found a workaround for the DK2 crash problem. You simply need to run it in "Vista Compatibility" mode. 1) Right-click on DCS shortcut 2) Click on Properties 3) Go to compatibility tab 4) Select "Windows Vista" compatibility mode First impressions?? I have all settings High (make sure that VSYNC is off!) and no judder at all in the base. As crisp as FlyInside FSX: Amazing!! Let me know if it works for you.

Admin, can you merge this thread into the other DK2 thread which was opened 7 minutes before this one? http://forums.eagle.ru/showthread.php?t=147767 Just trying to make sure that all DK2 crash information is consolidated for providing good data to developers. Thanks!

Those who had problems with Oculus Rift, could you please write your system specs down (OS, graphics card, graphics driver version, etc..)? Looking at the success stories, I suspect that people with Windows 7 are the ones having problems. Windows 8 and 10 are ok.

This thread is a duplicate of http://forums.eagle.ru/showthread.php?t=147775

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.

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.

You can turn it off by modifying the script file for MIG-15. The file is C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\Mods\aircraft\MiG-15bis\Cockpit\Scripts\mainpanel_init.lua To turn off autolean, set it to false: autoLeanToAimMiG15 = false Just to throw in as a bonus, you may want to also switch off auto hunker down for F-86 (if you have the module). Here is how to disable head height adjustment that happens after you take off: C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\Mods\aircraft\F-86\Cockpit\Scripts\mainpanel_init.lua landSeatAdjustF86 = false