Suggestion to mappers [how to remove timer bu

Ok. As we all know all maps have timer bugs, cuz func_train objects are a bit bugged.

I was thinking much about it and found 2 ways. Will start from more uber correct one but maybe impossible by mapping, but what the hell - lets try:

1. Using sprites. Create a sprite with specific framerate (with it you can also make seconds like 0.01). Anyway, sprite is created now use some entity to disable sprite (if possible), so all datas are setted to 0. Now when button is pressed find a way to activate the sprite (if possible), so all framerate is started. Now finish button - some way to deactivate sprite, so frame switching will be changed. Some information about framerate - it actually doesn't use frames - it uses hl time what is working under 32 byte system (good enough for 0.01 seconds).

2. This way is more classic and is possible and has no timer bugs (however it has bugs with linux, but there are special plugins what remove them and we are now talking about windows demo recording). Anyway, why on earth you stick with modern way (00:00) when you can create a classic clock with func_rotating entity? Yes, maybe it cannot work with 0.01 seconds but it wont have no problems at all.

Start using Shizuka's and Sadpuppy's timer. I think it's 100% correct. If I'm wrong, correct me :D

I didn't had in mind anything about reset button.

Let me explain what I have in mind:

Sprite created, now it should count seconds, but some object touched another object and counter stopped. Now when you press start button - counting continues (it was stopped on 0). Now you press stop button and counting stops.

I think mappers should try doing a new timer with 100% corect time or smth. :)

Originally posted by NumB

Ok. As we all know all maps have timer bugs, cuz func_train objects are a bit bugged.

I was thinking much about it and found 2 ways. Will start from more uber correct one but maybe impossible by mapping, but what the hell - lets try:

1. Using sprites. Create a sprite with specific framerate (with it you can also make seconds like 0.01). Anyway, sprite is created now use some entity to disable sprite (if possible), so all datas are setted to 0. Now when button is pressed find a way to activate the sprite (if possible), so all framerate is started. Now finish button - some way to deactivate sprite, so frame switching will be changed. Some information about framerate - it actually doesn't use frames - it uses hl time what is working under 32 byte system (good enough for 0.01 seconds).

2. This way is more classic and is possible and has no timer bugs (however it has bugs with linux, but there are special plugins what remove them and we are now talking about windows demo recording). Anyway, why on earth you stick with modern way (00:00) when you can create a classic clock with func_rotating entity? Yes, maybe it cannot work with 0.01 seconds but it wont have no problems at all.