[FIXED] Game speed question

[orca]

For a scenario I am working on I’ve created multiple unit enter area triggers based on circles of reference points fixed to an enemy carrier. The different sets of circle reference points are at various distances from the carrier creating the multiple different unit enters area triggers.

I suspect the answer is no, but do reference points have any significant impact on game speed?

And does having a large number of triggers such as unit enters area have a significant impact on game speed?

Thanks

[DWReese]

I don't have a definitive answer for you but, like you, I use a lot of Reference Points, and I don't see any diminished speed.

What is probably more telling is that "AU" counter in the bar above the map. In most cases, it has been stated that a value under 1500 is great, and a value over 2000 will definitely slow things down. I would assume that those numbers have something to do with the amount of memory used, so that is probably more indicative of slow speed than the number of reference points by themselves.

That's just my opinion.

Doug

[Whicker]

AU counter - never seen that before, poked around and under Game Options>> Map Display >> Show diagnostics, now there are a couple more things above the map, AU is one of them.

Cool!

[Rory Noonan]

Lots of area triggers will slow things down too if I'm not mistaken

[AlphaSierra]

When things get too hectic and I need to slow the game down...

I throw up 4 satellites.

[hasler]

Ya sats slow things down fast. I am working on 4K stating AU scenario. Rann very fast until I gave PACT and NATO two sats each. Oh well 5x max just gives the player incentive to kill faster.

[Dimitris]

ORIGINAL: hasler
Ya sats slow things down fast. I am working on 4K stating AU scenario. Rann very fast until I gave PACT and NATO two sats each. Oh well 5x max just gives the player incentive to kill faster.

Can you post or PM me that scen if possible? I'd like to check that bottleneck. Thanks!

[Dimitris]

bump

[Dimitris]

bump

[Dimitris]

Guys, are we ever going to get a save that clearly demonstrates this or is it going to remain one more unsubstantiated anecdote?

[AlphaSierra]

I thought your request was directed to hasler. I quit using Satellites a long time ago, for this reason.

Take any scenario in the community pile and strip out the Sat's time it and add them back in, you will see quite easily.

If that doesn't get you what you want, then I guess I can build you a scenario.

HP

[AlphaSierra]

This was a sandbox I was playing with but I just gave up because of the brutal hit.

The idea was to find the SAT's with a path over my AOR
then strip out all the others

My thoughts at the time were to ask for a setting to shut off the sensors just to speed them up

I gave up

[Dimitris]

I checked this now, using B998.16. There is a problem with that scenario, but it has nothing to do with the _number_ of satellites.

The problem is that 12 of the satellites, all of them in GEO (mostly Vortex / Orion / Mentor SIGINT birds but also a SBIRS-High) seem to have a problem with their orbits and they constantly "blink" between positions. This could be either a problem with the orbital data or a GEO-specific flaw in the orbital code. We'll have to check either way.

Once I removed these culprits, the other 101 sats sailed through like butter.

If you had brought this to our attention earlier, we would have been able to help you earlier.

[AlphaSierra]

Nice!

let me know if you get a fix.

In the meantime can you highlight a screenshot on which ones to remove?

Thank you

[Dimitris]

The problematic sats are:

* USA 105
* USA 110
* USA 112
* USA 118
* USA 136
* USA 171
* USA 184
* USA 200
* USA 202
* USA 223
* USA 230
* USA 237
* USA 241
* USA 259

[AlphaSierra]

BZ!

Much Appreciated

[AlphaSierra]

Just when I thought....

I swear all I did was tell em to engage opportunity contacts.

That took the game to her knees


I just discovered this a few minutes ago.

[Dimitris]

Reran this scenario now with the current build and no slowdowns have occurred. Marking this as fixed.