Pikey Posted February 3, 2017 Share Posted February 3, 2017 (edited) So I checked for a regression as I reported the last late activation with air radars and I'm not convinced this is ED's issue at all because of the radar being third party external and i tested air radar... BUT this needs fixed pronto, it's messing up the ability to do random spawns on a trigger, or literally any type of randomisation above the % active in the ME which appears to work fine. As title says; if you place late activation units int he mission, the radar detects them, even though they are not present. Really annoyed at myself only finding this on Friday :/ Edited February 3, 2017 by BIGNEWY TITLE 1 ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING * Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted February 3, 2017 ED Team Share Posted February 3, 2017 Thanks Pikey, reported 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, HP Reverb G2 Link to comment Share on other sites More sharing options...
Pikey Posted February 6, 2017 Author Share Posted February 6, 2017 Update to this as it's not just Late activation, there a second component bizarrely. if you set a units condition of appearance to 100%, THEN click late activation, the condition % greys out, as expected. However!!! If you set the condition to 50% and THEN set late activation, the % test is honoured first, so, if you set 10 groups with 50% possibility, then set them all to late activation, in game 50% appear on radar and 50% don't. which is kindda wierd as I would expect late activation to override % condition, which to me seems like the % condition is honoured AFTER late activation, in the line of code, making the cause be the order of which they are processed in code. Hope that helps the dev who got the ticket. ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING * Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted February 6, 2017 ED Team Share Posted February 6, 2017 Thanks Pikey, I will take a look and add the info as necessary 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, HP Reverb G2 Link to comment Share on other sites More sharing options...
swither Posted February 6, 2017 Share Posted February 6, 2017 fixed in latest internal build :) 2 /Daniel Heatblur Simulations Link to comment Share on other sites More sharing options...
Pikey Posted February 7, 2017 Author Share Posted February 7, 2017 Cool, thanks Daniel was gonna add that it affected SP only so the valid workaround is to run as a connected client and you don't see them pop up/ I'm sure not everyone can do that, but some might. Thanks to Delta99 for that find. ___________________________________________________________________________ SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING * Link to comment Share on other sites More sharing options...
david.lind Posted February 7, 2017 Share Posted February 7, 2017 Does this fix have an effect on the errant RWR performance? https://forums.eagle.ru/showpost.php?p=3039260&postcount=1 Link to comment Share on other sites More sharing options...
Recommended Posts