Nova1395

I've come from an Odyssey G1 to a Reverb G2 - these symptoms are similar. It happens whenever I make a drastic view change - ie, F2 view to another aircraft that is 150nm away, so it has to render the aircraft and the map and scenery around it, or - the F10 map. It doesn't happen every time, but roughly about 10% of the time. On the Odyssey it would so something similar, but the headset would instead just crash out. My Reverb does that too, sometimes it bluescreens and then just goes to a black screen while the sim continues running, and continues tracking. I can't say I'd blame ED for this one entirely, but perhaps there's better ways to go about rendering.. It feels like the GPU just gets overloaded with a new request for a new environment out of the blue, and takes up such a toll on the GPU that essentially WMR crashes out because there's nothing to even really render at this point, the GPU is maxed out. Staggered rendering in a way would be a better way to go about it I guess is the best way to put it, at least when switching external views - initial render is low res, then populate with higher renders. As for the F10 map, this has been an issue for me for over a year now because it's the same damn problem. It's ditching the cockpit and environment we were just in, and now rendering a totally new environment with an aircraft in the hangar bay. Tolls out the GPU, and if you're unlucky, you bluescreen out. I wish they'd just move onto a live F10 overlay map like the kneeboard.

Would it be possible to have it revert back to mouse mode in DCS when I hide the kneeboard? I normally have my mouse right over my right leg and my new pen tablet has taken up that residency now so that I could use the VRK. However it'd be nice to still be able to use the mouse mode when I hide the kneeboard, so that I can re-arm and use the F10 map, or the server browser, without having to fumble around to find my mouse. Anybody had any luck with that?

In Open Beta, I noticed that when you put the HUD in Reject 1 or Reject 2, it locks the Mach and Current G's to the last known value. They remain on the HUD (which according to page 34 of the Hornet Early Access guide, they should not), but no longer update on other displays that they should be present on like the HMD. This was particularly confusing when I forgot to switch it back to Normal and got into an air to air engagement, wondering why I was going Mach 0.53 at 450knts IAS at 20k/ft. To reproduce: 1. Turn on HMD 2. Set HUD Symbology to Reject 1 3. Increase or decrease airspeed, or pull G's. HMD and HUD will not reflect the changes.

You are correct, slightly. In the Hornet, Dispense switch Forward will always dispense Program 5, and Dispense switch Aft will dispense whatever program is currently selected. You can edit all the programs (including Program 5) to your liking, program 5 is basically your 'emergency' program. Rather than try to explain this over text, I've made explaining the issue. I have found an easy workaround, which is cycling through the programs and is quite honestly a low priority item, but just thought I'd bring it up. When I went from horsing around and doing a flare dump on program 4, then into a dogfight on the next sortie, I was surprised to see all 40 flares dumped in about 5 seconds as I struggled to figure out what was going on.

I understand what you're saying, but that isn't actually what's happening. >Enter a custom program into program 4 >Power cycle system >Select program 3 >Upon firing countermeasures, program 4 is instead used. This would be definitely viable, however I'm still trying to get a feel for what's appropriate for different parameters, and I've never messed with the lua files.

A bit hard to explain this in the title. Say you go into EW and configure Program 4 to be your 'airshow' setting, dump 40 flares in 10 seconds (2 flare, 0 chaff, repeat 20 times, 0.25s intervals). If you flip the Countermeasures switch and flip it back on, you can load up Program 1, but when you activate the program it will change Program 1's configuration to Program 4's configuration, and you will dump all your flares. Steps to recreate (Open Beta): 1. Set up a Countermeasure Program to dump all flares on any program. 2. Remain on this profile. Flip the Countermeasures switch to OFF 3. Flip the Countermeasures switch back to ON 4. Select a different profile once the BIT test is completed. VERIFY that the program setting is not set to dump all flares. 5. Countermeasures Aft release, watch all of your flares go byebye. A more common occurrence: 1. Ground Pound run, set up 10 flares to drop over 10 seconds as you drop ordnance, to counteract any MANPAD's on the ground. 2. Out of ordnance, RTB. 3. Turn Countermeasures Off as is good habit. 4. Take back to the skies, and find a bogey that's within your reach, select your ECM program that's for RWR/IR missiles. 5. Turn defensive against a radar guided missile, go to drop countermeasures... instead, it reverts back to your ground pound program. reeee.trk