DerFangzahn Posted May 4, 2019 Posted May 4, 2019 (edited) Hi, It seems that in Mission 3 the compass alignment is completely screwed. Mission starts with heading 219° while INS shows 60°. Degradation is off in options. Do I miss here something? Edit: Every start a get a different heading. 60°, 80°, 120°,... Edit2: And the mission crashes few minutes after takeoff... I don't have this issues with other missions or campaigns in the M2000 Edited May 4, 2019 by DerFangzahn
baltic_dragon Posted May 5, 2019 Posted May 5, 2019 Hey. Only this one mission? Also: are you on stable or open beta? For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
DerFangzahn Posted May 6, 2019 Author Posted May 6, 2019 Open beta. Only tried the next one. And this one fine again.
DerFangzahn Posted May 8, 2019 Author Posted May 8, 2019 Do you need additional information? Any chance to get this solved?
baltic_dragon Posted May 8, 2019 Posted May 8, 2019 I can’t reproduce it, I will need to dig deeper. For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
Pinola Posted September 10, 2019 Posted September 10, 2019 Hi, I´m having the same issue. The compass shows bearing 330, but i´m actually heading the other way around. Tacview show my heading was 140. I have the "no INS alignment option" set, could that be the problem? I´m attaching an screenshot and the tacview file.Tacview-20190909-232228-DCS-M2000 NTTR M03.zip.rar M2000 | Mig-21 | Mig-15 | F-14 | UH-1H HUEY | A-10C II | MB-339A | A-4E-C | F-18 | F-86 | KA-50 | F-16 |AH-64D| NTTR | PG | AMD RYZEN 5 2400G 3.9GHz + RX 580 8GB OC + 32Gb + 1TB SSD
DerFangzahn Posted September 10, 2019 Author Posted September 10, 2019 (edited) Replayed the mission yesterday and the bearing bug is still present. Could this be an issue with the mission file itself? I do not get this in any other mission or campaign. Also it is impossible to fly into the direction of a selected waypoint. HSI will give a direction. But if you fly into the displayed direction you are not flying to the selected waypoint. On the HUD I am even not able fly into the direction of the selected waypoint. Waypoint will always be displayed left or right on the HUD. You can turn where you want. You will not get the waypoint indicator into the center of the HUD. Edited September 10, 2019 by DerFangzahn
baltic_dragon Posted September 10, 2019 Posted September 10, 2019 Hey, I have absolutely no idea what may be the reason, but I’ll try to check with the Devs and will report back. For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
Zeus67 Posted September 10, 2019 Posted September 10, 2019 Please provide a track file. "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
Murdock_01 Posted September 25, 2020 Posted September 25, 2020 Hey there, I have the same issue. Done INS alinment properly and its the same thing. Did you manage to get a fix for this? looks like quite a few people is having this issue for a long time. I have not tested the next missions as I cound not pass the 3rd mission with this issue. I am on OPENBETA M2000c Pilot :pilotfly:
DimSim Posted October 21, 2020 Posted October 21, 2020 (edited) Same issue for me. HUD Heading tape/indicator is incorrect. I have special option 'INS does not require alignment' on. This occurs only for Mission 3 of Red Flag campaign to my knowledge. I tested some Instant Action and loaded Mission 1,2 and 4 into the Editor. Those all started correctly. I loaded Mission 3 into the Editor and changed the date from 23 Jul 2012 to April 2012 and Oct 2020. Each date change caused the heading to start at different position. It seems the INS setting is not honored for this mission. Yet selecting the player craft shows 'Enforce INS Align & Drift' is Off. Work around: Performing the INS alignment procedure, (even without editing the Lat, Lon digits which are not accurate), causes the heading to align to correct value after first phase. EDIT: Work around inadequate, see next post. Running Beta build 2.5.6.55960 Edited October 22, 2020 by DimSim
DimSim Posted October 22, 2020 Posted October 22, 2020 My work around was inadequate, even with the heading tape correct, the waypoints remain incorrect. This makes the mission unplayable at this present time. Track file linked (attachment too large). m2000_red_flag_mis3_bad_ins_wpt1.trk https://mega.nz/file/09EizTwJ#KejzoeLbvSQjGq0Hq1L7srBwOeHZ8caAeBYbzOWnEsg
LordOrion Posted November 18, 2020 Posted November 18, 2020 Same issue here: I had yo skip the mission to go on RDF 3rd Fighter Squadron - "Black Knights": "Ar Cavajere Nero nun je devi cacà er cazzo!" "I love this game: I am not going to let Zambrano steal the show." ~~~~~~~~~~~~~~~~~~~~~~~~~ CPU: i7-11700K@5GHz|GPU: RTX-4070 Super|RAM: 64GB DDR4@3200MHz|SSD: 970EVO Plus + 2x 980 PRO|HOTAS Warthog + AVA Base + Pro Rudder Pedals|TrackIR 5|
baltic_dragon Posted November 19, 2020 Posted November 19, 2020 OK I will be looking at some M2K missions so will try to finally sort this one out too! For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
baltic_dragon Posted December 4, 2020 Posted December 4, 2020 OK, it seems that this is the only mission that has "enforce INS alignment and drift" enabled. I have never noticed the problem, because I always perform the full INS alignment at mission start... could that be the problem? I also never used the autostart function. In other words, if you launched the aircraft manually, inserted correct position into the INS and ran full alignment it should work as intended. Or am I missing something? For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
Recommended Posts