unknown Posted April 29, 2018 Share Posted April 29, 2018 I have a problem with the RB-15 after the update to 2.5.1OB. I select BX 8, press T1 and move the cross/circle over the target(pic1) and press TV and now the circle jumps from my target to the right(pic2). This reminds me a little to the problem with the RB75 we had earlier. I launched the RB-15 and they followed the BX7 and 8 waypoints, but because the BX8 was not on the target they just flew past them(to the circle on the radar screen). Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
RED Posted May 4, 2018 Share Posted May 4, 2018 Same problem here. I'll produce a track later. Inputting Bx waypoints with Lo/La works fine, but updating them through radar makes them jump elsewhere (more than 100 km). Really confusing while learning the RB15 procedure. Updating WPs without the radar worked for me. Link to comment Share on other sites More sharing options...
toilet2000 Posted May 4, 2018 Share Posted May 4, 2018 Yeah, it seems to do that for other types of "waypoints" too. I've had this problem on several occasions when using the radar to update a position (ie the waypoint being updated to a different position than the designation cross). I'll add it to the list of issues I've compiled on this forum section. Link to comment Share on other sites More sharing options...
tn_prvteye Posted May 4, 2018 Share Posted May 4, 2018 Thank god, I thought I was the only one. I was practicing this last night and I was very confused. Link to comment Share on other sites More sharing options...
unknown Posted May 12, 2018 Author Share Posted May 12, 2018 After yesterdays update to the DCS 2.5.1 OB branch i tried the Viggen with the RB15 again, to test if something changed. Something changed but sadly not like i hoped. The "jumping circle" is gone, because the whole circle is gone. If i try a radar fix for a Nav point i can move the marker on the radar screen - see video(pressing T1 move the marker, pressing T0 to abort). If i select BX8 and press T1, no marker on the radar screen and nothing to move, pressed T0 to abort. Even on the 120km scale, nothing to see. Is this maybe related to the course indicator bug - which appeared with the latest patch - showing always to the 6 o'clock position so that the radar marker is perhaps placed outside the radar screen - just guessing here. I was in ANF - ATTACK - mode. I hope YT doesn't need to long for processing the video for goog quality, should be aviable in 1440p. Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
Marduk879 Posted May 15, 2018 Share Posted May 15, 2018 Confirming this problem on my side aswell. Link to comment Share on other sites More sharing options...
abyss123100 Posted May 17, 2018 Share Posted May 17, 2018 When I'm ready to set my Bx8 waypoint, it just selects B2. I have no idea what's been going on, glad i'm not the only one. Link to comment Share on other sites More sharing options...
fjacobsen Posted May 23, 2018 Share Posted May 23, 2018 Seems to have been fixed with the 23rd may 2.5.2 update. i7-10700K 3.8-5.1Ghz, 32GB RAM, RTX 4070 12GB, 1 x 1 TB SSD, 2 x 2TB SSD2 TB, 1 x 2 TBHDD 7200 RPM, Win10 Home 64bit, Meta Quest 3. Link to comment Share on other sites More sharing options...
unknown Posted June 3, 2018 Author Share Posted June 3, 2018 Even though the F/A-18C is taking up most of my time now, thank you very much for fixing this bug! Just tried it with the latest DCS 2.5.2.18144 Update 2 for Open Beta and had no problems setting the BX - points. :thumbup: Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings Link to comment Share on other sites More sharing options...
Recommended Posts