OG84

From what I found on google, it should be a FZU-39/B radar proximity sensor (fuze). So it seems like it has a small radar for determining when to dispense. But what my shower type of question would be, how is that setting transfered to the bomb in dcs. Seems like in reality it is set directly on the bomb/fuse itself, outside by some ground crew. So no clue if changing this in the PACS ingame is actually changing the setting on the bomb itself. I assume same applies to the spin parameter which is probably manually adjusting some fins at the tail of the bomb. Probably values entered in PACS are just used for calculating the correct trajectory and drag and setting up the bomb has to be done by ground crew. But I could be wrong as I don't have any insights in any of those things

yep thanks, I already fixed it by using the native quad views and your Varjo Foveated enhancement. Performance is really nice. Better than anytime in the past.

ok thx. seems like there were quite some changes with native DFR which I wasn't aware of. That's why I couldn't fully make sense of what you were saying. Thanks for explaining.

hhm ok, yes I had Foveated Rendering enabled, which gave me quite some performance improvements. But it is part of the OpenXR tookit, so there was no third party app I was running in parallel. Will do some more testing with XR toolkit today... Edit: Just saw, that for DCS World and Aero you need this OpenXR-InstanceExtensionsWrapper listed on the compatibility page when running OpenXR tookit. Will give that a try.

I now also have the black screen with Aero, openXR toolkit companion app and Multithreading. But didn't play in a while, so can not say if it is related to the latest update. DCS Log: EDCORE (Main): (dDispatcher)enterToState_:1 2023-06-23 17:57:54.107 ERROR VISUALIZER (9600): xrBeginFrame 1000002243.851562 failed with error: XR_ERROR_RUNTIME_FAILURE 2023-06-23 17:58:05.828 INFO UIBASERENDERER (Main): Cannot load font [C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\dxgui\skins\fonts\]! 2023-06-23 17:58:05.828 INFO UIBASERENDERER (Main): Cannot create font [C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\dxgui\skins\fonts\] size 0! 2023-06-23 17:58:05.974 ERROR VISUALIZER (9600): xrBeginFrame 1000002243.851562 failed with error: XR_ERROR_CALL_ORDER_INVALID 2023-06-23 17:58:05.988 WARNING LOG (26260): 1 duplicate message(s) skipped. 2023-06-23 17:58:05.988 ERROR VISUALIZER (9600): xrBeginFrame 1000002243.851562 failed with error: XR_ERROR_RUNTIME_FAILURE 2023-06-23 17:58:05.991 ERROR VISUALIZER (9600): xrBeginFrame 1000002255.751543 failed with error: XR_ERROR_CALL_ORDER_INVALID Open XR Log companion app: [OXRTK] 2023-06-23 19:57:52 +0200: Creating swapchain with dimensions=2268x2268, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21 [OXRTK] 2023-06-23 19:57:52 +0200: Creating swapchain with dimensions=2268x2268, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21 [OXRTK] 2023-06-23 19:57:52 +0200: Creating swapchain with dimensions=2054x2054, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21 [OXRTK] 2023-06-23 19:57:52 +0200: Creating swapchain with dimensions=2054x2054, arraySize=1, mipCount=1, sampleCount=1, format=29, usage=0x21 [OXRTK] 2023-06-23 19:57:54 +0200: xrBeginFrame: XrResult failure [XR_ERROR_SIZE_INSUFFICIENT] Origin: m_openXR.xrLocateViews(m_session, &info, &state, 2, &viewCountOutput, eyeInViewSpace) Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\vrs.cpp:234 [OXRTK] 2023-06-23 19:58:06 +0200: xrBeginFrame: XrResult failure [XR_ERROR_SIZE_INSUFFICIENT] Origin: m_openXR.xrLocateViews(m_session, &info, &state, 2, &viewCountOutput, eyeInViewSpace) Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_MBUCCHIA_toolkit\vrs.cpp:234 I will debug a bit and see if I can find a solution... EDIT: ok after reinstalling varjo base and disabling openXR toolkit, DCS is working gain. Probably there is some incompatible openXR setting in my toolkit config.

I assume you have also tried pressing the "5" key on the numpad? Should be the DCS recenter button.

Steam, Varjo Aero, 13900k, 4090 User here. After updating and first MT start I got the following error in the logs: ERROR VISUALIZER (27432): xrBeginFrame 1000009404.352429 failed with error: XR_ERROR_RUNTIME_FAILURE To fix this, I had to disable OpenXR compatibility in Varjo Base. Otherwise DCS didn't render anything. Now it seems to work perfectly. I even getthe OpenXR overlay from the companion app, which is strange, because i thought it should be disabled now. But anyway it works now and performance is really good so far. But could also be due to the fact that with the openXR companion app I have enabled Fixed foveated rendering and NIS scaling and stuff. Also created a quick start mission with max. number of red and blue AIs, and performance is still between 80-90 fps. I will keep an eye on it and do some more testing.

thx for the info. same issue here. Also in the other flightsim.

For me there is also something wrong with the Pro 2. I have the feeling that the eyes in dcs are not correctly aligned. If I take off the headset, it feels like cross eyed for a short period of time. I hope this can be figured out with software updates. Edit: I returned mine. Maybe it was just my unit, but something didnt feel right. Also performance was not acceptable with 3090. Staying with the index for now

I don't agree at all dude I think you're shooting a little bit over the top. Except for the cloud jittering, for me this update is one of the best ones in a long time. (Valve Index)

yep thanks a lot. I get much less reprojection going on with 2.7. First thing i noticed is this performance increase. Hope the cloud jittering is on prio though. Also being on the ground in the first f16 red flag campaign mission is now finally smooth. But I'm on the very high end hardware wise, so will only speak for myself: Good job guys and girls!

Hi, not sure if this is of interest for you guys, but i just upgraded from a 3900x to a 5900x. Quite some improvement. Fyi is with a 2080ti. 3900x + 32GB CL16 3200Mhz cinebench r23: single: 1302 multi: 16732 dcs frametimes VR preset + Valve Index: p51 cold start krymsk: 10ms f18 super carrier cold start: 20,5ms (23 fps) --- 5900x + 32GB CL17 4000Mhz (running at 3800Mhz with Infinity Fabric (Fclk) at 1900), Fclk 2000 was not working with Asus X570 Gaming cinebench r23: single: 1599 multi: 20739 dcs frametimes VR preset + Valve Index: p51 cold start krymsk: 9,1ms f18 super carrier cold start: 15,5ms (23/45 fps)

just delete the dlc from disk manually. e.g. steamapps/dcs/mods/aircraft/... Or in steam manage your dlcs and uncheck them there.

Would be nice to have one Thread per AI if thats somehow possible :) That can scale nicely with Future cpu Gens. Keep up the good work. Gesendet von iPhone mit Tapatalk

yeah i think it's not about hardware, it's about code. i just disconnected my vr gear to see what kind of performance i get with my "good" system specs in 2d. 55fps with the supercarrier cold start mission (vsync off) 2080ti, 3900x, 32gb LOW preset settings, except shadow on low 1080p! So i would expect a little more from those specs tbh.

@grammaton There are a lot of nice VR features in the nvidia sdk :) But regarding single pass, i guess they are already working on a vendor agnostic implementation (https://forums.eagle.ru/showthread.php?t=269320&page=2). At least sounds like it. Also the predominance of the green team could possibly change with upcoming rdna2 from AMD.

yep noticed this too. I only hear the clicking sounds of the throttle itself, but no variation in engine sound. Maybe a very subtle change in tone, but very irritating in general :)

This is just a calculated value to point out the difference. dcs fps counter shows 22fps vs 45fps.

On the supercarrier cold start mission shadow has a huge impact. Between shadow off (8ms) and shadow low (18ms) there is a difference of 77fps (cockpit view) 2080ti/3900x

Would the i9-9900k mind to retest with super sampling 1.0?

thx, that was a typo. fixed.

Well my personal conclusion is, that a high end ryzen performs on the same level as a high end intel. That suprised me the most. Even with way less core clock. But 10900k is around the corner. though i cannot verify all results, except my own. Due to lack of more data I cannot give more conclusions at the moment ;)

updated...

Hi pilots, i would like to collect some data on which system components have the most impact on VR performance. That's why i would ask you to take part in the following voluntary survey (no personal data is collected, only system specs). E.g. what i would like to know if the latest high core count amd cpus perform better in a Steam VR environment than some older but fast single core cpus. I will share and present the results later, but you can already watch the current data yourself after you complete the survey. https://docs.google.com/forms/d/e/1FAIpQLSdp6019Z5WOcl4hUt9CUhVJqPSqHn0X-T4hhcSauc2oOkAxPQ/viewform thx :smartass: PS: you can also submit multiple times if you like, e.g. with different super sampling settings or core clocks Current Results (2.5.6.47404) super sampling 1.0-1.2 9.1ms (109fps*) -> Ryzen 9 3900x (12+12 core 4.1ghz oc) + 2080ti + 32 GB DDR4@1599 + Valve Index + super sampling 1.0 = 0.061 FPS per € 9.5ms (105fps*) -> i7-7700k (4+4 core 5ghz oc) + 2080ti + 32 GB DDR4@1596 + Valve Index + super sampling 1.0 = 0.062 FPS per € 10.1ms (99fps*) -> i7-9700k (8 core 4.8ghz oc) + 1080 + 32GB DDR4@1596 + Samsung Odyssey + super sampling 1.0 = 0.087 FPS per € 10.5ms (95fps*) -> i7-7700k (4+4 core 4.2ghz stock) + 2080ti + 32GB DDR4@1596 + Valve Index + super sampling 1.0 = 0.056 FPS per € 25ms (40fps*) -> i7-7700k (4+4 core 4.2ghz stock) + 1080 + 16GB DDR4@1500 + Rift S + super sampling 1.2 = 0.048 FPS per € 44ms (22fps*) -> i5-3570k (4 core 4.4ghz oc) + 1080 + DDR3 @1596 + Rift CV1 + super sampling 1.0 = 0.029 FPS per € super sampling 1.4-1.5 11ms (90fps*) -> Ryzen 9 3900x (12+12 core 4.1ghz oc) + 2080ti + 32 GB DDR4@1599 + Valve Index + super sampling 1.5 = 0.061 FPS per € 12ms (83fps*) -> i7-7700k (4+4 core 5ghz oc) + 2080ti + 32GB DDR4@1596 + Valve Index + super sampling 1.4 = 0.062 FPS per € 12.3ms (81fps*) -> i7-9700k (8 core 4.8ghz oc) + 1080 + 32GB DDR4@1596 + Samsung Odyssey + super sampling 1.5 = 0.087 FPS per € 12.6ms (79fps*) -> i9-9900k (8+8 core 4.9ghz oc?) + 2080ti + 64GB DDR4@1066 + Valve Index + super sampling 1.5 = 0.060 FPS per € 14ms (71fps*) -> Ryzen 5 3600 (6+6 core 4.2ghz oc) + 2070 + 32GB DDR4@1596 + Valve Index + super sampling 1.4 = 0.127 FPS per € * projected fps, just 1000 divided by frametime. Not necessarily the fps shown in dcs due to reprojection or other frame locking. * price per € = fps (ss1.0) divided by sum of current cpu, gpu and ram price Systems with most bang for buck: 1. Ryzen 5 3600 + RTX 2070 2. i7-9700k + GTX 1080 The frametimes shown, are only for the the TF-51D quickstart mission (cold start from krymsk). Also note the different super sampling settings. E.g. when I project the 9900k to super sampling 1.0, then it runs a 8,4ms frametime. The results do not represent the general dcs performance throughout all missions. There a probably other missions where gpu or ram size has a higher impact. Personal note: Although I have ~10ms frametime in this single player mission, I only have ~40ms frametime in multiplayer.

I would rather use the frametime from the steamvr widget as a metric for performance. FPS do not necessarily change in linear steps due to how vr works.