BlimpyBoy

Any update on this issue? I haven't been able to get the PVI and others to work either.

You will find the VR subforum in the "Input and Output" section on the main forum page. As to your issue, if you look in the controls mapping section of the DCS settings, in the drop-down tab that has the list of planes, scroll down and you will see an option for UI or VR (I can't remember exactly the name) and it has a "re-centre Headset" button that can be mapped. That should get you seated back in the cockpit. I'm not sure why it bumps you out to the left occasionally, in my experience that's a tracking issue or could be that the button is already mapped to a key/button that you use. There are also a couple of other handy VR controls in that section like VR zoom and Spyglass zoom that you will want to map if you haven't already. Good luck!

+1 it's so f*&*ing annoying...please fix ASAP. I beg you.

yeah i'm jumping in and adding a +1 to this...really frustrating. the "hands-free" button pushing should be at least an option in the settings... it's too easy to hit buttons/switches by accident. in the f18, when my hand is on the HOTAS stick IRL, it doesn't perfecting line up with the VR cockpit so my hand keeps hitting the buttons on the lower mfd...I usually just fly with it off now to prevent accidental activation. We have the ability to use the grip (laser) and trigger to interact with the cockpit with, which is awesome, I love it...Just let us turn on/off the "hands-free" button pushing.

Then click on Options - Kneeboard Profiles. Click on Modify to create a new Profile for the Kneeboard. Then click on the aircraft dropdown, and select the aircraft you want this profile to apply to. Alternatively you could select All here to have the same kneeboard profile apply to all your aircraft. I'm having trouble with this part...the Modify button is greyed out so I am unable to resize the kneeboard. Am I missing a step? I followed your write up and read the manual (which is a bit outdated).

After Digging through some of the bug threads, it has been reported. https://forums.eagle.ru/showthread.php?t=237211&highlight=box

That's a negative ghostrider. The JHMCS can be used with all the current air-to-air weapons. As for the original question, not sure "why" the circle is there. You can still use the JHMCS to lock-up the target off-bore within the radar FOV for the AMRAAM.

Ok so I tried it out again and the JHMCS symbology is messed up, at least in my game. When locking up a target with the JHMCS off-bore (ie looking up, left , etc), the TD box should follow the target. But for me, the TD box is jumping back to the HUD. I've attached my track file so you can see as well as a link to a YouTube video how it's supposed to work. f18hud2.trk

Thanks for the reply Harker! I didn't realize it was on by default...at least in the instant action/missions. But the second TD box was due to the JHMCS being on and looking through the HUD. I think I have to tweak the HMD reject options a little...because this didn't happen before.

Hey guys! I just jumped back into the Hornet today and noticed something different with the HUD symbology behavior when targets gets locked up. If you take a look at the attached track file, I'm getting a ghost TD box floating around...not sure if this is new with LTWS or what...any ideas? This is a fresh install of DCS on a fresh install of windows 10...VR with an HTC Vive Pro. Thanks f18hud.trk

I've been playing DCS 2.5 in VR for a while and would like to ask if you could add the "Use Mouse" option in the VR settings page as a bindable key in the Controls page. This would allow quick switching from using the mouse pointer to using the HMD pointer instead of going through the menus during flight. For example, running a ramp start in the F/A-18C Hornet with "use mouse off" is not practical as trying to use the HMD to point the cursor to the knobs and switches on the lower consoles is difficult and impossible in some cases (chin is in your chest) . And vise versa in flight, with "use mouse on", trying to use the mouse to manipulate the various switches while flying is not very practical either. In both cases, you have to go through the menu (ESC > Options > VR Settings > Use mouse On/Off) to change it during flight. However if this option could be toggled on/off with key presses like some of the other settings, you could stay in the 3D cockpit and transition between the two options without having to go through menus. Thank you for taking the time to read this suggestion.

Do you guys know if it's possible to have a hotkey for quickly switching the "use mouse" option on/off? During Ramp starts and some in-flight operations I like to have "use mouse" on. Otherwise my chin is basically in my chest trying to work the left/right console knobs and buttons. But during flight I turn it off and just use my head as the pointer so I'm not fumbling with the mouse. The only way I know of is by going through the ESC menu...

Yeah I have agree to this...when the Harrier first arrived the NavFLIR and FLIR worked beautifully! I almost always made missions at night. But since 2.5, night ops in general for all plans has been something to avoid. But that hits the AV-8B N/A harder than others as it's a Night Attack module. And it's something that really grinds my gears, but it's a DCS issue. I reported this issue to ED at what seems like a LONG time ago, and they said they were working towards a fix. But now seeing Wags post that it is high priority, it gives me that warm fuzzy feeling inside again. Once the HMD for the Hornet is complete, I hope they tackle this right after.

nvm! I did a 'verify integrity of game files' check in steam and all is working now. Thanks Capt Zeen!

I have a question gents: I'm getting the DDIs, AMPCD and IEFI to export to my second monitor, but then the in-game screens are blank. Is this normal? I had the Beta installed before I did the update 2 and the export and in-game screens would be on at the same time.

The Hotfix changelog doesn't mention anything about NVG fix.

It's a real shame that 2.5x has gone to release version without a fix for night lighting...this should be higher up on the 'to do' list for ED. Are you listening ED? Please fix the current night lighting/FLIR issues...thanks for the cows but let's focus. It's been long enough.

TBH FLIR is barely working presently...this module has taken a beating recently. Please remove the N/A from the module name. Fake news:doh:

I've posted this issue in the RAZBAM AV8B forum but it is actually an issue with the current DCS build. I wanted to re-post it here so the community could take a look. FLIR and NAVFLIR are broken (too dark/too weak/washed out) compared to earlier versions of 2.5.X, at least in the AV8B (the only plane to have NAVFLIR I think). I've attached screenshots of the comparison. I might check the FLIR in the A10 when I get a chance. The latest version that I could roll back to other than the current 2.5.2 stable is 1.5.8...but this issue was not present in earlier 2.5.X versions. Not sure when this issue popped up in 2.5, but the current OB and release version both have this issue. ED Devs said they are working on a tweak for the FLIR but are not sure when it will be updated. Some users were able to mitigate this issue before by turning DS off...so another kick to the nuts with the DS only build.

ED dev team is aware of the problem and are working on a tweak. No ETA given for when we will see the fix.

That's awesome! Can't wait for this! Great work!

I contacted ED tech support and they acknowledged there is an issue with FLIR and are working on a tweak. No ETA on when we will see it.

Here are some screenshots of NAVFLIR in 1.5.8 vs. 2.5.2 clearly broken...

FLIR doesn't use moonlight, that's Night Vision. I've just noticed this issue on a recent playthrough of a mission I built a while ago for night attack...the NAVFLIR feature is broken now. It's like the ground isn't producing any infrared heat at all...zero. That is the opposite of realism. The NAVFLIR HUD image is not showing up properly...FLIR on the MPCD isn't as bad...but also not as good as before. ED says this may be tweaked in the future...I hope so.

Sorry, I just saw this issue was already posted in the Bugs section.:music_whistling: