VC

Right, so I tested this and it's definitely the physical joystick. Initially in a test mission I couldn't make it happen at all, and I was going to blame server lag, but then I worked it out accidentally. What makes it happen is how suddenly and how hard I pull the trigger. Gentle squeeze, only one missile. Even with holding, I was wrong about that. I probably assumed it was holding because when multiples fire while you're still pressing the trigger it's easy to blame that. And Phoenix has a launch delay so you don't know if it fired more than one until 3 seconds later. Obviously in a chilled testing mission I was being gentle (initially). In twitchy combat I naturally squeeze hard and *poof*, multiple launch. After some "practice" I could do it every time. I managed to launch all 4 Sidewinders at once from an F-14, and 3 at once from an F/A-18. Sparrows and Phoenixes too. This also explains why I thought it affected Sidewinders worse, I'm more relaxed when launching BVR. However, it still only affects the Tomcat and Hornet. I tried quite hard with the F-15 and never managed a double shot, so something about the launch logic in FC3 planes filters out the bad inputs I guess. I also tested re-mapping to a different button and I can't make it happen so it's only the trigger. This is really worrying actually, especially combined with what you're saying about needing to disasseble the trigger to clean it! Guess I need to learn to be gentle!

That's why I held down initially and like I said, it fired all 4 Phoenixes! So now I tap really fast and a few seconds later one comes off the rail. Rarely two.

Interesting. I'm on Windows 10 but I wouldn't jump to blame OS. My Joystick is getting a bit old now. I'm going to experiment with mapping the weapon fire function to a button other than the trigger and see if I have the same problem.

Single trigger, nothing weird in Windows settings. I don't have this problem with FC3 planes, but they actually require you to hold the trigger for 1-2 seconds for launch. Or the MiG-21, but that forces you to select stations. I do however have the same problem with the F/A-18C. And on the F-14 I've done this accidentally with the AIM-7 and AIM-54 as well, but not as often. With the AIM-54s, I assumed you have to hold the trigger for the 2 to 3 second launch cycle, but this just fires all 4 at once! Is that even intended behaviour? It seems it is more likely to happen if you reflex-fire on the Sidewinder tone while boresighting a target without a radar lock. Firing with radar lock makes it less likely, but still possible.

T.16000M, no additional software.

I have an issue in the F-14. It often fires my Sidewinders in multiples. Usually I only carry two, so it fires both and leaves me without. I can get it to fire one at a time, but only if I tap my trigger as gently and quickly as physically possible. Even 0.5 seconds holding it down it interprets as firing everything. Are there some settings I can change to stop this happening?

Sorry, my frustration wasn't aimed at you. I hope this is something ED get better at. I can see now you already posted the issue, but it's not convenient to check every news thread across all the sub-forums for information that should be accurate in a central place.

So inaccurate patch notes, great. Can they not go back and edit the change log to remove the misleading parts?

I went to test this after reading the patch notes (yes I'm on Open Beta) but those buttons still don't work, at least not in VR. Trying to click them just closes the cover again.

Does the fix by RVator affect MP server Integrity Checks? Will it cause problems when the next game patch hits since it's modifying core files manually?

Can you explain what you mean? The patch notes were incorrect?

Thanks! Will give it a try!

Sorry for the noob question but can't seem to find this in various threads/tutorials. Is it possible to filter the RWR (EW page) to only show airborne threats and hide all SAMs? Super annoying having overlapping symbols when some maps have a lot of SAM clutter.

Because it's broken in VR only and testing is expensive. Testing everything essentially twice (on screen and in VR, which is a huge simplification anyway because there are different resolutions of both) is unrealistic, so they probably don't do it comprehensively. This slips through the cracks in the same way a web designer might let slip a bug that makes text overflow and look bad in 1024 x 768 because they develop on a 1600 x 1200 screen and don't think to check.

OK thanks, will try the fix in that thread and keep an eye out for hotfix.

Since the update today, my Jester menu is broken in VR. Instead of appearing centered in my view, it's off to the left and down, and part of it is cut off. It's very hard to use. Any ideas if this is something I can fix or if it's a bug that got introduced?

Fair enough, I guess you don't always have to crank to the last degree :) I'll practice, maybe see if I can find a scratch or screw on the TDI to act as a quick reference.

Yes, I remember your thread but knowing it's 60 doesn't help you visually estimate 60 on a rectangular TID with no additional markings. Can someone confirm if the VDI shows it and maybe post a screenshot of the symbology?

When cranking in STT, is there any symbology to help me tell when I'm nearing radar gimbal limits? I've been looking at the TID and I can estimate but there's nothing obvious to help me optimise, and depending on the scan range the locked target can go off the edge of the screen in a hard crank. Plus looking down like that while violently weaving and trying to shoot back in between isn't ideal. Any tips for this scenario?

Which PTT behaviour are you using in the "Special" tab of the settings?

Diamond is just showing you the locked target. If there's no diamond there's no lock, so the pipper range isn't necessarily the target range.

Fair enough then, thanks!

All of them have this to an extent, well, the ones I own (Flankers, Fulcrum, Fishbed, Tomcat). But the F-15 is the worst by far, hence the only one I've gone out of my way to try to find a solution for. The others I think have bigger HUD glass areas, or the stuff rendered on the HUD doesn't go to the edges by default so you have some wiggle to move your head up and not lose it.

Did a few loops and hard turns with full AB and 0 curve, no wing snap. Had to go deliberately ham-handed to break it. My conclusion is, it's about the speed of the stick movement in the high-G region. By putting the G on gently and watching the acceleremeter, I got to nearly 10G and blacked out before the plane snapped. Next time, I broke wings at about 9G without blackout by pulling suddenly from 8G to 9G. So this confirms for me that the steepness of the positive curve in this region makes breaking wings more likely. Might leave mine on 0 for now or got for -5 to -10. I flew a few test dogfights with 0 and wasn't really paying attention, so I kept blacking out. That's a good sign, a couple of weeks ago each of those blackouts would have been a wing-snap instead.

Not helpful guys :lol: I want to see it in VR.