RickInAZ

Both eyes work normally in the start-up menu and set up screens. Once I choose a mission, however, the LEFT eye shows only a fuzzy blue background (plus the SRS window and/or the CHAT window). The RIGHT eye seems fine, showing the whole rendered scene as it normally should. When I quit the mission, the left eye display returns to normal. This happens in stand-alone missions and in multiplayer games, and across all modules I tested. I suspect this has something to do with a very recent change: I dropped OpenComposite and started using the native support for OpenXR (using the command line modifiers). At first, everything seemed great--and both eyes displayed a normal image, in and out of missions. But after a couple of days (and without any further changes to my configuration or settings), the left eye display suddenly stopped working properly. I have tried rebooting my PC, unplugging the Reverb headset, switching to a different USB port, changing the display settings from "VR" to "HIGH" and back again, and reviewing the DCS log to see if anything jumped out at me. I didn't find anything that worked. I have not done any configuration with the OpenXR Toolkit, although it is active when I boot into the game (v 1.2.4). Has anyone experienced this phenomenon with the Reverb or another WMR headset, and if so, have you found a way to restore normal rendering? I would be happy to share other details (like a log file) if it would be helpful. Thank you.

I configure the Huey with just one front minigun. When the BUG happens and the AI co-pilot starts crazy-firing, I set him to HOLD, and press my trigger once (normal press, into the second detent on my two-stage trigger). This stops the gun from firing. Once it stops, I can set the co-pilot back to FREE FIRE and he won't go nuts. When I tried this with both front miniguns installed, pressing the trigger just switched which gun was firing... eventually one side would deplete its ammunition. So this is just an attempt to stop the madness, and it's not a fix. It's also not optimal, because sometimes you really want both front guns firing on a target. Having only one gun reduces the coverage arc and lowers the total power of the front system substantially. At least the door gunners aren't affected by the BUG. Or are they?

I have to tip my head forward to bring the flight reference items (speed, height, vertical velocity, and the level reference line with cross bars) to the horizon. Note how much lower the HIADSS is, reference to the panel objects. This is about 10 degrees "nose down" for me.

This is a mirror of my VR view, with my head in a normal posture, and I am looking through the "sweet spot" of my headset lenses at the horizon straight in front of me. As you can see, the reference cross is above the Apache's cockpit crossbar, and the heading reference tape is way up in the upper glass. So, it's very different from what you imaged from your gameplay, @BIGNEWY. I hope this helps illustrate the problem. The helicopter can still be flown, but when I need to watch the pilot's sight (the crosshairs) and fly, I am looking through a portion of the headset lens that already has some fuzzy focus. By the time I am looking at the heading reference, the whole outside view is out of focus. The headset lenses just aren't good enough to have a sharp picture to the top edge.

@BIGNEWY, thank you for your suggestions and the screenshot of your view. I tried the headset position recommendation, and I think mine fits about the same way yours does. Comparing my view to your screenshot, the only way I can get something that looks like that is to point my chin down almost to my chest... at rest, my straight-ahead view is just above the ball of the inclinometer. The crosshair when in flight appears to be well above the horizon, so that I get the "align limit" warning on the gun when my head is comfortably level. The direction (compass) indicator is way above the crossbar, and the interface for George is above that, way up out of the Reverb's "sweet spot"--it's always out of focus. I did check for snap views (found none), and I have not used the VR eye alignment tool. I did reset my environment data and reestablished my seated position with my headset and Windows Mixed Reality Portal, and it did not make a difference. I agree with @dimps and other posters who have suggested that this positioning should be made adjustable for different people and headset combinations; clearly you and other users have no problems with the symbols as they are. Thanks again.

The problem persists. It's well-documented in this thread. I, too, have a Reverb G2 and the problem is clearly evident to me. Do you need anything further from me as far as setup or configuration? Thanks for your help.

I stumbled across this site while seeking an answer about "BAL Limit" that I couldn't figure out. This is not related directly to the DCS Apache module or the manual or procedures that are correct for our bird. But if you just can't get enough AH-64D stuff, this is a short quiz (with answers!) that you can check out.

This short video shows an AI aircraft circling with idle power, and an obviously incapacitated pilot. In this single-player game (DCS Liberation), the persistent campaign does not show this as a "killed" aircraft, and it will appear in the next mission--with more experience and up-leveled skills! These planes can be attacked and shot down, but something is wrong. It shouldn't be able to stay in the air.

Yes. Confirmed on F/A-18.

I just downloaded the mission files, skins, and necessary mods, as directed. When I attempt to start the mission (the "dawn" variant), I get a compile error: DX11Renderer - Error Shader "model/fake_spot_lights.fx" failed to compile - HRESULT: ERROR_PATH_NOT_FOUND Am I doing something wrong, or did the latest DCS update break things again? Thanks for creating this mission. I am looking forward to flying it! Rick

Embark Troops Works We went back to the valley and successfully completed the mission. The EMBARK and DISEMBARK commands work perfectly now. I am glad they were able to fix the problem. I did notice a terrible lag/stutter after dropping off B squad... only one frame per second until after I had taken off. Then, the motion became smooth again and I could fly normally. Each update seems to make the VR performance worse, in my opinion. Thanks again for this campaign. I am enjoying it very much. Rick

I had the same problem. Rick

Hi CHPL! Thank you for building this campaign; I am now a much more skilled helicopter pilot than I was before I began these missions! I am stuck in "Mission 11", as you are calling it in this thread. I have had success with eliminating the first rush of attackers, and with landing to pick up the troops. However, I noticed that the "embark troops" command (F7-F1) does not work correctly... Pressing F7 brings up the detail, but there is no F1 choice available, only F11 and F12. The door gunner reports that everyone is on board, though, and I can pick up and go. (Visually, the Alpha group is still standing in the LZ, but I think they "un-spawn" in a minute.) The next step is where I get stuck. I don't know if this is the big surprise for the mission, so I will try to hide my comment with a spoiler tag... Do you have any suggestions for finishing this mission successfully? I know my crew would like to be done with it; we have been up that valley 15 times already! Thanks again! Rick

Thanks for your response! No, I am using Windows speech recognition. But that's a good suggestion and I will follow up on it. If anyone has "Action ..." commands that are working well, I would love to hear any tips you may have. I am mostly drilling on the F/A-18 and Alerax's LSO script for carrier operations. Thanks! Rick

Import F10 Menu I have used the "Preferences", "Import F10 Menu" to generate "Action ..." command phrases in the past. Of course, I have followed the steps to "Finish" the process, so that the profile matches the database. These Action items seemed to work fine. But this week I noticed that the group of Action commands was different: I saw a bunch of items in there that I didn't recognize and I was missing some mission-specific (F10 menu items) phrases that had been there before. So, I went into the Editor tab and deleted all the Action command phrases... and "Finished" the process so that the database was synchronized. Then, I checked the "Import F10 Menu" checkbox, opened DCS, and flew the mission I wanted to capture. After a short flight, I closed DCS and checked for the keyword command phrases (the Action... commands) in the Editor. I didn't see any Action phrases at all. The "Test" button (on the Editor tab) verified that nothing new had been added. I went through this process a second time, with the same results... or lack of results. So I could use some advice at this point: How can I get the VAICOM PRO to gather and import the F10 menu items and have them available? I am running the DCS Beta on Windows 10, all updated. VoiceAttack and VAICOM PRO are current versions, too. Thanks! Rick