General > Bug Reports

FPS Rule

(1/6) > >>

G[M]X:
Well, FPS rule does not have a bug, its just bad made.
Its meant to block people who are abusing the 23fps bug, not to punish legit people who got little freezes or lag spikes.
Im one of those guys who barely can finish a race without getting FPS rule'd.

I don't see a reason to keep this rule tbh, but my suggestion is to check twice someone's fps to make sure its not a unlucky timing issue and the driver is really abusing this glitch.

Queen|iPink:
You said that it meant to block people from abusing and then you say there's no reason to keep it so lol...?

There's this super low percentage of players facing this problem caused by low net/pc etc reasons.
IMO it's more important to keep it and avoid abusers instead of getting rid of this rule when 90% records on ax are almost impossible to beat nowadays anyways (because all races are raped hard enough, espec old ones, not talking about new) so basically you lose nothing, couple of points only

If so.. There would be more abusers than players who are facing this "low fps" problem.


--- Quote ---my suggestion is to check twice someone's fps to make sure its not a unlucky timing issue and the driver is really abusing this glitch.
--- End quote ---

It's possible only if real admins decide this one day, not autoadmin :D

G[M]X:

--- Quote ---It's possible only if real admins decide this one day, not autoadmin :D

--- End quote ---


--- Code: ---SetTimerEx("CheckFPS", 5000, false, "i", playerid);
public CheckFPS(playerid)
{
    if(GetPlayerFPS(playerid) <= 30) FPSAbuse[playerid]++, SetTimerEx("DoubleCheckFPS", 2500, false, "i", playerid);
...
}
public DoubleCheckFPS(playerid)
{
   if(GetPlayerFPS(playerid) <= 30)
  {
      if(FPSAbuse[playerid] > 0 ) BlockRecord(playerid);
      else FPSAbuse[playerid]=0;
...
}
--- End code ---

This will give a 2,5 sec to double check, unlucky timings will still exists but it will be harder to see.
2,5secs + 5sec from first timing = 7,5 secs is not enough to abuse.


@edit
[spoiler]

--- Quote ---You said that it meant to block people from abusing and then you say there's no reason to keep it so lol...?

There's this super low percentage of players facing this problem caused by low net/pc etc reasons.
IMO it's more important to keep it and avoid abusers instead of getting rid of this rule when 90% records on ax are almost impossible to beat nowadays anyways (because all races are raped hard enough, espec old ones, not talking about new) so basically you lose nothing, couple of points only

If so.. There would be more abusers than players who are facing this "low fps" problem.

--- End quote ---

1 - Low end PC
There is a lot of people who still use a low end pc, or just old one, or laptops, well, most of them aren't pros, letting them play with 30fps will not hurt the highscore system, plus giving a slight advantage on straight lanes will not change much since 1/10 of the races. maybe less, are long-snoopy-drags style.
And by the way, most people who still play samp are low end pc users who plays this game because their pcs can't run newer games.
@editn2: About pros abusing this, changing the handling will hurt them more than help them. FPSbug is only helpful in drag style races, and you barely can see races like this anymore.

2 - Network problems.
Here I am.
Most of my issues are due to little loss spikes, but it still not my fault.
And please don't say it doesnt matter because this rule is meant to punish people abusing 23fps bug, not people who are having network problems. If you want to punish us, just set the ping limit to 100 and have fun.
[/spoiler]

Terrorfist:
SA-MP pretty much disables everything hindering PC performance (motion blur is the one). But GTA SA is horribly optimized as shit even my Core 2 Quad system is puking to play SA at 1440x900 native res everything at max

[LSR]Jalicno:
Procesor cores (quad)have nothing with resulution but video card does cause game was made 2004.

Navigation

[0] Message Index

[#] Next page