lwalter Posted August 2, 2020 Posted August 2, 2020 I'm trying to understand what's happening with the INS update, whether by fly-over or by radar slant range. With both methods, I get the cross pointing to where the INS thinks the WPT is. Then I use either REC by fly-over or the "INS update" button in OBL/TAS mode with the diamond on the correct location. The offset is shown and I press "VAL". The L/G of the WPT doesn't change. I suppose this is normal as this should be real L/G of the WPT and only the INS internals itself is updated. However, the cross seems to stay where it was before update. I would expect the cross to move to the updated point. Am I missing something here? iMac Retina 5K, 27-inch, i7 4 GHz, 32 GB RAM, AMD R9 M395X 4 GB | Thrustmaster HOTAS Warthog | Cougar MFD | MFG Crosswind | EDTracker Pro | Realteus ForceFeel DCS World | Bf109 | Fw190 A8/D9 | P47 | P51 | Spitfire | I16 | C101 | L39 | F86F | MiG15 | MiG19 | MiG21 | FC3 | A10C | AJS37 | AV8BNA | F5 | F14 | F16 | F/A18 | M2000 | JF17 | Christen Eagle | Yak52 | SA342 | UH1H | Mi8 | Ka50 | Combined Arms | NS430 | Persian Gulf | Normandy | Channel | Syria | NTTR | WWII Assets
lwalter Posted August 6, 2020 Author Posted August 6, 2020 answering to myself: looks like it's a bug according to this thread https://forums.eagle.ru/showthread.php?t=193008 iMac Retina 5K, 27-inch, i7 4 GHz, 32 GB RAM, AMD R9 M395X 4 GB | Thrustmaster HOTAS Warthog | Cougar MFD | MFG Crosswind | EDTracker Pro | Realteus ForceFeel DCS World | Bf109 | Fw190 A8/D9 | P47 | P51 | Spitfire | I16 | C101 | L39 | F86F | MiG15 | MiG19 | MiG21 | FC3 | A10C | AJS37 | AV8BNA | F5 | F14 | F16 | F/A18 | M2000 | JF17 | Christen Eagle | Yak52 | SA342 | UH1H | Mi8 | Ka50 | Combined Arms | NS430 | Persian Gulf | Normandy | Channel | Syria | NTTR | WWII Assets
Steph21 Posted August 7, 2020 Posted August 7, 2020 To make things short: INS drift and update are bugged, disable Gyro Drift in your options :thumbup:
Aernov Posted August 7, 2020 Posted August 7, 2020 Strange, I was able to update INS via OBL (radar slant range), and the waypoint cross moved closer to the actual WPT location (not exactly on the landmark, which, I assumed, was because of coordinates "scale" (degrees/minutes/two digits of seconds do not define a precise point)). Before update this cross was really far away (like 2-4 nm away after 2.5 hours of flight), and after - not farther than 200 meters.
Ramsay Posted August 7, 2020 Posted August 7, 2020 Before update this cross was really far away (like 2-4 nm away after 2.5 hours of flight), and after - not farther than 200 meters. When doing a INS update, any INS drift is zeroed out, this happens regardless of the method or aircraft position (as long as within range of the waypoint/coordinates being used to update the INS). The update is "perfect", however the HUD's waypoint cross is misaligned and the actual waypoint position is near the bottom of the top tick mark and not in the center of the cross. Note how the waypoint/vehicle stays near the bottom of the top "tick" More detail about INS updating can be found in this thread. https://forums.eagle.ru/showthread.php?p=4198819#post4198819 i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Recommended Posts