Mr_sukebe Posted December 3, 2019 Share 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. System: 9700, 64GB DDR4, 2070S, NVME2, Rift S, Jetseat, Thrustmaster F18 grip, VPC T50 stick base and throttle, CH Throttle, MFG crosswinds, custom button box, Logitech G502 and Marble mouse. Server: i5 2500@3.9Ghz, 1080, 24GB DDR3, SSD. Link to comment Share on other sites More sharing options...
MYSE1234 Posted December 3, 2019 Share 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. [sIGPIC][/sIGPIC] i7-10700K @ 5GHz | RTX 2070 OC | 32GB 3200MHz RAM | Link to comment Share on other sites More sharing options...
Marsvinet Posted December 3, 2019 Share 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. Link to comment Share on other sites More sharing options...
Mr_sukebe Posted December 4, 2019 Author Share 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. System: 9700, 64GB DDR4, 2070S, NVME2, Rift S, Jetseat, Thrustmaster F18 grip, VPC T50 stick base and throttle, CH Throttle, MFG crosswinds, custom button box, Logitech G502 and Marble mouse. Server: i5 2500@3.9Ghz, 1080, 24GB DDR3, SSD. Link to comment Share on other sites More sharing options...
Recommended Posts