Jump to content

Recommended Posts

Posted

Is the localizer deviation line in the M2K accurate in both position and time? It feels like there is a huge lag with it starting to move, and when I turn back to correct the line just keeps sliding in the opposite direction, no matter how hard the turn is. Can anyone suggest a way to deal with the issue? Should I just disregard the line, follow my navigation and correct my heading once I see the synthetic runway?

 

If the line isn't functioning as it should, is there a workaround? I found some old threads reporting issues with the localizer deviation line, but I'm not sure if what I'm seeing is what was spoken of in those, and since they were a couple of years old I was hopeful that those issues would have been fixed already.

 

 

If anyone can offer any advice it would be welcome.

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F-15E] [F-16] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis]

[Afghanistan] [Cold War: Germany] [Iraq] [Kola] [NTTR] [PG] [SC]

Intel i9-14900KF, Nvidia GTX 4080, Gigabyte Z790 Aorus Master X 64GB DDR5 @ 6400 MHz, SteelSeries Apex Pro, Asus ROG Gladius 3, VKB Gunfighter 3 w/ F-14 grip, VKB STECS throttle, Thrustmaster MFD Cougars x2, MFG Crosswind, DSD Flight Series button controller, XK-24,

Meta Quest 3

Posted

If you mean the runway axis in the HUD, yes, forget it for now.

 

 

The -O- in the box is OK.

 

 

You also have have Loc and Glide needles on ADI.

Mirage fanatic !

I7-7700K/ MSI RTX3080/ RAM 64 Go/ SSD / TM Hornet stick-Virpil WarBRD + Virpil CM3 Throttle + MFG Crosswind + Reverb G2.

Flickr gallery: https://www.flickr.com/gp/71068385@N02/728Hbi

Posted
If you mean the runway axis in the HUD, yes, forget it for now.

 

 

The -O- in the box is OK.

 

 

You also have have Loc and Glide needles on ADI.

 

Awesome, ta, I guess that is what I mean :)

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F-15E] [F-16] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis]

[Afghanistan] [Cold War: Germany] [Iraq] [Kola] [NTTR] [PG] [SC]

Intel i9-14900KF, Nvidia GTX 4080, Gigabyte Z790 Aorus Master X 64GB DDR5 @ 6400 MHz, SteelSeries Apex Pro, Asus ROG Gladius 3, VKB Gunfighter 3 w/ F-14 grip, VKB STECS throttle, Thrustmaster MFD Cougars x2, MFG Crosswind, DSD Flight Series button controller, XK-24,

Meta Quest 3

Posted
Is the localizer deviation line in the M2K accurate in both position and time? It feels like there is a huge lag with it starting to move, and when I turn back to correct the line just keeps sliding in the opposite direction, no matter how hard the turn is. Can anyone suggest a way to deal with the issue? Should I just disregard the line, follow my navigation and correct my heading once I see the synthetic runway?

 

If the line isn't functioning as it should, is there a workaround? I found some old threads reporting issues with the localizer deviation line, but I'm not sure if what I'm seeing is what was spoken of in those, and since they were a couple of years old I was hopeful that those issues would have been fixed already.

 

 

If anyone can offer any advice it would be welcome.

 

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.

Posted
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.

 

Hi, thanks for replying.

 

1: No, this is a training mission so it starts as you prepare for approach with no mark points set, and there isn’t really time to create one.

 

2: I didn’t check the CP/PD, but the synthetic runway is located exactly where it should be so I don’t think it’s navigation error. There are times when I’ve banked more than 360 degrees without ever catching back up to the runway axis line, so that suggests an error in the symbology rather than accumulated navigation error, yeah?

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F-15E] [F-16] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis]

[Afghanistan] [Cold War: Germany] [Iraq] [Kola] [NTTR] [PG] [SC]

Intel i9-14900KF, Nvidia GTX 4080, Gigabyte Z790 Aorus Master X 64GB DDR5 @ 6400 MHz, SteelSeries Apex Pro, Asus ROG Gladius 3, VKB Gunfighter 3 w/ F-14 grip, VKB STECS throttle, Thrustmaster MFD Cougars x2, MFG Crosswind, DSD Flight Series button controller, XK-24,

Meta Quest 3

Posted
Hi, thanks for replying.

 

1: No, this is a training mission so it starts as you prepare for approach with no mark points set, and there isn’t really time to create one.

 

2: I didn’t check the CP/PD, but the synthetic runway is located exactly where it should be so I don’t think it’s navigation error. There are times when I’ve banked more than 360 degrees without ever catching back up to the runway axis line, so that suggests an error in the symbology rather than accumulated navigation error, yeah?

 

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.

Posted

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.

Posted
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.

 

Thanks for taking the trouble to unpick all those problems. So the synthetic runway was on the wrong runway, and the other cues were for the runway that should have been used.

 

I see the irony in this, but I’ve done that mission so often now that I actually feel pretty confident landing now, so I guess I’m better off creating a fast mission and using that to practice landing?

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F-15E] [F-16] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis]

[Afghanistan] [Cold War: Germany] [Iraq] [Kola] [NTTR] [PG] [SC]

Intel i9-14900KF, Nvidia GTX 4080, Gigabyte Z790 Aorus Master X 64GB DDR5 @ 6400 MHz, SteelSeries Apex Pro, Asus ROG Gladius 3, VKB Gunfighter 3 w/ F-14 grip, VKB STECS throttle, Thrustmaster MFD Cougars x2, MFG Crosswind, DSD Flight Series button controller, XK-24,

Meta Quest 3

Posted
Thanks for taking the trouble to unpick all those problems. So the synthetic runway was on the wrong runway, and the other cues were for the runway that should have been used.

 

I see the irony in this, but I’ve done that mission so often now that I actually feel pretty confident landing now, so I guess I’m better off creating a fast mission and using that to practice landing?

 

Lol the synthetic runway wasn't even at the airport let alone the wrong runway. Yeah you could just create one really easy. I'm actually going to see whats up with this mission though because I'm curious. If I can fix the mission I can get you a copy.

Posted
Lol the synthetic runway wasn't even at the airport let alone the wrong runway. Yeah you could just create one really easy. I'm actually going to see whats up with this mission though because I'm curious. If I can fix the mission I can get you a copy.

 

That would be awesome, thank you! Did you fix it by editing waypoint 2 using the info on the Batumi kneeboard page for runway 12?

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F-15E] [F-16] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis]

[Afghanistan] [Cold War: Germany] [Iraq] [Kola] [NTTR] [PG] [SC]

Intel i9-14900KF, Nvidia GTX 4080, Gigabyte Z790 Aorus Master X 64GB DDR5 @ 6400 MHz, SteelSeries Apex Pro, Asus ROG Gladius 3, VKB Gunfighter 3 w/ F-14 grip, VKB STECS throttle, Thrustmaster MFD Cougars x2, MFG Crosswind, DSD Flight Series button controller, XK-24,

Meta Quest 3

Posted (edited)
That would be awesome, thank you! Did you fix it by editing waypoint 2 using the info on the Batumi kneeboard page for runway 12?

 

Yeah but I also changed the date because the magvar felt off and added 1kt winds so they would def pick the right runway. I attached the file if you need it. I tested it a couple times. It should work for you until baltic dragon gets back from holiday.

 

If you ever need help with anything let me know I've got a decent amount of time in most of the aircraft.

M2K Training 04 FINAL ILSfix.miz

Edited by defeatist99
Posted
Yeah but I also changed the date because the magvar felt off and added 1kt winds so they would def pick the right runway. I attached the file if you need it. I tested it a couple times. It should work for you until baltic dragon gets back from holiday.

 

Very much appreciated Defeatist. These are changes I could never have made myself, kudos :)

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F-15E] [F-16] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis]

[Afghanistan] [Cold War: Germany] [Iraq] [Kola] [NTTR] [PG] [SC]

Intel i9-14900KF, Nvidia GTX 4080, Gigabyte Z790 Aorus Master X 64GB DDR5 @ 6400 MHz, SteelSeries Apex Pro, Asus ROG Gladius 3, VKB Gunfighter 3 w/ F-14 grip, VKB STECS throttle, Thrustmaster MFD Cougars x2, MFG Crosswind, DSD Flight Series button controller, XK-24,

Meta Quest 3

Posted
It was nothing m8 literally took less than a minute to fix. I just wanted to test it and make sure it worked.

 

Mission is great now, cheers! :thumbup:

 

 

Modules: [A-10C] [AJS 37] [AV8B N/A] [F-5E] [F-14] [F-15E] [F-16] [F/A-18C] [FC3] [Ka-50] [M-2000C] [Mig-21 bis]

[Afghanistan] [Cold War: Germany] [Iraq] [Kola] [NTTR] [PG] [SC]

Intel i9-14900KF, Nvidia GTX 4080, Gigabyte Z790 Aorus Master X 64GB DDR5 @ 6400 MHz, SteelSeries Apex Pro, Asus ROG Gladius 3, VKB Gunfighter 3 w/ F-14 grip, VKB STECS throttle, Thrustmaster MFD Cougars x2, MFG Crosswind, DSD Flight Series button controller, XK-24,

Meta Quest 3

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...