This in the code should be improved:

-make the turnspeed timeindepentednt
(time_factor in the player.pan rotation)

-use a camera.arc of 80 to 90, its just the standard currently,
wich does not fit for shooters.

-i could see me own playermodel when walking backwards,
try to make it invisible

I always thought that the movement of the mouse was the only thing that should be left dependend on the frame rate.
thanks for the other code suggestions. the weapon is also a bit dependent on the framerate, bad programming on my side.

I'd like to join you tonight, too, but i got no computer that can run the game fluently right now.

EDIT: sorry martek, your 12k points might as well be the record, but i don't save the log files. i only verified the record of germanunkel because it looked really high for me and it was the highest number that had been posted.

Somebody wants to join now?

when?

Well, now. In the next moment.

I ran the game on a very slow PC, so there is a noticable
reduction in the turnspeed in high-FPS consuming views given the
same mouse-speed input.
The goal should be to have the same angle per second rotation
no matter how the FPS are.

You might not have noticed it on a fast PC with FPSMax on,
as this automatically creates steady framerates.

in the gamestudio manual they use mouse_force without multiplied time_step...

Well, and the manual is using it simpy wrong,
as it is not framerate independent.
Its just a short code-snipplet to show how the vector
works.

Beat my record around 152000!

You're not serious .
My record is around 40000 but after around 2 seconds i get the sweet Connection lost message.