Search the Community

Sometimes the new problem is just an old problem repackaged. Switched from another anti-virus vendor to BitDefender. No problems until trying to play DCS with my Pimax 8KX in VR. Nope. Nope. More nope. Starting through the troubleshooting list provided by Flappie, (a most excellent resource by the way) I discovered that in changing over from one anti-virus to the next it turned on parts of my Windows Defender. That wrecked everything with lower FPS and random crashes. Windows everything off. Problem solved. Sometimes the new is really the old. Hopefully this saves someone out there some aggravation. - Richrach

Are you ready to showcase your skills? All entries will have the chance to be featured on Pimax socials with their winning rig photos and dogfighting tips. Plus, every valid entry will receive a $10 USD discount code for Pimax accessories! Eligibility: Open for everyone! Submission Requirements: File Format: JPEG or PNG for Rig Setup ; Video format for Killshot momenth Originality: Must be your own work Uploading Instructions: Reply to this forum post and attach your submission. For other platforms, include the hastag and a valid link to your post. Deadline: Submit your entry by November 30, 2024 at 23:59 UTC Judging Criteria: Creativity: Originality and storytelling Relenvance: Your proud moment Visual: Clarity, impact and simplicity Terms and Conditions: Pimax may use your entry in promotional materials. You will be contatcted via the forum to claim prizes. Multiple entries are allowed. If you want to join the 1v1 Dogfighting competition, please register here:

Hey Folks, Curious if anyone using Ultraleap or VR in general has a VR keyboard they have implemented as part of their rig? I have a small hand-held keyboard I have on my kneeboard leg that I am trying to use, but without seeing the keys, it's kinda too small to hunt and peck. Any thoughts? I really want to use it as data input or chatting rather than keys. Or maybe even Voice to Text Options available? Thanks! -Chris Here's the mini keyboard I am using: null

does Pimax have a LUA they install for the HMD. I am having massive frame drops and was thinking a LUA file for pimax might be the problem everything works fine except DCS VR .steam home other VR no issues just DCS

I have been testing my VR configuration/stability & visual improvements with my Pimax5k Super HMD since DCS provided OpenXR support. At first, tests where KO and could hardly just get to the flight phase. But a recent break through has occurred and has changed the testing results by 180 degrees for the better. The big game changer happened yesterday when I found out that the OpenXR Toolkit was revised to v1.2.4. to improve usability with DCS OpenXR implementation, see note 1. I will spare you the testing details and jump directly to some results/configurations that work for me. Hardware configuration: (if you wish to compare, here are my PC details) Mobo: MSI X570-A PRO/PCIe 4 CPU: AMD RYZEN 9 3900X (12 CORE) GPU: EVGA-RTX 3080Ti RAM: DDR4-32 GB (3200MHZ wt XMP) HMD: PIMAX-5K SUPER Software configuration: DCS World Open Beta v 2.8.2.35759 (latest as of 3 FEB 2023 & wt OpenXR support) PiTool v1.0.1.284v - Version 284 is required as per PimaxXR requirements. See note 1. PimaxXR v0.3.0 - This app is the runtime required for OpenXR to work with PiTool and to bypass SteamVR. PimaxXR runtime is needed to avoid PiTool kick starting SteamVR by default. Install PimaxXR and make sure that PimaxXR is selected as the OpenXR runtime. See note 2. OpenXR Toolkit v1.2.4 – Latest version as of 2 FEB 2023. See note 3. OpenXR Explorer v1.4 - Optional application to analyze OpenXR runtimes & OpenXR Toolkit app that is installed. Not required for success in implementing OpenXR with DCS. See note 4. OpenComposite - This application and its DLL implementation into DCS is not required for success in implementing OpenXR with DCS. However, you may need it for other VR games or simulators that are designed to use the SteamVR app to run them in VR. See note 6. Recommendations: Always make sure that the PiTool app is UP and running regardless of what VR runtime (SteamVR or OpenXR) you use. Otherwise, your Pimax HMD is not available for your VR sessions. If you have configured a DCS game start icon in PiTool and wish to test OpenXR runtime, avoid using that game start icon. Starting DCS from the PiTool/My games/DCS icon will kick start SteamVR. Having DCS started via SteamVR while OpenXR is configure for the game will likely cause undesired results. If you are going to run or test DCS OpenXR VR method (bypassing SteamVR), for safety, just delete the game start icon in PiTool as you will not really need it anymore. Instead, do the following… Exploit the DCS command line features to start the simulator as these will be useful to you. Make yourself some DCS game start window shortcuts to facilitate things. Here are some windows shortcut command line targets that I use. Make a DCS game start shortcut for each of the following shortcut targets & see note 5 for other DCS post link; "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR - to start DCS with OpenXR support. Make sure that SteamVR is not running. Make sure that OpenXR Toolkit is enabled. At first, use the default Toolkit shortcuts. Also, make sure that active OpenXR runtime is ticked back to OpenXR within the PimaxXR app. This will enable bypassing SteamVR and will avoid SteamVR from being called. "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_SteamVR - to start DCS with SteamVR support. If you revert back to using SteamVR, make sure that the OpenXR Toolkit is disabled (tick the disable switch in OpenXR Toolkit) and that active OpenXR runtime is ticked back to STEAMVR within the PimaxXR app (start PimaxXR app and select SteamVR as the runtime). "your game install path\DCS World OpenBeta\bin\DCS.exe" --force_disable_VR – to start DCS without VR so that DCS displays on your primary display screen. This could useful for HOTAS configuration, etc. Without guaranties, this methodology should work for Pimax4k, 5k or 8k HMD owners. Can all these pieces of software & apps co-exist at the same time on your PC. YES, however, configuring the apps correctly is required if you wish to use DCS with SteamVR or with OpenXR. See comments above depending on the shortcut command lines that you are using to start the DCS simulator. You need to experiment with the OpenXR Toolkit settings. Do that using the Toolkit shortcuts while in the game. Settings will likely vary if you have a Pimax4k, 5k or 8k HMD. When your satisfied with your Toolkit settings, share them with the community by writing your own post. Using OpenXR... Generally speaking, I am getting better control of my FPS frame rates, better control of color effects and better control of sharpness inside the cockpits. I do experience a bit of stuttering when switching from F1 to F10 and back to F1 views...not sure what would cause that. So far, multiplayer seems OK. Could the experience be better...YES. Correcting the stuttering when changing views needs to be addressed but I am not sure to who I should shot the requests ...to DCS regarding their OpenXR implementation, to the PimaxXR folks dev team or to OpenXR Toolkit dev team...don't know! Hope this helps you enjoy OpenXR with your Pimax HMD. Everest…Out! Notes: 1- For PiTool v1.0.1.284v, see https://community.openmr.com/t/pitool-1-0-1-284v/39823 2- For PimaxXR v0.3.0, see https://github.com/mbucchia/Pimax-OpenXR 3- For OpenXR Toolkit v1.2.4., see https://mbucchia.github.io/OpenXR-Toolkit/ 4- For OpenXR Explorer v1.4, see https://github.com/maluoi/openxr-explorer/releases/tag/v1.4 Be aware that this app is not required for OpenXR implementation with DCS. It is included here as reference only and is recommended for folks that do application development work. 5- For DCS news letter regarding OpenXR implementation, see the following forum post: https://forum.dcs.world/topic/318004-dcs-now-supports-openxr-natively/ 6- For OpenComposite & OpenComposite switcher, see https://mbucchia.github.io/OpenXR-Toolkit/opencomposite.html Note that no revision is mentioned for OpenComposite probably because this is actually a DLL which did the work of throwing DCS VR runtimes to PimaxXR before introduction/support of OpenXR in DCS. OpenComposite solution is no longer required to operate OpenXR in DCS. PS...If you like this post, please rate (@ top of post) or like it...

I did the firmware update today for the Pimax Crystal Sim. I'm on v1.3.0_au0221 with client 1.18.02.01. Sometimes when I launch I get constant movement in the hangar. I have to force stop DCS when that happens. Other times I get the cockpit moving all around when I pan the headset around. Fix: I did a slow repair. Launched into a Viper mission with success. I also tested QuadViews with Turbo Mode in PimaxXR, and it is back to working smoothly.

Date: April 15th Time: 11:00 AM PDT Where: Pimax.com & PimaxVR@Youtube

Input on a moderate system that may help others without the big pockets needed for a RTX 4090 GPU. System: i5-12400F (Overclocked to base 4GHz, manually set to all cores, turbo mode off) RTX 3070 (Overclocked GPU 2115Mhz (+200MHz), VRAM overclocked to 8Ghz (+1000 MHz) 32GB DDR4 RAM Pimax 8K+ (No base stations, 9-axis) MSI Z690 Pro WiFi DDR4 Motherboard Results: Syria map, heavy mission with high load of aircraft, vehicles, and static objects Cockpit view (A-4 Skyhawk) - 43-51FPS (Lower values only momentary. Majority of time is 48-50FPS) External view (F2) - 36-51FPS (HIGHLY dependent on what one is looking at. Planes in flight upper numbers. Helos on ground or aircraft taxiing lower range FPS) Vehicle view (F7) - 35-53FPS (HIGHLY dependent on what is going on in the view. Simple vehicles/static objects, no problem. Combine moving vehicles, explosions, firing, flames, aircraft flying overhead and the frame rate hits the lower end occasionally.) NVidia Settings: Image scaling - Off Anisotropic filtering - App controlled (***Make sure you have only one program doing this function. It is easy to slip up and have several programs selected to do the same thing!***) Antialiasing - FXAA - Off Antialiasing mode - App controlled CUDA- GPUs - All Max frame rate - Off MFAA - Off Texture filters (in order) - Off/Allow/High performance/On Threaded optimization - On Triple buffering - Off Vertical sync - Off VR pre-rendered frames - 1 OpenComposite settings OpenXR OXRMR settings: Rendering custom scale - 115% (***Make sure you have only one program doing this function. It is easy to slip up and have several programs selected to do the same thing!***) Motion reprojection - Disabled Pimax settings: 72Hz FOV - Normal Render quality - Custom 1 Fixed foveated rendering - Balanced Parallel Projection selected OpenXR toolkit: Upscaling/sharpening - CAS Sharpening - 50% Fixed Foveated Rendering - Off (***Make sure you have only one program doing this function. It is easy to slip up and have several programs selected to do the same thing!***) Turbo mode - On Post processing - On DCS settings (off unless otherwise listed): Textures - Medium (cannot see more detail at high setting) Terrain - High Water - Med Visibility range - Med Shadows - Med Res cockpit - 1024 (really cannot tell difference between this and 512) MSAA - 4X (GREATLY reduces shimmering in headset. I have tried all combinations of rendering levels in DSC/Pimax/OpenXR, SSAA, MSAA. For whatever reason, this seems to work best on my system. ***Make sure you have only one program doing this function. It is easy to slip up and have several programs selected to do the same thing!***) Clouds - Low Clutter/grass - 500 Forrest Vis - 50% (Syria map has WAY more trees that the Golan Heights has in reality. I turned this down just to make it more realistic. Higher settings do not seem to impact FPS. Literature indicates the trees are actually still there at lower settings but not rendered to the screen) Forrest details - 1 Scenery details - 1 Preload radius - 100 Chimney smoke - 1 Anisoptrophic filtering - 8x (***Make sure you have only one program doing this function. It is easy to slip up and have several programs selected to do the same thing!***) Terrain object shadows - Flat Rain droplets - On VR density - 1.0 Force IPD distance 40 (I flew the A-4 in real life. Setting this to 40 gives my eyes the same perspective I had in the actual cockpit. Your mileage may vary) I have spent many hours working all the settings. Much of what goes into making DCS perform at its best is FM (Freakin' Magic) and pure trial and error. Take my inputs with a grain of salt. I hope these give you at least a good place to start from. Good hunting, Richrach USN(ret) Actual aircraft flown: TA-4J, F/A-18, F-16, B-52, SH-60B, SH-3, E-2C, EA-6B (among many others)

I've been thinking about my future PC and VR headset upgrade. For VR, I've been look at the Pimax Super QLED and Micro-OLED. There also the option to get both in one package. I just watched an update from Pimax on YouTube and they said the QLED will be available first with a 50ppd lens while they also talked about a 57ppd lens being developed. I'm assuming that the 57ppd is for the OLED. Which do you think would look better in DCS? YouTube Pimax Crystal Super Update

Download here: QuadViews Companion (digitalcombatsimulator.com) V 1.0.2 (updated) - NET5.0 support Quadviews Companion makes modifying the settings within mbucchia's implementation of QuadViews a breeze! mbucchia's QuadViews is an essential download if you fly in DCS, and you have eye-tracking capabilities. However, for many, the settings.cfg file setup and modification can prove difficult when trying to find the best Dynamic Foveated Rendering settings for DCS. This handy utility not only automatically creates the initial QuadViews user settings file, but lets you load, modify, and update the settings without needing to open the config file at all. See https://github.com/mbucchia/Quad-Views-Foveated/wiki for further details. Works with Pimax Crystal, Pimax 12k, and Varjo Aero, Varjo XR3.