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)

OK thanks, I'll wait for DCS with EDGE even more impatiently now :) Thanks for the hint, I've always used the DK2 as secondary monitor :doh:, will try as primary :joystick:

Hi all, I am doing some extensive testing with the Titan X and the Oculus Rift DK2. I found a good compromise between quality and performance and I created a benchmark mission I am using to test the various aircrafts. I can keep constant 75fps (no judder) with every plane (Hawk and A10C included), even with cockpit and flood lights on, but there is no way to get the C-101 working at that frame rate, I always get bad judder which makes it unusable with the Rift. The problem is mainly visible in cockpit view (as if there is too much geometry or it is not very well optimized) but also looking the aircraft with F2 causes the problem. I can get to 75fps just in extremely sparse situations (over the sea for example) but as soon as I get close to an airport judder starts again. Turning on the cockpit flood lights makes things much worst. Unfortunately, there is no way to shortcut the other light controls from the hotkey assignment panel and the clickable cockpit is unusable with the Rift. It's such a sin because I love to fly this plane, I would really love to get a smooth experience as the other planes. Giuliano Golfieri aka Tellurico 36° Stormo Virtuale Italy

+1

Thanks guys! :)

Hi all, I finally finished my custom UFC and I would like to share it with you: Please let me know what you think about it. It took a couple of weeks to design and assemble everything and about 150 euros in workings and parts (I opted for a "all-plexiglass" solution which is very cool but quite expensive), but I am extremely happy with the result :thumbup: I decided to use the 6 unused keys for the RWR controls and STR PT/TCN/ILS buttons. Very helpful. For building pictures and so on you can find a complete thread on our 36th squadron forum (in italian): http://www.36stormovirtuale.net/Forum/index.php?topic=16717.0

1.2.1.6099 is out. I can't test it at the moment. Can anyone notice any improvement?

OK faccio subito il rollback alla 1.2.0, non ha senso questo update! Comunque ho installato anch'io l'hotfix e non migliora nulla, probabilmente sistema solo il problema dell'attivazione. Inoltre confermo che il problema del puntatore rimane, le missioni si caricano molto più lentamente e c'è un "soffocamento" (1 fps) di circa 5 secondi all'ingresso nella missione che prima non c'era... insomma a parer mio una chiavica fenomenale!

L'ho scritto anche nel forum inglese (http://forums.eagle.ru/showpost.php?p=1566306&postcount=318), ma sono certo che sappiano già quale sia il problema... :joystick:

Anti-Aliasing setting?

Ragazzi penso di aver capito il problema degli FPS, o per lo meno cosa lo causa! Grazie a tutti i test fatti nei giorni scorsi durante dei tentativi di overclocking di CPU (2600K) e GPU (GTX680) (sempre coi monitor di CPU e MSI per la GPU attivi) ho notato che ora la GPU, con gli stessi settings usati per la 1.2.0, lavora sempre al 97%-98% nelle situazioni di benchmark dove prima restava sui 70%-80%. Ho cambiato sistematicamente tutti i parametri sia di scheda video sia di DCS e ho isolato il problema: l'antialiasing!!! In precedenza che mettessi l'AA a 2x o a 16xQ CSAA (dal pannello di controllo nVidia lasciandolo su OFF nei settings di DCS come consigliato in vari forum) non cambiava quasi per nulla il carico della GPU, mentre ora la sovraccarica moltissimo. Disattivando l'AA sono tornato esattamente alla situazione di prima (ovvero 60-130 FPS a seconda dei punti di vista nella Instant Action Spring dell'A10). Ho visto che fino a 4x il carico della GPU resta tollerabile (nonostante sia molto superiore a prima anche se usavo 16xA CSAA), di conseguenza per ora anche se con gli spigoli un po' seghettati riesco a volare con gli FPS di prima... Speriamo che arrivi presto la patch...

Anti-aliasing makes FPS drop!!! Regarding the FPS problem, the cause is indeed in anti-aliasing! :mad: I did a lot of testing in the past days (on 1.2.0) with MSI Afterburner and CPU monitoring tools always opened on my 2nd monitor while trying to overclock my i7 2600K and 680GTX at their top and I created some benchmarking situations to get a hang on the performance I was getting while OCing. Today, in the same situations, my GPU was always working at 97-98% (even in outside views) when before updating it used to run at 70-80%. Selectively deactivating the features in my nVidia control panel I finally got back to the old FPS with anti-aliasing set to OFF. Probably something was changed to the AA handling in the code and is now uselessly overloading the GPU, where before it made a 1-2% difference going from no AA to 16xQ CSAA now puts a 20-30% stress on the GPU. I hope the guys at Eagle Dynamics are aware of this and will provide a patch soon. Now the only option is flying with AA at 2X or 4X to get the minimum impact on FPS... :doh:

Thank you Frogisis. I'll try to work out what is causing the FPS drop tonight changing various settings...

Hi, what are your system specs please? Maybe the FPS problem is just nVidia related? My system is: - ASUS Sabertooth Z77 - i7 2600K OC @ 4.8GHz - 16GB RAM 1600MHz - PNY nVidia GTX680 2GB VRAM - Samsung SSD 256GB Before updating I had 60-80 FPS average in the first A-10 instant action mission, after update it's 30-40 FPS...

Your system specs?