anirothan Posted February 14, 2017 Posted February 14, 2017 (edited) This is weird one to report. I the month of January, the magnetic declination in the INS has a value of 102.8 :helpsmilie: In months other than January, the INS reads a magnetic declination of 6.0 (or very close to that). I have tested this by hot-starting in Vaziani, at parking position 73, at various dates. For comparison, I have used an A10C at the same position and dates. Specifically, in December, February, March and June the M2000C's INS always has a magnetic declination of around 6.0 which is consistent with the A10C's value. However, in January the M2000C reads 102.8 whereas the A10C reads E6.0 (MV entry in POSINFO in the CDU). I have tested this in both Open Beta ( 1.5.6.1938 ) and stable releases and observed the same behavior. In all cases true heading seem's to be accurate. I can provide mission/track files or screenshots upon request, but this should be fairly easy to reproduce. This bug report seems to be related to the following reports: https://forums.eagle.ru/showthread.php?t=183063 https://forums.eagle.ru/showpost.php?p=3051186&postcount=4 Edited February 15, 2017 by anirothan 1
Winterz Posted February 15, 2017 Posted February 15, 2017 Yep and it's been a while! https://forums.eagle.ru/showthread.php?t=173902
GreyEcho Posted February 17, 2017 Posted February 17, 2017 Same problem here. It's especially annoying since a huge part of the campaign happen to be in January. I wonder if the pilot can change the declination manually in the Mirage while in Prep Waypoint 00 ? Intel i5-2500k - Gigabyte P67X-UD3-B3 - AMD HD7950 - RAM 12Go - SSD 250Go - Acer FHD Screen - Logitech G940 - TIR5 - FC3 - M-2000C - A-10C [sIGPIC][/sIGPIC]
anirothan Posted February 17, 2017 Author Posted February 17, 2017 I think I tried changing the magnetic declination manually before and after alignment and it could not be done. The magnetic declination seems to be preset even before alignment starts. You can see it any time by setting PCN to DEC. For the part of the campaign that takes place in January, you can still set the HSI to Cv NAV and use true headings/bearings. You can get a magnetic heading/bearing by adding 6 degrees, since the correct magnetic declination is 6.0 degrees to the east.
GreyEcho Posted February 18, 2017 Posted February 18, 2017 Yep, that's what I ended up doing, but before noticing it, that was very confusing. Especially on mission 3 I think, when you are supposed to go 180 after passing a TACAN station. My question was poorly worded, I meant to say: "I wonder if the real Mirage pilot can change the declination manually, and if so, would this be something added by RAZBAM, for example by switching the PSM to VEI before alignment, setting the PCN to DEC, and editing Waypoint 00 ? Intel i5-2500k - Gigabyte P67X-UD3-B3 - AMD HD7950 - RAM 12Go - SSD 250Go - Acer FHD Screen - Logitech G940 - TIR5 - FC3 - M-2000C - A-10C [sIGPIC][/sIGPIC]
Azrayen Posted February 18, 2017 Posted February 18, 2017 Yes they can. Probably done by preparation crew more than pilots (declination doesn't change overnight), unless we're talking long "ferry" flights. Not implemented (yet) in DCS. Is it useful is a real question, as without the current bug we wouldn't ever had the need to do so. I'm more in favor of fixing the january bug; seems simpler (=quicker) to do than to add the DEC setting feature. ++
myHelljumper Posted February 18, 2017 Posted February 18, 2017 Yes they can. Probably done by preparation crew more than pilots (declination doesn't change overnight), unless we're talking long "ferry" flights. Not implemented (yet) in DCS. Is it useful is a real question, as without the current bug we wouldn't ever had the need to do so. I'm more in favor of fixing the january bug; seems simpler (=quicker) to do than to add the DEC setting feature. ++ Both would be best, the manual state that the DEC data is editable so I think it should be. Helljumper - M2000C Guru Helljumper's Youtube https://www.youtube.com/channel/UCK3rTjezLUxPbWHvJJ3W2fA
Pikey Posted February 21, 2017 Posted February 21, 2017 https://forums.eagle.ru/showthread.php?t=183442 It's more like the magnetic heading has changed than the declination, but the end result is the same, in january the compass points 90 degrees left. Which is a killer for winter maps since designers often pick it as winter for the textures. And lazy people like myself dont align and scramble and use Horizon secours. ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *
ruddy122 Posted February 27, 2017 Posted February 27, 2017 Thank you for the post I thought I was doing something wrong. I rarely fly with winter textures. I never noticed it before. Thanks Sent from my iPhone using Tapatalk [sIGPIC][/sIGPIC] LUCKY:pilotfly::joystick: Computer Specs CPU: AMD Ryzen 5 2600 6-Core 3.4 GHz| GPU: Nvidia GeForce GTX 1660 6Gb | RAM: 32 GB DDR4 @ 3000 MHz | OS: Win 10 64 bit | HD: 500 Gb SSD
Zeus67 Posted February 28, 2017 Posted February 28, 2017 This is weird one to report. I the month of January, the magnetic declination in the INS has a value of 102.8 :helpsmilie: In months other than January, the INS reads a magnetic declination of 6.0 (or very close to that). I have tested this by hot-starting in Vaziani, at parking position 73, at various dates. For comparison, I have used an A10C at the same position and dates. Specifically, in December, February, March and June the M2000C's INS always has a magnetic declination of around 6.0 which is consistent with the A10C's value. However, in January the M2000C reads 102.8 whereas the A10C reads E6.0 (MV entry in POSINFO in the CDU). I have tested this in both Open Beta ( 1.5.6.1938 ) and stable releases and observed the same behavior. In all cases true heading seem's to be accurate. I can provide mission/track files or screenshots upon request, but this should be fairly easy to reproduce. This bug report seems to be related to the following reports: https://forums.eagle.ru/showthread.php?t=183063 https://forums.eagle.ru/showpost.php?p=3051186&postcount=4 It is a DCS bug. They fixed it and then it made a comeback when 1.5.6 was released. Something about the left hand not knowing what the right one did. I'm pushing ED for a fix. "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."
Boxin Posted March 5, 2017 Posted March 5, 2017 Yep, that's what I ended up doing, but before noticing it, that was very confusing. Especially on mission 3 I think, when you are supposed to go 180 after passing a TACAN station. My question was poorly worded, I meant to say: "I wonder if the real Mirage pilot can change the declination manually, and if so, would this be something added by RAZBAM, for example by switching the PSM to VEI before alignment, setting the PCN to DEC, and editing Waypoint 00 ? This just happened to me (mission 2 btw) It's how I came to find this thread. I didnt even notice until I restarted the mission and messed with the HSI. I thought I was going bonkers. i9-9900k | 2080 Ti ftw ultra | 32gb DDR4 3200 | Oculus hmd | HOTAS Warthog | MFG Crosswind | MFD Cougar
Rolds Posted March 6, 2017 Posted March 6, 2017 Thanks so much for finding this! It affects the campaign and I was going nuts trying to figure out what I'd done wrong!
Redglyph Posted April 1, 2017 Posted April 1, 2017 Was it fixed finally? It seems I just had this problem again, or I did something wrong with the INS. System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR
Redglyph Posted April 2, 2017 Posted April 2, 2017 Ah well, I'll just edit the date then. Thanks! System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR
azm Posted May 20, 2017 Posted May 20, 2017 Any progress for this bug? Got DEC=100.4 in open beta yesterday.
Redglyph Posted May 20, 2017 Posted May 20, 2017 I was wondering the same, should we post a report in the DCS bug section? System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR
myHelljumper Posted June 29, 2017 Posted June 29, 2017 is the bug fixed ? AFAIK it isn't. Helljumper - M2000C Guru Helljumper's Youtube https://www.youtube.com/channel/UCK3rTjezLUxPbWHvJJ3W2fA
amalahama Posted June 29, 2017 Posted June 29, 2017 If the magnetic declination knob was operative... *sigh*
baltic_dragon Posted June 29, 2017 Posted June 29, 2017 Guys I edited all the January missions and changed the date to February. Note that the briefigs and all the rest didn't change, this is just a temporary system-wise solution and will be available with the next update. 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.
flanker0ne Posted October 16, 2017 Posted October 16, 2017 The January Bug goes far beyond the simple setting of magnetic variation value. In fact, by lowering the backup compass, it can be seen that it is also influenced by it SCOPRI DI PIU': https://www.amvi.it/joinus.php DISCORD COMBINEDOPS The Battle Planning Tool
Recommended Posts