DerKlausi

Only when looking around inside the cockpit or outside as well? If the latter, do you have bloom and lens effects set to OFF?

Hi all, just updated to the latest DCS patch 2.9.12.5336 (after skipping one or two?) and recognized that the 'dreaded' QuadViews focus area rectangle, previously only appearing with lens effects or bloom activated, is now also visible when looking around in the cockpit. It turns out this bug is exclusively linked to SSAO being turned ON. This is with Pimax Crystal OG but has been reported by at least one more DCS user with Varjo XR4. Would be happy to see this getting fixed soon, as SSAO makes quite a difference for me in visual experience. Cheers, DK

Two questions: 1. What HMD are you using? 2. What is your VR view direction/position in the menu screen after launching DCS, but before centering VR view?

It is very likely that this is caused by your flight sim seated position/orientation not being the same as you used to set up your (Steam)VR environment (room setup). Also make sure that both when you launch DCS as well as launch & activate XRNS, you're seated wearing your HMD exactly (!) the way you will be later during flight. Means: same seated height, same lateral and longitudinal position on chair or rig, same default forward looking direction, same HMD pitch angle. For example, when I put my HMD on my rig's seat and launch DCS/XRNS, XRNS will be off in a way similar to yours. I have to wear it on my head sitting with the rig already in the neutral instead of parking position (motion rig). Good luck!

How did you guys mount the Ultraleap 2 to the Crystal? Are you using it together with the Lighthouse faceplate? Cheers, DK

Question to you TQS owners: does your throttle have significant backlash? When I set mine to a medium to high friction resistance, the throttle grip moves like 2..3mm with the whole rod & friction brake assembly inside the base, before the rod itself starts to move in and out of the friction brake. Are you observing the same? Or did I get a faulty unit? Cheers, r.

Hey man - thanks a lot for your tireless efforts to get this great mod up and running again! I'm looking forward to giving it a spin this weekend!

Did you check proper OpenXR layer order? I'm running XRNS fine with varjo-foveated, OXRMC and OpenKneeboard when XRNS is the first being loaded. That is - at top of the list using fredemmotts OpenXR-API-Layers-GUI.

Sounds like an issue I had a while ago - did you check my post on how I solved it?

+1

In many programming languages, ";" ends a code line and "//" indicates the beginning of a comment. So anything on the above line after the double slash is just for documentation. I did not find the time to try the mod though, but please feel free to report back if you were successful! DK;

Thanks for the insight - I'll give that a go!

Thanks, much appreciated - let's keep our fingers crossed! For the time being - do you know of any other way to reduce the haze? Cheers, DK

Thanks a lot - I had already tried querying LoGetMCPState() substates but unfortunately with limited success. In contrast to what I expected to happen after being hit by an AIM120, I found that with the Viper, only LeftAileronFailure and/or RightAileronFailure will ever trigger. Maybe you are able to enlighten me on why that is? Cheers, DK

Would be great for others if you let us know the 'how'!

Thanks - I had already tried that, but unfortunately it did not have any effect on the kill cam.

Late to the party, but I found your post yesterday and it inspired me to attempt my own solution. See here if you're still interested: https://www.xsimulator.net/community/threads/flypt-mover.13464/page-161#post-238866

Hi all, the title says it: I'm looking for a single parameter that can be evaluated within export.lua to find out if the player is dead/alive and/or ownship destroyed/functional. Background info: I would like to stop exporting telemetry data to my motion rig upon missile hit, before the plane goes into the violent nose-down spin. Not a fun ride, tbh. Cheers, DK

Hi, thanks for your feedback. This is exactly what I'm currently doing already - I have "exit" mapped to a button on my flightstick. However - I fear I may rip off my stick or corresponding button during these events one day...

Hi all, I'm curious if there is any way to disable the external camera sequence showing your damaged plane spinning and disintegrating after a missile hit (except for not getting shot down in first place)? Background of the question: during this sequence DCS is still transmitting telemetry data and you may guess what's happening if you're sitting in a motion rig. I wasn't able to properly cap these movements with a spike filter without impairing normal in-game motion yet. Any helpful suggestion are very much welcome! Cheers, DK

Hi, I'm late to the party and just getting started into mission building so thanks a lot for your .miz! I wanted to change the altitude at which the bogeys spawn, but the "Bandit Set Respawn PolyZone.lua" which appears to contain that particular info (4500-5500m I'm assuming) only exists temporarily as soon as I launch the mission. Well as I said - I'm a noob in this regard. Would you mind giving me a quick pointer as to where I may set the spawning altitude? Cheers, DK.

Hi all, is it just me or did the latest OB break the JAS39C mod? No matter which mission, training etc. I launch, I will always end up with the external view of some other plane, tank etc. Cheers, DK.

Totally second that. Visuals in VR are just WOW! Thanks @Barthek!

Thanks - it turns out the mistake was on my end. I thought I had already re-installed the original mod after upgrading DCS, but obviously I didn't. I did now and it's working like a charm again

Good morning all, I'm trying to get Grinellis' original F22 mod working with latest DCS-MT. In both MT-2D and MT-VR I don't see cockpit etc. but only the outer shell of the plane from inside. It's working fine with ST-2D and ST-VR though. I tried without any additional mods activated. Any ideas? Cheers, DK