Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Baneslave]

When it's blatantly obvious there's no need for smileys

When you are dealing with non-native English speakers, you should.

This is badly off topic, though, so lets leave this issue without other words.

[Draco18s]

It's not a case of making tasks take fewer ticks, but more a case of introducing 'frame-skip'.

Except that frame skip doesn't work for algorithmically generated game play.  If it takes 10ms to run A* it takes 10ms to run A*.  You can't just "skip" it.  Same thing for water, water has an algorithm.

All frame skipping would do is skip the "wait" commands such that instead of running A* for each dwarf every 100 ticks it runs it every 50.  Which means it's doing twice as much work.

Wait.  Weren't we trying to reduce CPU load?

THOSE WAITS ARE IN THERE FOR A REASON.  It means DF can use the time running other subsets of algorithms so that everything can run at a different time, yet synch up in real time.

[irmo]

It's not a case of making tasks take fewer ticks, but more a case of introducing 'frame-skip'.

Which doesn't work, because DF displays frames as fast as it can do the underlying calculations. The game can't "skip" the next frame and go to the one after that because it doesn't know what's going to happen two frames from now. It has to simulate game time up to the first frame, and then the second. Displaying the frame on the screen is trivial.

[Makrond]

I meant tick-skip. Literally, do algorithms less often.

It's why there were quotation marks around it. A bit hard to understand, I know. It's why I prefer face-to-face communication over forums, but there you go.

[Mikademus]

Afaik DF already does not run all algorithm every update.