[Kyance]

Quote:

Originally Posted by Threshold I don't see what's so difficult. Start the timer when they enter a vehicle, kill the timer when they leave it. Per player timers with this logic will make the most efficient option. pawn Код: forward SpeedometerUpdate(playerid); public SpeedometerUpdate(playerid) {     if(IsPlayerInAnyVehicle(playerid) && IsPlayerConnected(playerid))     {         new vID = GetPlayerVehicleID(playerid), string[142], string2[3], Float:rotation, Float:vhealth;         GetVehicleZAngle(vID, rotation);         GetVehicleHealth(vID, vhealth);         new direction = floatround(rotation, floatround_round);         while(direction > 360) direction -= 360;         while(direction < 0) direction += 360;         switch(direction)         {             case 0 .. 22, 338 .. 360: string2 = "N";             case 23 .. 67: string2 = "NW";             case 68 .. 112: string2 = "W";             case 113 .. 157: string2 = "SW";             case 158 .. 202: string2 = "S";             case 203 .. 247: string2 = "SE";             case 248 .. 292: string2 = "E";             case 293 .. 337: string2 = "NE";         }         format(string, sizeof(string), "~w~VEHICLE: ~y~%s~n~~w~SPEED: ~y~%d KM/H~n~~w~LOCATION: ~y~%s~n~~w~DIRECTION: ~y~%s~n~~w~HEALTH: ~y~%0.0f%s", VehicleNames[GetVehicleModel(vID) - 400], GetPlayerSpeed(playerid), GetPlayerArea(playerid), string2, vhealth, "%%");         TextDrawSetString(VehicleInfo[playerid], string);         TextDrawShowForPlayer(playerid, VehicleInfo[playerid]);         string = "\0";     }     else     {         KillTimer(VehicleTimer[playerid]);         TextDrawHideForPlayer(playerid, VehicleInfo[playerid]);         TextDrawHideForPlayer(playerid, VehicleBox[playerid]);     }     return 1; } public OnPlayerStateChange(playerid, newstate, oldstate) {     if(newstate == PLAYER_STATE_DRIVER || newstate == PLAYER_STATE_PASSENGER)         VehicleTimer[playerid] = SetTimerEx("SpeedometerUpdate", 1000, true, "i", playerid);     if(newstate == PLAYER_STATE_ONFOOT && (oldstate == PLAYER_STATE_PASSENGER || oldstate == PLAYER_STATE_DRIVER))         KillTimer(VehicleTimer[playerid]);     return 1; }

Quote:

Originally Posted by ****** I mean that if you use multiple timers, there is a loop over them somwhere internally in the server. If you use one timer, the loop is in your code. Either way - there is a loop to call the same chunk of code (the main loop body) multiple times. People seem to think that moving the loop in to your code is a good thing because the server (which is written in C++ BTW, not PAWN) is somehow bad at loops and anyone can do better in 3 seconds of PAWN. WHY people think this, I don't know!

Alright, thanks!

Quote:

Originally Posted by Bakr If you have only one timer (execution time is obviously exaggerated): Код: Player sync Timer called (exec time = 5 seconds) Timer ends > players go without sync for 5 seconds Player sync If you have a single big timer you may experience lag because while it is executing the players cannot sync. However, if you have multiple smaller ones, it chops it up to where players can sync between calls. Код: Player sync Small Timer called (exec time = 1 sec) Small Timer ends > players go without sync for 1 second Player sync Small Timer2 called (exec time = 1 sec) Small Timer2 ends > players go without sync for 1 second Player sync ... This is because we only have a single thread to work with (which I use to look at as a disadvantage).

Thanks, that taught me a lot!