YoYo Posted May 18 Share Posted May 18 I noticed that there is some offsetting of the waypoints (TIR on the HUD), not a bit (20-40 meters maybe) but actually it's quite important. Perhaps it is related to tuning the systems - but in this case I start in the air, the declination is ok (or near ok, QFE is right too, from the Kneeboard). Even though the points are marked correctly in the mission editor, there is quite a significant shift on the HUD (marked by red circle here). Any ideas why the TIR circle does not match the point from the editor? Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro Link to comment Share on other sites More sharing options...
Rudel_chw Posted May 18 Share Posted May 18 44 minutes ago, YoYo said: Any ideas why the TIR circle does not match the point from the editor? The Viggen does not nave INS or GPS for its navigation, instead it uses Dead Reckoning which is prone to drift over time. You need to do a Navigation Fix on the waypoint prior to the one of the target. 1 For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB Link to comment Share on other sites More sharing options...
YoYo Posted May 18 Author Share Posted May 18 Yes I know but even doing the visual fix (T1>TV, 1th waypoint), it doesn't change to much. Offset is present still. Maybe that's just how it's supposed to be? And is it normal that there is a shift of several dozen of meters? test.trk Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro Link to comment Share on other sites More sharing options...
YoYo Posted May 18 Author Share Posted May 18 (edited) I have the impression that it is simply something related to the editor, maybe. I noticed that even if you manually fix the waypoint (no matter what method, it can be radar), even by a large distance, it does not change the entire flight plan by that much, the point with the target is still in the same place, even though the position of B1 has changed and significantly so. Edit: right, if the waypoint is marked as M (target in ME) and you are doing the offset of the one waypoint, the target point is still in the same place (bug?). So maybe better use manual marking of the waypoint as a target with "9" on CK? But this still doesn't explain the corresponding shift. Maybe there's an error in declination right now? I noticed - default start (in the air) 6,5 on the knob In the kneeboard is 7,2 Edited May 18 by YoYo Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro Link to comment Share on other sites More sharing options...
YoYo Posted May 18 Author Share Posted May 18 (edited) test2.trk Generally, it seems to me that it is some kind of bug, when I gave directly M1 in the mission editor (without any WP), the TIR shows everything ok, the target center. All you need to do is add WP1 and it'll be in the wrong place right away. The flight is short enough that there should be no deviation. Also fix isnt needed according me due the short distanse (waypoints on the right place, see the first track). Edited May 19 by YoYo Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro Link to comment Share on other sites More sharing options...
TOViper Posted August 30 Share Posted August 30 Yoyo, is this still an issue? Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1 Link to comment Share on other sites More sharing options...
YoYo Posted August 31 Author Share Posted August 31 2 hours ago, TOViper said: Yoyo, is this still an issue? Hard to tell me, didnt fly on Viggen from few weeks. Sry. Webmaster of http://www.yoyosims.pl Win 10 64, i9-13900 KF, RTX 4090 24Gb OC, RAM 64Gb Corsair Vengeance LED OC@3600MHz,, 3xSSD+3xSSD M.2 NVMe, Predator XB271HU res.2560x1440 27'' G-sync, Sound Blaster Z + 5.1, TiR5, [MSFS, P3Dv5, DCS, RoF, Condor2, IL-2 CoD/BoX] VR fly only: Meta Quest Pro Link to comment Share on other sites More sharing options...
Recommended Posts