AMBUSH

JESTER needs call out the waypoint number he is switching to when he updates the nav at waypoint passage. When flying along a chain of waypoints JESTER will correctly update the waypoint to the next one in the sequence at waypoint passage, but he just calls out that the nav is updated. Unlike a human WSO JESTER does not say which waypoint is not selected which makes if very difficult to know that you are approaching your IP at Waypoint 7 for example. This is also very useful information to know when doing canyon runs because the pilot could then now which type of turn is coming up next

I am experiencing this issue as well. Jester menu is cut in half with left side visible and right half is cut off. Menu items are there and can be activated, but the menu items are not visible

Usually there are at least three: Side A, Side B and the Reality/Truth Side. The Reality/Truth Side rarely matches either of the others completely but will tend to be closer to one than the other.

@Flappie I am also have this same CDT and before now I have very rarely CDT (maybe 1 per month at most). Looking at the forums it would seem that it has become a MUCH more common crash experienced by quite a few people. I have attempted the recommendations you have made in several other forums posts including the no mods, clean install of DCS, TDR changes, pagefile changes, memory and SSD scans for errors, no overclocks on cards and recreating my Saved Games. The crash is VERY repeatable with flights on in the Syria F-15E instant action mission that is bomber intercept (I am not at my DCS machine to find the exact name but will update later) which is not an intense mission as far as unit count or high detail models. -forgot to mention that I have also completely deleted and cleaned then reinstalled the 2 previous versions of the NVIDIA drivers for my GPU and tested with them also

I am seeing extremely huge smoke plumes also. They look many times larger and darker than the original pics in this thread Was actually going to look in the files to see if it could be cut down a bit.

You need to limit the FPS for the Pimax 8KX to be just below the Hz of your headset (my 8KX is at 75Hz and I limit it to 72fps, if you have a 90Hz headset 85-88fps should work) using OpenXR Toolkit. When the Pimax software gets FPS saturated the tracking goes wonky. I recommend running the Pimax 8KX on the PimaxClient 1.10.0 with PimaxXR 0.3.4 and OpenXR Toolkit 1.3.2

Not a fix, but I have found that if you set the mission time to winter (even if the temp is not cold) the objects show up on FLIR much better. It is a work around I have used until the everything has FLIR thermal textures. That being said, ED does need to get this corrected as it was something that has been stated known since the announcement that the Apache would require better thermal textures and the first iteration of the new FLIR

See this thread. PimaxXR does work but there is an issue on the menus when it becomes GPU bound. There is a work around by setting a max FPS

I had this issue with a Pimax 8KX. My solution is to limit the FPS to just below what your HMD can handle to prevent GPU Limit. See linked post

The issue seem to happen when the multi-threaded system becomes GPU bound. I have used OpenXR Toolkit to impose an FPS limit of 70 FPS (my PIMAX 8KX is older and only does 75hz) With that FPS limit setting the menu screen is stable and does not devolve into spinning views. I have loaded in multithread and played singleplayer and connected to two online servers and all was stable Reporting to ED and continued investigation is needed to find the root cause but that appears to be be a usable workaround at the moment

QUOTE: 2- For PimaxXR v0.3.0, see https://github.com/mbucchia/Pimax-OpenXR There is a version 0.3.1 from mbucchia of the PimaxVR tool that solves some issues a few people had, but he has not released it on the github yet. PimaxXR_0.3.1.msi

You have a newer headset than I do. Mine is an old (like early model) one before they were able to do 90Hz

Download PiTool 1.0.1.284 here https://community.openmr.com/t/pitool-1-0-1-284v/39823 Here are the settings I am running.

What OpenXR dll are you placing in the DCS/bin folder? If you are referring to the Open Composite .ddl for manual installation, then you need to remove that. The new open beta version of DCS has OpenXR native and it is enable from the command line with --force_OpenXR

I run a Pimax 8KX and it works GREAT with the DCS native OpenXR Here is my setup: Pimax 8KX at 70MHz PiTool V1.0.1.284 PimaxXR 0.3.1 a beta from mbucchia that can be found on the OpenXR Toolkit discord (0.3.0 works also) Create a Shortcut to launch DCS with the following option on the command line: "G:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_OpenXR A few things to check first: If you used OpenComposite, disable/remove it (either in the OpenComposite app or remove the .dll if you put it in manually) Make sure Smart Smoothing and Parallel Projection are disabled Make sure the Pixel Density in DCS is set to 1.0 I have a thread on the OpenXR Toolkit discord with all of my settings and steps but it would occupy a lot of space here