Mike_CK

I’m having problems getting a consistent lock when I put it in “cage” mode, put the enemy aircraft inside the pipper and hit the “nose wheel steering/auto acquisition” button. It seems to lock up when I do it the first time head on. But once the turning starts, I seem to be unable to get it to lock despite the fact that the enemy is only 1-2 miles ahead. Manual seems to suggest you have to hold down the button but Is there a minimum range or other reason why I would have difficulties locking a plane? maybe if I’m too close the Pipper won’t have that range countdown circle on the outside that I usually rely on to tell me it’s locked maybe? Just seems odd that it works fine head on so I thought maybe it’s a Doppler thing???

Well. I did re-run the scenario where Jester was constantly repeating: “I’ve got a good lock….i lost lock…I’ve got a lock…I’ve lost lock” and I noticed the radar screen looked “fuzzy” and jumbled like it was being jammed. I went into the mission editor and set the AI aircraft to “never use” in regards to ECM (they were SU-24s). This time Jester locked and held lock fine so clearly I just misunderstood the mechanics and we were being jammed. Not sure if that related to by steering circle never growing or letting me fire (so I had to turn off interlock) but could be. For all I know the SU-24 had a good ECM system when up against radars from 1968

I have sometimes have problems with the dynamic circle never getting bigger and it won’t let me fire as I slowly watch the enemy merge and pass me. So, I turned the interlock off. Do that and you can fire as long as the bad guy is locked. Have to remember that this is an old radar. It can’t lock planes up very well past 15-20 miles; especially small ones like a mig-21. also helps if every now and then, hit the context button short twice to put Jester back in regular scan. Sometimes he needs the readjustment. i have experienced, multiple times, the same thing Casmo had on one of his. Jester reports “I got a good lock” and immediately follows with “I lost the lock”. Hit context (long)..”ok, I got a strong lock” then immediately “I lost the lock”. This will continue until the plane is really close. but these things always need to be tweaked. Until we all get a better understanding of how this works and what is a bug, keep interlock off, order Jester to lock it up once it’s around 12 miles away and fire when it’s around 6-8 miles. When using Aim-7E or Aim-7F, I launch two. when jester starts with his repeated lock drops or says he can’t find anything despite it being 10 miles off your nose, reset him with the context double tap and try again. i have mixed results with interlock on. When off- and when I shoot within 7-8 miles hot- I see about a 40% hit rate. Much more with the Aim-7m. So maybe use the aim-7m until you get used to it

Load up aim-9m and see if it works. As stated, some models of the aim-9 don’t un-cage. The M model does

Got it. I was above 212kts…that’s why they weren’t coming down.

That didn’t work for me I’ll post my options lua when I get home. I set it to 1200x800 but I’m thinking that b/c I have my mirror set to the 1024x680 option in the menu, I should set it to that. Maybe then it will be in the middle. I’ll give it a shot

Yeah…problem is I couldn’t find the flap handle inside the cockpit to put the thing on!

Thank you. I have not been able to download the manual yet so thank you although im sure I tried those bindings to no effect. Guess I’ll give it another shot. Wasn’t sure if there was a fuse or something

Same. Set resolution manually in “special” tab to 1200x800. It makes the wheel visible but is offset to the left. I tried the “HB offset” setting but it didn’t have an effect the problem is that b/c it’s high and left, I can’t really use head movements in VR to select. I end up looking straight up. Is this something that can be fixed? I mean, this isn’t an issue in the F-14.

I’m guessing that you are diving down into thicker air and that is why. If you start at 45k feet and initiate a shallow dive that puts you at 20k feet by Mach 1.7, you ain’t going faster even if you go straight down head up to about 40,000ft and light them off. Stay in level flight until you are about maxed out (guessing around Mach 2). THEN dive a little and see where you are around 36,000 feet or so. Once you start getting below 30,000-35,000 feet, the air just gets too thick for Mach 2 flight

Well, having been flying many of the advanced high fidelity modules for 5 years, I feel like a moron asking this but here goes: what is the damn key binding to put the regular vanilla flaps down for takeoff/landing and up? I see all sorts of “flap switch” and out and down. I’ve tried almost all of them and I can’t get them down. What do I bind them too? Is there a special trick?

Single core? Not in VR!

Since you can fly it from either seat, i find it much easier to trim it well, get it as close to a hover as I can, then switch to the co/pilot seat and control from there. If you are trimmed, you shouldn’t have to do more than torque pedals and some minor cyclic. Nothing that keeps me from effectively operating the sights with a thumb stick on my HOTAS.

Man….sometimes people want to vent. Let them do it. It’s frustrating. Yeah, you CAN play in 2d…but for people like me who don’t have a track IR anymore, it blows. Yeah, there are work arounds but they don’t work for everyone. It doesn’t matter whose fault it is, it frustrating that there has been a fix for over a week but we can’t get it. Maybe there’s a good reason but that doesn’t make it any less annoying. if I’ve been looking forward to my 3-day weekend on a Florida beach for a year and when I get there, it rains all three days, I’m entitled to be frustrated and grumble. Doesn’t matter that it’s no one’s fault.

The workarounds don’t work for everyone. Second, I don’t care whose “fault” it is; according to Meta, it’s ED’s issue to fix and ED does has a fix for it. So yeah, for those of us that can’t use the workarounds, we don’t play and that’s frustrating when it’s been weeks. im sure ED and BigNewy understand why we are frustrated…we aren’t hurting their feelings or something. It’s a legit gripe and -as long as it’s civil- there’s nothing wrong with people voicing their displeasure at something on the forums. If you don’t want to hear it, don’t read the thread

I can’t begin to express my frustration at this issue that has been here for weeks… and the fact that we can’t get any kind of hot fix. I understand the workaround are there for some but they don’t work for me. I get Errors so I’m stuck waiting for a patch that is now delayed for another week. I don’t understand why we can’t just fix this one issue outside of the patch

Because you have “VR enabled” on the in game menus. There is a post back in the thread telling you what file you can open to change it

Yeah. I saw that but I’m hesitant to start messing with files. I don’t really know what I’m doing. I don’t mind pancake for now

Yes, this is an identified work around. You are playing through SteamVR instead of Oculus VR. I know for me at least, the drop in performance makes it a no go. I don’t love 2d mode but I’ll play pancake until - hopefully for the love of god- Tuesday when the patch comes out (can’t see it coming out on the weekend or Monday). Gives me a chance to enjoy the better graphics AND the ability to actually spot and identify enemy ground units in my Hind for once!

Habit. Sometime I think that answer is thrown in there b/c there have been several times I had an issue, gotten the “sorry…all Ok on our end” only to see a “fix” days later in a patch or to see the bug confirmed BUT….thank you! That’s why I post even if I don’t have a track. Many times someone on here knows what I did wrong or the issue even if I’m told “can’t reproduce”.

I know the CCIP/CCRP system with the hornet has been an issue in the past but I’m still having major issues and -before I post a track file- I’m interested in whether others are as well. playing an instant action mission w/hot start. Modern day (so GPS and no INS issue). I have mk82SE but dropping in Freefall mode. I see the target out in front and designate it with the HUD “meatball”. I move the designator more precisely onto the target building and press TDC Depress again. By the time the timer counts down and releases the bombs, I am WELL past the target. Like, I’m flying over the designated point when the timer is still at 10 seconds. I tried multiple times to undesignate and redesignate other targets but it always releases when I’m well past (I tried CCIP and even dropping at low altitude, it was also inaccurate but that could be the retarded bombs in FF mode ) I’ve been flying the hornet since 2019. I don’t have any issues when I designate the target with a TGP or WPDSG. I can drive tacks in the F-16 and I’ve also cleared my FXO & Metashader files but I’ve always had this issue. hiw about you guys? Any idea if I’m doing something wrong?

How do you download these files? I click “download”, it says “zipping files” and nothing happens. I don’t get any options where to download it or where it went

Well, I was hoping for a patch today but that doesn’t seem likely since Bignewy said he hopes to let us know the patch release date soon. So that means at least another 4 days. I know it’s pointless to ask….but it makes me feel a little bit better: can we PLEASE get a hotfix for this outside of the gameplay patch if that is at all possible???

I own both and - along with the F-14 and Mirage 2000k fly them a lot. But sometimes I want to fly a Mi-24 hind. Other times I’m in a WW2 mood. When the F-4 comes out. I’ll be into that. Can’t fly only 2 planes for 6 years!

Not as many as some; about 15 (not including the FC-3 pack). I don’t really ever fly 4 of them (mirage F1, Mig 19, Mig 15, f-86) but the others I do…in “bursts” depending on mood. But trust me, there are a lot of people who have invested more than me. So I figure that we should get a lot more room to yell and complian over stuff like this compared to a regular $50 game