Author
Topic: Idea For Low FPS (Read 1994 times)

I think that for low fps should low fps waringmany people happen to have the 90 fps constantly but their moment something happens and fps drops rapidly below 30 and can not therefore enter the recordI thought to introduce to Low fps waringexampleMe falls below 30 fps and get LOW FPS WARING 1/3 and if we fall again get LOW FPS WARING 2/3if I get back in the same race and have LOW FPS WARING 3/3 That is then switched to my record is deleted due to low FPS

It should be working on /race mode only, not in /tt. Its possible to abuse then imo. You can retry tt race if uve got this warning but at least for me its more annoyin when it appears out of nowhere in /race mode. Admin wont reload it just because you didnt make top as your fps dropped till 30 for one second that was caused by bug or w.e else

lauu I see no reason why not to do it and in /tt modethe low fps waring would not last five seconds than at intervals of 1 second if we are below 30 fps or in tt below 40if we are more than 1 second so we get a low fps waring and if we fps 3-4 seconds so under 40-30 get low fps waring 3/3

I see no reason for that low fps function at all, i mean record disabling. Because as we know low fps gives speed adventage only on plane or boat races but 95% of races on the server is a car races, so what is the point?

MadMax and others proved that it is possible to abuse it in any race where acceleration is crucial. And, if you're getting random lag spikes, you're probably not competing for the record anyway, as that will indeed slow you down.

you did not understand what I told youthat low fps = high speed with the boatI thought that as soon as you make the fps drops below 30 FPS to get waring if we FPS stands below 30 then constantly make us the FPS Waring filled within 3-4 seconds if you know what I mean

actually, the system is indeed coded to forgive little lag spikes, but there will always be someone who lags more than that.the reason it doesn't warn you for that is because it is time, and not count based.

What karlis said is that the system doesn't annule your record when your fps go below 30 one time. It annuls your record when you are below 30 fps for X amount of time.

And I don't believe a warning should be necessary, if you have fps spikes, there's nothing you can do about it during the race, and if there is (for example closing a demanding program), you lose time doing it so the rec won't be good anyway.