Can you up the speed in singleplayer?

[Kasszz]

Dear KaM Remakers and players,

Is there a why to increase the speed of the game in singleplayer, but not to 300% trough the developer menu?

Casper

[Krom]

Hi Casper,

You can edit KaM_Remake_Settings.ini file in Notepad and edit these variables:

SpeedPace=100
SpeedMedium=3
SpeedFast=6
SpeedVeryFast=10

Pace determines tick duration (default 100msec) and Medium/Fast/VeryFast are multipliers linked with F6/F7/F8. So you can finetune speed you need by setting Pace to e.g. 75 and speedup to 2, this will result in perceived speed of 100% * 2 / 0.75 = 266%.

Don't forget to reset the changes before you join the multiplayer, I don't remember if these are overriden or not.

[Kasszz]

Thanks

[dicsoupcan]

but there is no need for that right? i mean in singleplayer you can just switch between gamespeeds by using the folliwing buttons:
F5 = normal speed
F6 = 3x speed
F7 = 6x speed
F8 = 10x speed

[pawel95]

but there is no need for that right? i mean in singleplayer you can just switch between gamespeeds by using the folliwing buttons:
F5 = normal speed
F6 = 3x speed
F7 = 6x speed
F8 = 10x speed

Yeah I think Krom didn´t understood the question. He just wanteed to know "how to speed up the game". What Krom wrote is, when you want 20x instead of 10x for F8-Button, you can change the settings with the notepad, like Krom just said

[Krom]

Yeah, I thought the guy referred to 300% = 3x, that's the minimal speedup one can have in SP, so I explained how to get smaller speedups like in MP (150%, 200%, 250%).
Anyway, now everything is covered

[Esthlos]

Hi Casper,

You can edit KaM_Remake_Settings.ini file in Notepad and edit these variables:

SpeedPace=100
SpeedMedium=3
SpeedFast=6
SpeedVeryFast=10

Pace determines tick duration (default 100msec) and Medium/Fast/VeryFast are multipliers linked with F6/F7/F8. So you can finetune speed you need by setting Pace to e.g. 75 and speedup to 2, this will result in perceived speed of 100% * 2 / 0.75 = 266%.

Don't forget to reset the changes before you join the multiplayer, I don't remember if these are overriden or not.

This is extremely interesting!
(Yes, I used the search function of the forum, yes, I tried to use these settings for a lazy implementation of interactive pause and no, it doesn't work)

I have a question...

Premise: As far as I understood, SpeedPace is the Tick's actual duration while the various speed settings are how many Ticks are computed per game logic update (is this correct?).
(Evidence: SpeedPace 10000 on x100 doesn't give smooth gameplay - at all)

Question: wouldn't it be better if, instead of being multipliers, the various speed settings (at least the default ones) changed the SpeedPace Tick duration to 33ms (x3), 17ms (x6), 10ms (x10), 1ms with 3 computations per update (x300)?
Would this give better performance on speedups or would it be worse/same/not worth it?

[Krom]

You can try setting SpeedPace=1 and seeing how it compares to SpeedPace=100 at x100 speed

[Esthlos]

You can try setting SpeedPace=1 and seeing how it compares to SpeedPace=100 at x100 speed

SpeedPace=1 feels very similar to SpeedPace=100 x10 (x ten, it's not a typo), but freezes the game if also sped up at x10 (it went back to "normal" SpeedPace=1 when set back to x1)
Do you know why doesn't it go faster, and why does it freeze?

[Krom]

The time has to be shared between CPU (computing game logic steps) and Input/GPU (responding to controls and drawing). If either one is overused, the game starts to freeze.

[Esthlos]

The time has to be shared between CPU (computing game logic steps) and Input/GPU (responding to controls and drawing). If either one is overused, the game starts to freeze.

Thanks.
But why doesn't Speedpace=1 go at the same game speed as x100?
Does it maybe spend 90% of the time on almost-unnoticeable micro-freezes, or is there another reason?

(By the way, KaM overloading a machine that can run X3: Terran Conflict's space battles on SETA 10 -which means x10 game speed- without going haywire is quite funny )

[Krom]

In first case we need 100 precise 1ms intervals with 1 update in each, in second - just one 100ms interval in which we dump 100 updates. 1ms ticks require sub-1ms precision from the OS, which is hard to get, so we did not bother.

P.s. How many real-time entities does X3 have?

[Esthlos]

In first case we need 100 precise 1ms intervals with 1 update in each, in second - just one 100ms interval in which we dump 100 updates. 1ms ticks require sub-1ms precision from the OS, which is hard to get, so we did not bother.

Thanks.

P.s. How many real-time entities does X3 have?

I'm not really sure what do you mean, but every small ship can have up to 8 (more or less) weapons each of which shoots 1 shot a few times per second (depends on the weapon) + sometimes a few missiles (can be homing or dumbfire, some split into smaller missiles after launch), and even small battles easily have a dozen of these crafts.
Bigger ships can have even more weapons (50 guns circa, usually in 6 turrets), but their turrets can also move and fire independently of the ships' movement.

There are also an universe worth of civilian, pirate, and military ships and stations not involved in the battle.
(Only those in the same sector as the player are rendered by the GPU - the rest run on a lighter weight simulation)

This video should give an idea: https://www.youtube.com/watch?v=Ua3zy9c59fg
(Albion Prelude is an expansion that uses Terran Conflict's engine but adds story, ship types, etc)

To be precise though my pc does go haywire on the biggest battles (4-5 capital ships and 40-50 fighters) with SETA on, so we're not talking about NASA-level computers.

[Krom]

Problem with KaM is that average game has up to thousands of entities (all units, all houses) all acting in real-time, finding hundreds of paths around and interacting with each other, also affecting fog-of-war (and AI internals, if AI is present). That puts a toll on CPU.

X3 on the other hand (from the looks of it) has little to no pathfinding, no dynamic fog-of-war and no complex logic that needs to run every tick.

[Esthlos]

has little to no pathfinding

I'd say it doesn't have it at all, judging from how easily ships crash into each other.

no complex logic that needs to run every tick.

It does have have this, though mostly in the merchant ships.
But I got your point, thanks.