Hippo Posted December 9, 2024 Posted December 9, 2024 (edited) Not a big deal as I can get around it by zooming in until there is separation, but it seems like odd behaviour. I notice that if I place a unit icon (I was using an il-76) or its waypoint over the threat circle (yellow) ring of a ground unit (I was using an SA-10 group), the unit icon or waypoint becomes unselectable. Is this intentional? Or maybe I'm doing something wrong? In the image, I'm unable to select WP3 or WP0 (by clicking on them with the mouse, and so am unable to move them). Edited December 9, 2024 by Hippo 1 System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, 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 Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
Hippo Posted December 9, 2024 Author Posted December 9, 2024 9 minutes ago, buceador said: Is this in-game (F10) or in ME? ME System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, 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 Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock, Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals
buceador Posted December 9, 2024 Posted December 9, 2024 Confirmed. Waypoint OVER threat circle.miz 1
razo+r Posted December 9, 2024 Posted December 9, 2024 1 hour ago, Hippo said: Not a big deal as I can get around it by zooming in until there is separation [...] As a workaround, instead of zooming, you can also just disable the detection ring with the button on the top right in the mission editor. 1 1
buceador Posted December 9, 2024 Posted December 9, 2024 1 minute ago, razo+r said: As a workaround, instead of zooming, you can also just disable the detection ring with the button on the top right in the mission editor. Or don't place the waypoint exactly on the threat ring 1
rob10 Posted December 9, 2024 Posted December 9, 2024 3 hours ago, buceador said: Or don't place the waypoint exactly on the threat ring That doesn't work simply because at different zoom level's the unit moves in relation to the ring (if you zoom out it will likely get closer to the ring because the scale goes up so 4 nm away may be shown a directly on top). I can confirm both the behaviour and need to adjust zoom to allow selection. Likely a rendering order thing, and the fix might have equally problematic unintended consequences.
ED Team f-18hornet Posted December 11, 2024 ED Team Posted December 11, 2024 Thank you, reported. 1 AMD Ryzen 9 3900X, GeForce RTX 2080Ti, 32 GB DRAM, HOTAS TM Warthog, FSSB R3 Lighting, MFG Crosswind, Win 10 Pro
Recommended Posts