Mistermann

Here's the video that made it all come together for me. Until I watched this, I was pretty darn frustrated.

Not stupid at all! From first-hand experience, I can attest that OpenXR works with the Pimax. Like all things in the hobby of ours, there's a lot of nuance to that answer however. I tried it and the experience was less than desired. I don't remember the specifics, but my FPS dropped by something like 50% when compared to the SteamVR experience. I probably could have spent countless unproductive hours trying to diagnose the issues, but chose to switch back to SteamVR and fly. If you need any nudge towards the Pimax, I can definitely attest to the experience. I've had my headset for a couple of months, and wouldn't give it up without an altercation.

Prepare yourself for an amazing experience. I got the Pimax 8KX a couple of months ago. Coming from an Oculus Rift-S. I can attest that the FOV is worth it. At least in my opinion it is. I only have the Oculus to compare it against. However, my peripheral vision on the Pimax headset feels "right" to me. I wear glasses and the screens far exceed where my lenses stop - which is precisely my RL experience too. I couldn't be happier with my purchase. That video above will save you hours of frustration in setup and tinkering with DCS.

WOW! Thanks so much! I never would have guessed. Most appreciated

Indeed. And how I came to download this. Thanks for making this for us!

Except that I have it toggled off in my example. See image above. Maybe the toggle doesn't work? It makes sense that its a radar lock. File PM'd. Thanks.

Hey @Vyrtuoz - long time user here. I have your 64-bit Advanced version of the software. I have always wondered what the red dotted line represents in the product. I don't see a way to turn it off. Better yet, what's it represent? Can you shed some light on what this feature is telling us, please? I have done some significant internet searching in my attempt to answer this before asking here (including the Tacview site and this thread). Maybe I am missing something obvious - definitely a possibility. Most appreciated! Update: the dotted line does disappear when I am low (in this mission), so I am wondering if this is a radar tracking me (it makes sense if that's the case). An official answer would be very welcomed. Thanks!

YMMV here. Speaking from first hand experience, I experienced horrible drifting with just a single base station. I had to re-center the VR view every 5-10 seconds. For me, it was unplayable. A buddy of mine (original Pimax 8K kickstarter backer) told me he had the exact same issue and a second base station solved that problem for him. I ordered a second base station and the Pimax has been rock solid ever since. I only use the Pimax for DCS. I don't use any hand controllers. Also, if you have any questions on Pimax setup in DCS, this guy's video saved me hours. I got lucky and used all his settings. Pimax is smooth.

Thanks for all this work, cfrag. I tried your "demo-player score" demo mission yesterday and it crashed DCS (latest OB). I will pull together the logs and messages and get them over to you after testing again with this latest version.

@toutenglisse - I hereby nominate you for DCS Forum All-Star award! Sir, you are absolutely one of our most helpful members. Thanks for being awesome! I was just looking for how to do this very task in the ME. Thanks to this thread, I have it working in 5 minutes instead of the hours it would have taken to figure out the UNCONTROLLED check-box.

Back in June of this year I was looking into those numbers trying to figure out if they were warhead weights, TNT equivalence or something else. Based on some searching, it appears to me that these are supposed to represent the warhead's TNT equivalence in kilograms. I have two back to back entries that discuss my findings. Hope this helps.

@cfrag Sir, this is brilliant. I am late to this party, but do use the standalone debugger. I have created personal missions for many years and consider myself between intermediate and advanced from a ME usage standpoint. I don't write much lua but use mist and moose to boost my missions where needed. BTW, I always wondered how people used that box at the bottom of the trigger zone! Now I know. I am downloading dml and consuming the documentation. Admittedly I am a little apprehensive and wonder what the learning curve will be. I feel like I've already learned the foreign language of the ME and wonder if I'll struggle unlearning/relearning. This is a "me" (not mission editor) issue and not a criticism on DML. I hope ED is following this concept. IMHO we need a more accessible ME so mortals not named Baltic Dragon or Reflected can create compelling missions. It appears you've unlocked a significant amount of capability for those of us who want to build missions like LEGOs. Thank you for all your efforts! Looking forward to diving into the docs and giving some of these concepts a test drive or two. This old dog is looking forward to some new tricks!

Does the INS BIT ever say anything other than "NOT RDY" for you guys? I suspect I am just getting confused by that and attributing my poor skills with JDAM and ATFLIR with alignment issues. @BIGNEWY - can you confirm that the INS BIT is not working properly at this time in EA? Thanks

I have done a bunch of forum searching before posting this. Unfortunately, I haven't found an answer. Even checked Chuck's guide. When doing a cold start (land or sea), my NAV BIT for INS shows "NOT RDY". I believe I am aligning the jet properly, but at this point, I am starting to question that statement. Here's what I am seeing. From a cold jet on the carrier deck, I startup the engines and then turn my attention to the INS alignment. Step1 - Set INS knob to "CV" Step2 - Turn on STD HDG on HSI Step3 - Wait for QUAL:0.5 OK Step4 - Set INS Knob to IFA (yes, I am flying a mission in the GPS era) Step5 - Check NAV BIT QUESTION: Shouldn't the INS BIT now be something other than "NOT RDY"? The reason I ask is I flew a mission this morning after doing these steps above and my JDAMs were not accurate, nor was my targeting pod (it seemed to think targets were not where I marked them with the HMD (I did align that as well before flight)). I am starting to wonder if my INS alignment is incorrect. Sure this could all be piloting mistakes by me, but that NAV BIT is nagging at me. Am I missing a step in INS Alignment somewhere? Thanks.

Thanks - I was being visually challenged that day!

Just in case people have any difficulty finding the great mod, its in the DCS-Downloads-User Files https://www.digitalcombatsimulator.com/en/files/3301042/

Initial experience ... I am absolutely sure this is a "me problem". I followed the instructions in this video which make it appear there's really nothing to do but install a couple of programs, double click and voila everything works great. Unfortunately for me, my experience was very poor. My SteamVR FPS sits around 45 in the Hornet Free Flight mission. It drops to 20 when using OpenXR as outlined in the video above. I am sure there are tweaks I need to do in openxr somewhere, but I just didn't have the patience to tinker and waste a bunch of time just to get a few frames here or there above what SteamVR is currently delivering. @edmuss -- how much "better" do things get? I am definitely willing to make the time commitment if there are significant improvements over SteamVR. Right now, its all relevant to this virtual pilot - Pimax experience blows my old Rift-S experience away. AND, I have a long term VR headset that likely won't be fully realized until my next PC upgrade.

I think Rudel_chw is asking a great question. What specific features from the Tornado ME are you looking for? I am all for improving the DCS ME as part of the general maintenance of DCS world.

This bug has been around for years. There's plenty of evidence showing what's happening and I appreciate ED acknowledging the problem. For now, I've learned to "game" the system by applying power just before landing that pushes the AoA back up countering the FM defect. I hate that I've allowed myself to do this over the years because I am going to have to "unlearn" this bad habit once this defect is finally resolved. At this point, I think our choices are to 1) Game the system, 2) Ignore the LSO's grade. There may be a 3rd option of using scripting like MOOSE and use the AIRBOSS routines (I haven't done that, so YMMV). Anyway, @BIGNEWY posted in the thread I linked above (April 2022) that the team knows about the defect and will "tweak" it. As for "when" - only the ED program managers know the answer.

I'm almost afraid to ... Next up - me flying the heck out of DCS for a few days. THEN I'll play with openxr.

@Devil 505 OMG - THANK YOU!!! Seriously ... thank you for that video. I spent my lunch hour watching every second and taking notes. I configured my system the exact same as you (we have almost identical systems). It ROCKS! You have saved this DCS old timer some significant heartache and pain. DCS has never looked so good. The FOV of the Pimax is a complete game changer. This is coming from a guy that felt VR, in general, was/is a game changer. The first time I experienced the sim in VR was a day I will never forget. That day has been replaced with the first time I experienced DCS in VR on a Pimax. I wouldn't be saying this without your advice contained in that video. Sir, I salute you!

Thank you @edmuss and @Devil 505. Devil, I will check those vids out ASAP. Thanks for taking the time to post those videos!

Exactly. I'm beyond the baseline at this point. I am trying to understand where I manipulate the resolution outside of DCS and PiTool. Is the SteamVR setting above the place to manipulate?

Please forgive the newbish question here. I am just not familiar with the SteamVR or Pitool options and what they do. With my Rift-S I'd set the DCS PD to 1.0 and then upped the supersampling to 2.0 in the Oculus toolkit. Where should I be fiddling with the supersampling? In SteamVR and leave DCS PD at 1.0??? Is that this setting here? Thanks!!

I was able to play around a bit and my FPS at a DCS PD of 2.3 was 20-25. Yeah, that's no good. My Rift was usually no less than 30 and closer to 40 for most high altitude flights. For me, its less about the numbers and more about the experience. Right now, I have the DCS PD set to 1.4 and am getting between 30-40FPS. BUT my FOV is greater and it feels like the cockpit is in sharper focus. I could live with this for the foreseeable future, but feel I should try and squeeze out some additional performance. I will continue to play with the settings. I can always revert back to where I am right now. @WipeUout - I haven't tried any of your suggestions yet. They are next on my list to try. I can't imagine trying to figure all this out on my own. Thanks to all of you active participants in the community!