dorianR666 Posted September 26, 2020 Posted September 26, 2020 once you approach a waypoint, its symbol is displayed at a wrong place on the HSI page on attached images, the selected waypoint is part of the sequence, yet isnt placed on the sequence line (the line is correct). once you almost arrive, the waypoint symbol rapidly moves along a circular path around the ownship symbol to appear behind the ownship symbol (again, at an incorrect place).hsibug.trk CPU: AMD Ryzen 5 1600X GPU: AMD RX 580
dorianR666 Posted September 26, 2020 Author Posted September 26, 2020 SA is just as broken. CPU: AMD Ryzen 5 1600X GPU: AMD RX 580
ED Team BIGNEWY Posted September 26, 2020 ED Team Posted September 26, 2020 Reported thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
isotaan Posted December 7, 2020 Posted December 7, 2020 I haven't experienced this until the last patch, but now I'm seeing every time I fly the Hornet. Some of the folks I fly with report similar issues while others haven't noticed it at all.
Hippo Posted April 18, 2021 Posted April 18, 2021 Bump. Is this still an open issue? I have several missions where I'm still seeing this behaviour. System spec: AMD Ryzen 7 9800X3D @ stock, MSI GeForce RTX 5090 Ventus 3X OC 32 GB DDR7, Gigabyte X870 Gaming X, Corsair Vengeance LPX 32GB EXPO (2 x 16GB) DDR5 5300MHz C30, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, Thrustmaster Pendular Rudder
ED Team BIGNEWY Posted April 18, 2021 ED Team Posted April 18, 2021 this is fixed in 2.7 if you ae still seeing an issue please add new short track replays showing examples. thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Hippo Posted April 18, 2021 Posted April 18, 2021 (edited) Thanks for the quick reply. I can confirm that I am still seeing this issue. Although it is a set of missions I created some time ago, so was wondering if it could be due to that. Will post track shortly. Edited April 18, 2021 by Hippo System spec: AMD Ryzen 7 9800X3D @ stock, MSI GeForce RTX 5090 Ventus 3X OC 32 GB DDR7, Gigabyte X870 Gaming X, Corsair Vengeance LPX 32GB EXPO (2 x 16GB) DDR5 5300MHz C30, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, Thrustmaster Pendular Rudder
Hippo Posted April 18, 2021 Posted April 18, 2021 (edited) Here it is. Go to around 07:45 (edit: SORRY 07:35) as I approach WP1. Note on the HSI how the WP symbol jumps and the A/P CPL can't deal with it (edit: apologies again, the A/P does deal with it, but because the WP suddenly jumps to being behind the aircraft it starts a 180 turn to the left - so the route cannot be flown correctly using A/P CPL, AUTO). I then disengage the A/P and have to set WP2 manually (i.e it doesn't automatically cycle). The issue is clearer as I approach WP2 and WP3 which should be on the "corners" of the route. P.S. Not shown on track, and I have posted about it before, but it doesn't appear to be possible on the runway to activate AUTO on the HSI before the aircraft starts moving. Thanks for replying, and thanks for all the fixes / additions in 2.7 (esp. the command heading on HUD now accounting for drift). Sorry the track is not "short", but hopefully not too much of a problem. Edit: This doesn't appear to be an issue in all missions. Perhaps it has something to do with the waypoints being at a high altitude for this one (34,000 ft)? hsi_wp.trk Edited April 19, 2021 by Hippo System spec: AMD Ryzen 7 9800X3D @ stock, MSI GeForce RTX 5090 Ventus 3X OC 32 GB DDR7, Gigabyte X870 Gaming X, Corsair Vengeance LPX 32GB EXPO (2 x 16GB) DDR5 5300MHz C30, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, Thrustmaster Pendular Rudder
Hippo Posted April 23, 2021 Posted April 23, 2021 (edited) I flew the mission again and this is now appears to be working correctly following the latest update. Thank you. Edited April 23, 2021 by Hippo System spec: AMD Ryzen 7 9800X3D @ stock, MSI GeForce RTX 5090 Ventus 3X OC 32 GB DDR7, Gigabyte X870 Gaming X, Corsair Vengeance LPX 32GB EXPO (2 x 16GB) DDR5 5300MHz C30, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, Thrustmaster Pendular Rudder
Hippo Posted April 23, 2021 Posted April 23, 2021 (edited) However, I am now seeing another issue that I was not seeing previously. In the same mission I take off with WP1 selected, and turn on CPL A/P. AUTO is not selected. If I select AUTO the WP is changed to WP0. Is this the expected behaviour? Shouldn't it stay on WP1 (which is what was happening in the previous version)? See track for details. I turn AUTO on and off several times and it appears to be ok, but it eventually happens (I think when I am far enough from WP0). Interestingly, if I replay the track from the other day (above), this behaviour is now seen, whereas it wasn't with the previous version. auto_wp0.trk EDIT: Pls ignore, have opened a new post for this. Edited April 24, 2021 by Hippo System spec: AMD Ryzen 7 9800X3D @ stock, MSI GeForce RTX 5090 Ventus 3X OC 32 GB DDR7, Gigabyte X870 Gaming X, Corsair Vengeance LPX 32GB EXPO (2 x 16GB) DDR5 5300MHz C30, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, Thrustmaster Pendular Rudder
dorianR666 Posted May 14, 2021 Author Posted May 14, 2021 this is now fixed 1 CPU: AMD Ryzen 5 1600X GPU: AMD RX 580
Recommended Posts