Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Subject:
Message icon:

shortcuts: hit alt+s to submit/post or alt+p to preview

Please read the rules before you post!


Topic Summary

Posted by: Father Tim
« on: April 25, 2020, 09:39:40 PM »

Also the sub-pulses pretty much only do movement & sensor checks and not even all of those.
Posted by: skoormit
« on: April 25, 2020, 04:04:45 PM »

Not everything is updated every tick. 
A lot (most) of the economic stuff happens once every construction cycle (5 days by default, but changeable). 
Posted by: Narhalles
« on: April 25, 2020, 03:57:43 PM »

As an outsider looking at the end game, I have no idea of how the game simulates on a per tick basis.   However, it appears that everything in the game is updated every tick.   (be that 5sec or 30 days) sub ticks look to run more frequently and serve to drop the sim speed if an event needs to be handled, at which point everything gets processed.   However, if this is the case then it would probably be worth only siming the affected system, or even the local area of the affected event (combat, sensor contact, etc) and if that impacts the player then it could drop the overall sim time and do standard interrupts, but in other cases only simming a limited set of data on a lower tick level than selected and putting that in the background could drastically increase performance. 

Another idea would involve seperating out simming of ships/missles from economy from stellar movement.  Thus, events that dont need to be performed every tick update (such as movement of planets on less than a 1 day scale) dont get updated when on lower tick increments.