chev255

What about night flying? I have been struggling with the blacks being really greyish, I have tried to decrease brightness to the minimum and it's a bit better but not great. I assume nothing we can do about it?

Change resolution of cockpit displays to 1024 and you will see a big difference

I would say 7800X3D is probably the most sensible option. But the 7950X3D allows you to run all other processes (voice attack, kneeboard, varjo base, etc.) on threads 16-31 which should also help with performance. So it all depends how much of a big deal is it for you to spend the extra $250

DCS FPS counter indications are wrong, I have never seen anything else than CPU limited, even when it is clearly GPU WHat GPU do you have?

I use process lasso (free version). When not setting any affinity, even though I set DCS as a game in the game bar, it was still loading threads 16-31 so it is worth using lasso. I am told in lasso it is better to use "CPU set" than affinity. EDIT: also I use lasso to move all processes other than DCS to threads 16-31

Just upgraded from a 9700K (all core 5GHz) to an 7950X3D. Video card is 4090. I did not do any proper benchmark but with Varjo Areo and lower resolution, to be CPU limited, I got the following at the start of Hornet Syria airbase defense mission, on the ground: 9700K - 45fps 7950X3D - threads 0-31 - 58fps 7950X3D - threads 16-31 (non 3D cores) - 61fps 7950X3D - threads 0-15 (3D cores) - 85fps So I am very happy with the 39% increase of the 3D cores versus non-3D!

Well some of the benchmarks above made me hesitate but on "the other sim" the 7800X3D and especially the 7950X3D are way better than the 13900K so I just pulled the trigger last night and will get the 7950X3D!

Sorry Everest I should have updated the topic, I reinstalled windows and that fixed the issue somehow! Thanks for your help

I have 9700K (all core 5Ghz) and used to have a 2080ti that I just replaced with 4090. Using the MT version and Pimax 5K+ (1.5 super sampling) I am GPU limited. So it all depends if you play in VR or "2D" screen

trevoC, I would like to encourage you to continue sharing as there are many of us who are looking for info on how 7950x3d performs. Unfortunately we sometimes become a little too passionate Myself I have a 9700K and a 2080Ti from 2018 and I am trying to figure out whether to go 13900K or 7950X. Since MT just halved my CPU frametimes I just pulled the trigger on a 4090 that I can use on my current build until I figure the CPU out. Last time I bought an AMD was 2005 and I wouldn't mind doing it again but all the discussions about core parking kind of worry me. Cheers

Hello - could you confirm which memory you have? I was interested in the Asus B650E-F but there was no 64GB DDR5-6000 in the QVL

Hi everyone, first thanks a lot mbucchia for PimaxXR and Everest for this topic! I am coming back to DCS and VR after a few years and I am not able to get my 5K plus to work... I have Pitools version 284, OpenXR toolkit 1.2.4, Pimaxxr 0.3.2 and OpenXR Explorer 1.0.25. I have added "--force_enable_VR --force_OpenXR" to my DCS shortcut. When I start DCS, it goes to the normal menu (not VR) although the screen aspect ratio is matching the Pimax. Nothing can be seen in the Pimax other than the "Pimax home" landscape. When I look at logs I find an "XrResult failure [XR_ERROR_RUNTIME_FAILURE]". I have tried restarting the pimax, rebooting, reinstalling, etc. 1- PimaxXR log 2023-03-06 17:29:14 +0800: PimaxXR - v0.3.0 2023-03-06 17:29:14 +0800: PVR: 1.23.1 2023-03-06 17:29:14 +0800: Hidden area mesh is not enabled 2023-03-06 17:29:14 +0800: Application: DCS World; Engine: 2023-03-06 17:29:14 +0800: Device is: Pimax 5K Plus 2023-03-06 17:29:15 +0800: PVR: 1.23.1 2023-03-06 17:29:15 +0800: Hidden area mesh is not enabled 2023-03-06 17:29:15 +0800: Application: DCS World; Engine: 2023-03-06 17:29:15 +0800: Requested extension: XR_KHR_D3D11_enable 2023-03-06 17:29:15 +0800: Requested extension: XR_KHR_visibility_mask 2023-03-06 17:29:15 +0800: Requested extension: XR_EXT_hand_tracking 2023-03-06 17:29:15 +0800: Requested extension: XR_KHR_visibility_mask 2023-03-06 17:29:15 +0800: Requested extension: XR_KHR_win32_convert_performance_counter_time 2023-03-06 17:29:15 +0800: Device is: Pimax 5K Plus 2023-03-06 17:29:17 +0800: Recommended resolution: 2562x2106 2023-03-06 17:29:18 +0800: Using D3D11 on adapter: NVIDIA GeForce RTX 2080 Ti 2023-03-06 17:29:19 +0800: xrCreateSwapchain: pvrResult failure [1] Origin: pvr_createTextureSwapChainDX(m_pvrSession, m_pvrSubmissionDevice.Get(), &desc, &pvrSwapchain) Source: D:\a\Pimax-OpenXR\Pimax-OpenXR\pimax-openxr\swapchain.cpp:400 2023-03-06 17:29:19 +0800: xrCreateSwapchain failed with XR_ERROR_RUNTIME_FAILURE 2- OpenXR log [OXRTK] 2023-03-06 17:29:14 +0800: OpenXR Toolkit - GA-2 (v1.2.4) [OXRTK] 2023-03-06 17:29:14 +0800: dllHome is "C:\Program Files\OpenXR-Toolkit" [OXRTK] 2023-03-06 17:29:14 +0800: OpenXR-Toolkit layer is active [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_KHR_D3D11_enable [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_KHR_D3D12_enable [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_KHR_vulkan_enable [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_KHR_vulkan_enable2 [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_KHR_opengl_enable [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_KHR_composition_layer_depth [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_KHR_win32_convert_performance_counter_time [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_KHR_visibility_mask [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_FB_display_refresh_rate [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_EXT_hand_tracking [OXRTK] 2023-03-06 17:29:14 +0800: Runtime supports extension: XR_EXT_hand_joints_motion_range [OXRTK] 2023-03-06 17:29:15 +0800: Application name: 'DCS World', Engine name: '' [OXRTK] 2023-03-06 17:29:15 +0800: Using OpenXR runtime PimaxXR (Unofficial) 0.3.0 [OXRTK] 2023-03-06 17:29:15 +0800: --> aSeeVR_connect_server(5347) [OXRTK] 2023-03-06 17:29:17 +0800: <-- aSeeVR_connect_server -1 [OXRTK] 2023-03-06 17:29:17 +0800: Using OpenXR system Pimax 5K Plus (aapvr) [OXRTK] 2023-03-06 17:29:17 +0800: Using OpenXR resolution (no upscaling): 2562x2106 [OXRTK] 2023-03-06 17:29:17 +0800: Using OpenXR resolution (no upscaling): 2562x2106 [OXRTK] 2023-03-06 17:29:19 +0800: Using Direct3D 11 on adapter: NVIDIA GeForce RTX 2080 Ti [OXRTK] 2023-03-06 17:29:19 +0800: Early initializeInterceptor() call [OXRTK] 2023-03-06 17:29:19 +0800: xrCreateSession: XrResult failure [XR_ERROR_RUNTIME_FAILURE] Origin: OpenXrApi::xrCreateSwapchain(*session, &swapchainInfo, &m_menuSwapchain) Source: D:\a\OpenXR-Toolkit\OpenXR-Toolkit\XR_APILAYER_NOVENDOR_toolkit\layer.cpp:830 [OXRTK] 2023-03-06 17:30:45 +0800: D3D11Device destroyed I have attached a few screen captures. I have spent several hours now but it seems that I am missing something - appreciate your kind support1 Thanks

Super Mirage 4000 (anyone remembers it?) first flew in 1979 and already had canards + delta wing

I understood it differently, that there would be no animation but does not mean no capability to transport (same as Huey for instance)?

Wow, great video!

Naquaii, I am eagerly waiting to see the capability to guide 6 AIM-54 simultaneously in TWS - have not seen that in any of the videos/streams. Is this possible in the current state of the module?

Great to hear!

I wonder if we will also get an alert 5 / alert 15 quick start on carrier? Need to have a stressed-out Jester rushing the checklist for these :)

I noticed on Ralfidude's stream yesterday that he has the F-15E icon on main menu :music_whistling: https://www.twitch.tv/videos/365920218 (look at 05:30) EDIT: he then just clarified this was just a mod :(:(:(

To me it is related to the book "Bye bye baby" about the Tomcat https://www.amazon.com/Grumman-F-14-Tomcat-Reminiscences-Service/dp/0760339813. I think they used some pics from that book in an older update ("cats and ducks" update if I recall correctly)

"get velocity vector around around first or second wire" you need to fly the ball (IFLOLS), not use the FPM/VV

Same here :(

Just need to open canopy so that the ground crew can "hear" you

Agreed, that's a pretty big omission! :D I live in Dhahran just across the bridge so would love to see at least the Saudi Air Force Base added.

^ This! I am not much interested in aircraft with SSM but it would totally make sense if it was giving us a "starter pack" for a famous conflict - to be eventually complemented by full fidelity modules.