Rhinozherous Posted June 25, 2022 Share Posted June 25, 2022 Hello! I watched this video where he talks right in the beginning about the Target Ageout Time for Bricks and HAFUs: https://youtu.be/0tisJn9naSE Is this "correct as is" or is it really wrong implementation and will it be corrected if it is? (Or is it already corrected, as the video is a few months old) Thanks! i7-14700KF 5.6GHz Water Cooled /// ZOTAC RTX 4070 TI Super 16GB /// 32GB RAM DDR5 /// Win11 /// SSDs only DCS - XP12 - MSFS2020 Link to comment Share on other sites More sharing options...
Tholozor Posted June 25, 2022 Share Posted June 25, 2022 MSI trackfile memory mechanics aren't implemented at the moment, so it's still tied to the aging setting. REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/ Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted June 25, 2022 ED Team Share Posted June 25, 2022 Hi, What we have in game is correct, it is based on time, not based on the number of complete frames. 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, HP Reverb G2 Link to comment Share on other sites More sharing options...
CaptPickguard Posted July 8, 2022 Share Posted July 8, 2022 I feel honored to have been cited, but I am absolutely not an expert! When I created the video I was incorrect in my assumption that the bricks were timing out based on number of sweeps. They absolutely timeout based on time. The issue I was actually alluding to was not, however, how the bricks timeout, but rather how that setting affects trackfile deletion. As a general rule for myself, I never delve into official documentation, so I'll let someone actually familiar talk about this particular issue. Link to comment Share on other sites More sharing options...
Hulkbust44 Posted July 11, 2022 Share Posted July 11, 2022 Hi, What we have in game is correct, it is based on time, not based on the number of complete frames. thanksThen what is the basis for the time a track is held in DCS? Link to comment Share on other sites More sharing options...
Swift. Posted July 12, 2022 Share Posted July 12, 2022 (edited) On 6/25/2022 at 8:44 PM, BIGNEWY said: Hi, What we have in game is correct, it is based on time, not based on the number of complete frames. thanks Just clarifying, you mean the aging for the bricks is correct? The track memory logic is still WIP last I checked. Edited July 12, 2022 by Swift. 4 476th Discord | 476th Website | Swift Youtube Ryzen 5800x, RTX 4070ti, 64GB, Quest 2 Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted July 12, 2022 ED Team Share Posted July 12, 2022 In the available docs we have on this, it indicates that it based on time. If you have unclassified information that it should be different feel free to PM me. 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, HP Reverb G2 Link to comment Share on other sites More sharing options...
raus Posted July 12, 2022 Share Posted July 12, 2022 (edited) @BIGNEWY I think there are two different topics being discussed here: - time vs frames: you have explained your docs say the setting is time-based rather than frame-based. Point taken. Personally, I think it is correct. -Meaning of the setting: here comes the controversy. Current implementation makes the time for both brick aging (persistency) and track „lifetime“. The opinion we are expressing -and cross-checked with Hornet pilots and other SMEs- is that it should apply to persistency of the bricks on screen, but not to the underlying track lifetime, and we should not have bricks fading constantly across the DDI, not to lose tracks if the tracking volume is big. some feedback/status about the second point would be greatly appreciated Edited July 13, 2022 by raus Typos 8 GV5Js DATACARD GENERATOR Link to comment Share on other sites More sharing options...
Recommended Posts