A further note:
It's the way it works, it will render faster when there are more surfaces and polygons in view.
EDIT:OOPS did I really write that?!? Of course I meant:
It's the way it works, it will render slower when there are more surfaces and polygons in view.
Dependng on the hardware, the Rate may toggle: from reaching full 60 HZ (using Flip 1) and dropping down to only 30 Hz frequently. This feels very "stuttering". You may try to use "Flip 0" and see if this was the cause.
The sooner or later you should use something like Delta correction, where the elapsed frametime is used to as a factor to be multiplied with all motion commands, so, no matter how the framerate is, the players stepwidth will always be relative to the elapsed time.
PS to speed things up you may try to use CopyEntity for the cubes, instead of CreateCube (well the very first cube must be made using CreateCube noless, of course).
It's the way it works, it will render faster when there are more surfaces and polygons in view.
EDIT:OOPS did I really write that?!? Of course I meant:
It's the way it works, it will render slower when there are more surfaces and polygons in view.
Dependng on the hardware, the Rate may toggle: from reaching full 60 HZ (using Flip 1) and dropping down to only 30 Hz frequently. This feels very "stuttering". You may try to use "Flip 0" and see if this was the cause.
The sooner or later you should use something like Delta correction, where the elapsed frametime is used to as a factor to be multiplied with all motion commands, so, no matter how the framerate is, the players stepwidth will always be relative to the elapsed time.
PS to speed things up you may try to use CopyEntity for the cubes, instead of CreateCube (well the very first cube must be made using CreateCube noless, of course).