Matrix Games Forums

Good Evening

I recently had steam update to 1527 from the previous Beta and have noticed that the pulse time has increased 10 fold.

I have included a copy of the scenario it 6310 AU so it probably more noticeable than smaller scenarios, nothing in it is moving, all planes and ships are currently in bases. In the previous beta it was pulsing 25-75ms, in 1527 it's now pulsing 771-1620ms. There are no errors in the logs but i have included them anyway.

EDIT: It has also become incredibly stuttery at faster time compression, to see this just put some aircraft in the air and speed up the time.

There are no changes to scenario between updates. Any further information require just let me know.

Also tested with Beta 1544 pulsing between 700-1600ms, 3D terrain rendering is not having any impact on pulse times.

Computer:

Ryzen 9 5950X running all 16 core multithreaded for 32 CPUs, Precision boost override, Speed 4.45GHz, Utilisation 7-12%, Ram 32Gb 3200MHz, Graphics RTX 3080 Ti. Windows 11 Pro, DirectX 12.

Save & Logs:


Thanks for your time.

Thanks for the report


Logged 0016506

Thanks for the scenario. We'll see what we can do.

This should be improved on the next update.

Excellent thanks Dimitris.

Unfortunately with 1566 it has got worse by another 150ms.

Edit: If you require any additional info or logs let me know and i'll upload them.

Thanks for your time.

Which "previous beta" are we comparing against ? Just so that I can understand what the comparison is.

Not 100% on the number but possibly 1493, looking through the logs i've gone from that to 1527.

I may have additional information i'm just rebuilding it to see if modifications to the aircraft sensors are the cause, it going to take me a little while to replace all the aircraft (approx. 4500) so bare with me on the testing for that.

I have definitely received a lot of fuse exceptions from cloning the modified aircraft (Exception: Object reference not set to an instance of an object.) in the scenario from x20, x400, x8000. Which is why i suspect it may be related to that. I will add the logs below in case they are helpful in the meantime while i replace aircraft with base models.

The exceptions will only happen once but the scenario version is early enough to make them happen. To replicate set to ferry any of the following aircraft; B-21 Raider at RAF Fairford, B-1B Lancer at RAF Alconbury, ScanEagles at RNAS Culdrose, B-52J at RAF Mildenhall launch one and clone around 36x, group and land back at the air bases they came from. I did rename each one at the time but it doesn't seem necessary for the exception which is Object reference not set to an instance of an object.There are probably others as well that will do it but i can't remember them all.

Logs:
Thanks for your time and any further info required please let me know.

Unfortunately the rebuild didn't help with pulse times, it did stop the Fuse Exceptions though. If you require the latest version (it's about a 1000 units less) let me know.

Thanks for your time.

Good Afternoon

I think this is related to the detect stuck unit with pulses tick box, when not ticked pulse time is about 30ms when ticked it is 500-900ms. Specifically the save pre-pulse scenario copy box seems to have most impact.

Thanks for your time

Yes, that's WAD, there's clearly stated that the save prepulse has a huge impact in performance and it's only used for debugging purposes

blu3s wrote: Tue May 06, 2025 5:09 pm Yes, that's WAD, there's clearly stated that the save prepulse has a huge impact in performance and it's only used for debugging purposes

Thank you, feel free to mark this as fixed or WAD from my point of view.

Edit: I'm actually seeing an improvement of speed as well with 1645 so thanks for that as well.