defeatist99

So the mission is definitely bugged. The synthetic runway isn't in the right place even if you fix all the stuff that isn't correctly in the INS. The coordinates in the INS for the runway weren't correct. And the runway heading wasn't correct in the INS. That being said when you fix everything TACAN and ILS work just fine. You can follow the localizer and glideslope and it will put you right on the runway. I think they somehow messed up the weather causing the game to think the opposite runway was going to get used for most of the incorrect INS inputs. I can't really explain the synthetic runway problem until I open it up in the mission editor.

Yeah that wouldn't be the cause on an approach training mission.... I'll give it a test here in a min, but there's been a couple wonky things with the mirage since the update.

I'm on the beta so I don't know if that was going to make a difference. You were careful you didn't accidentally switch to yankee instead of x-ray or accidentally put it in a/a or receive only? I know it isn't quite acting right with the line that's supposed to be pointed to the station itself not pointing near the station but I had it take me 86 miles bearing 108 from Kutaisi and it took me straight there. Are you hot starting? Ground starting? I wanna help you figure it out bro!

I just checked and it took me to the right place, but there was some other wonky stuff going on with the mirage. The thin needle was not working as intended. The thick needle took me directly to the distance and bearing though. Another weird thing was every time I centered my TrackIR it stuck my head so far between my knees I couldn't see the hud. Are you on the beta or the stable branch?

Two questions. One: did you do a nav update while you were flying? Two: did you check and make sure the runway heading was correct on the CP/PD for the waypoint. For some reason it's always a couple degrees off unless you actually set it.

I'm guessing you are in the campaign mission that takes you to Kutaisi. It sounds like you are doing it correctly. I'll redo the mission to check but last time I did it I think there was something not working right as well. I believe in the mission for some reason the thin line is actually on a direct 180 degree bearing and IIRC you are supposed to go to Kutaisi airbase first and then go south from there and meet up with the other mirage flight. Vad should take you direct to 20nm south of Kutaisi how you had it set up though. Pretty sure a mission trigger is over the airbase.

Harrier?

If you have random failures selected they are very rare, but do happen. You can also set different failures to random in the mission editor to make it more common.

Here is an example of the bug. Notice glideslope and runway heading switch sides. Also bonus typo in the mission 4 documentation.

I was close.

50,000 feet 399kts mach 1.47 Looks like IAS to me.

I figured it would use actual aircraft borsight. It seems odd that it would do that. I haven't seen anything in the manuals about it.

Going back through the campaign and if you go to the CP/PD page of the last waypoints on any of the missions they are displayed backwards until edited. It displays the glideslope on the left lcd and the runway heading on the right lcd. After editing it will correctly display runway heading on the left lcd and glideslope on the right lcd.

Yes..... but according to the TAC manual you shouldn't use it for sidewinders either. It's to be used for the pre-flight check or SMS failure.

Also to add to this when I used the velocity vector to put the DMT on a target it locked to the ghost vector being off boresight. Is it supposed to do that?

I am one of the more hardcore for realism but I think the right decision was to leave it to the mission designers. Any of your hardcore multiplayer servers would have the always aligned option disabled. But newbie events, aerobatic servers, and single player are fine to use it. I sometimes turn on the "cheat" because on my 4th mission of the day I don't want to align the stupid INS for 8 minutes again in single player. That's a half hour of pretty much nothing in the Mirage. The A-10 wouldn't need the "cheat" anyway because by the time you get everything else set up it's already done anyway. You shouldn't be able to do it in Blue Flag or similar servers but there's a lot of other reasons and places it isn't a big deal.

Mark-82's in Auto are releasing when they should. The bomb fall line still isn't stabilized correctly but the bombs aren't releasing as soon as I pickle. They are doing a consented release. As for DSL it's not a computed point so you would probably either need to be in a steeper dive to help with accuracy or I'm sure there are charts with altitude and speed for release in DSL.

I'll see if it's like that for me in about 10 minutes. Razbam talked to some USMC pilots and they only ever used the E and F on the harrier. They are using the G as a stand in for the F currently.

Yeah this has been bothering me since the update.

I've had this issue. It's not that they are blowing up it's as soon as they are start their engines they run into the back of you and blow up. I haven't been able to cold start on tarawa with a wingman without them immediately running into me.

Everything is set up correct and I've been flying the mirage since it came out. It's just something that has happened a few times though rare and requires a trim reset after disconnecting AP.

Real thing as far as I know.

Trim. It also helps if you do by the book accelerating and decelerating transitions. It will set you up for the hover quite nicely instead of just slamming on the breaks and trying to hover.

By everyone once the module is more complete. We don't actually know how easy it is going to be until more progress is made on the module.

He's talking about caging the HUD on the hornet. That can be ignored. It's just crosswinds. This happens more at low speeds. It will push your VV where the wind is pushing you and the HUD is sort of tied to that.