Mr_sukebe Posted December 3, 2019 Posted December 3, 2019 Trying to check as to whether anyone else is experiencing the issue that I'm having. Just tried my Viggen on two different maps (Gulf and NTTR) and when I tried changing an existing waypoint into a target point, the waypoint didn't change to an "M", and the range went nuts. Not sure if this is an error on my side, or not. 7800x3d, 5080, 64GB, PCIE5 SSD - Oculus Pro - Moza (AB9), Virpil (Alpha, CM3, CM1 and CM2), WW (TOP and CP), TM (MFDs, Pendular Rudder), Tek Creations (F18 panel), Total Controls (Apache MFD), Jetseat
MYSE1234 Posted December 3, 2019 Posted December 3, 2019 It works fine for me, using the open beta. What did you do to change it to a target point? Just to rule out incorrect procedures. Should be TAKT, 9 and then select the WP. Viggen is love. Viggen is life. 7800X3D | RTX 4070 Ti S | 64GB 6000MHz RAM |
Marsvinet Posted December 3, 2019 Posted December 3, 2019 It sounds like you entered the '9' into REF/LOLA instead of TAKT. That would give you a waypoint at 900000/000000 which is far away from anywhere. My thoughts at least.
Mr_sukebe Posted December 4, 2019 Author Posted December 4, 2019 It sounds like you entered the '9' into REF/LOLA instead of TAKT. That would give you a waypoint at 900000/000000 which is far away from anywhere. My thoughts at least. Spot on. Thanks chaps, resolved. Definitely an issue at my end, ie user ineptitude. 7800x3d, 5080, 64GB, PCIE5 SSD - Oculus Pro - Moza (AB9), Virpil (Alpha, CM3, CM1 and CM2), WW (TOP and CP), TM (MFDs, Pendular Rudder), Tek Creations (F18 panel), Total Controls (Apache MFD), Jetseat
Recommended Posts