SilentPatch

[mirh]

Doesn't tearing happens when there are too FPS than the maximum hz the screen have?

Those people who wants 100+ FPS while they have 60hz monitor....

 

I don't mind running SA at 30FPS as long as it doesn't get f*cked up with its physics and crashing at certain missions or cutscenes.

I just need to get used to it.

Just to debunk some myths: tearing is less noticeable as framerate increase and, in general as its deviation from refresh rate gets bigger (since the difference between frames that tries to be shown gets smaller)

100+ framerate is not useless on 60Hz screen. You don't exactly see it.. but I can assure I can feel it (and no I can exclude there was some kind of placebo effect)

Even if you don't have one of those fancy 144Hz, 1ms monitors there are still "standard" monitors better than others.. Next time you buy one I would suggest you to check ghosting tests (which are quite linked to overall LCD reaction times, imo)

 

[...]Divine Silent said[...]

 

Silent, if built-in frame limiter enable vsync too, could you explain how this was achieved when cap was 25FPS?

 

Edited December 21, 2014 by mirh

[Silent]

They used vsync + two time-based framelimiters. I removed one of them as it was useless and ended up capping the game at 25FPS whereas it should be 30FPS.

[Shooter Hex]

Try to use (0.248 version)enb's frame limiter and set the value to 60.0? It works fine for me.

 

Usage:

Open enblocal.ini,

EnableFPSLimit=true

FPSLimit=60.0

replace these two lines and save.

[mirh]

Try to use (0.248 version)enb's frame limiter and set the value to 60.0? It works fine for me.

 

Usage:

Open enblocal.ini,

EnableFPSLimit=true

FPSLimit=60.0

replace these two lines and save.

For the eleventh time: for a proper game experience you need to use 30FPS cap (i.e. in-game frame limiter + SilentPatch)

Everything else, 100, 90, 60, 32 is going to be (more or less) bugged.

[Blackbird88]

 

Try to use (0.248 version)enb's frame limiter and set the value to 60.0? It works fine for me.

 

Usage:

Open enblocal.ini,

EnableFPSLimit=true

FPSLimit=60.0

replace these two lines and save.

For the eleventh time: for a proper game experience you need to use 30FPS cap (i.e. in-game frame limiter + SilentPatch)

Everything else, 100, 90, 60, 32 is going to be (more or less) bugged.

 

Man you really need to chill out. He didn't even say it's bugfree. Also "proper game experience" sounds like PR buzzword

Edited December 24, 2014 by Blackbird88

[Silent]

He's right though, I think the same but I stopped expressing my annoyance

[nonamenoname]

There is a variable 0xB7CB5C - float, it's calculated in 0x5618D0 function every frame and 0xB7CB5C = elapced time from last frame/20

100fps = ~0.5

60fps = ~0.8

50fps = ~1.0

20fps = ~3.0

 

and some example how it work at 0x5262C1

float temp;if(*(float*)0xB7CB5C>=1.0) temp=*(float*)0xB7CB5C;else temp=1.0;v56=(v18-*(float*)(v2+188))/temp;v53=pow(*(float*)0xB7CB5C,0.8);

it's mean if this variable will be >1.0 (your fps will be smaller then 50) some calculations will be faster

with 20fps faster up to 3 times!

and why to pow this variable to 0.8?

this is a reason why some functions don't work with fps>50 and other faster with 20 fps

Edited December 24, 2014 by nonamenoname

[Silent]

But timestep actually makes things work properly... the higher the FPS is, the more often calculations are updated. So it's logical not to fix them but rather have them scale by some sort of delta time. And that's what timestep does.

 

It's just Rockstar using it wrongly in some places or not using it at all.

[nonamenoname]

As result fire extinguisher and flamethrower effects and swimming don't work with high fps

this variable used 1000 times in engine =\

and 20fps = some of cheating

Edited December 24, 2014 by nonamenoname

[Claude_Lib]

I guess the fact that PC version is originally locked at 25 fps came from PAL PS2 version which plays at lower framerate than NTSC. Who knows, maybe in-game physics works slightly different in NTSC and PAL PS2 builds, too.

[Blackbird88]

He's right though, I think the same but I stopped expressing my annoyance

 

He may be right if someone wants to use the 60 FPS knowing the consequences he shouldn't be so angry

Like I would understand if someone would so stupid to use something like 120 FPS, because "OMG I HAVE LE 120HZ moniter", but that isn't the case.

For some reason plenty of MTA Race servers also cap the game at 45 FPS. I wonder why.

 

Literally impossible

 

(Select 60 FPS quality obviously)

Edited December 24, 2014 by Blackbird88

[uncaged]

^ Oops, the broken physics is now... broken XD

[Blackbird88]

^ Oops, the broken physics is now... broken XD

You mean car physics? They are fine. The video looks sped up, but in-game it looks less silly.

Edited December 24, 2014 by Blackbird88

[uncaged]

No, I'm talking about infamous swimming at 60 FPS. I've heard so much complains about it so I've even taken Framelimiters' side. Now my world is ruined and I'm falling into the abyss...

[SilverRST]

 

 

Try to use (0.248 version)enb's frame limiter and set the value to 60.0? It works fine for me.

 

Usage:

Open enblocal.ini,

EnableFPSLimit=true

FPSLimit=60.0

replace these two lines and save.

For the eleventh time: for a proper game experience you need to use 30FPS cap (i.e. in-game frame limiter + SilentPatch)

Everything else, 100, 90, 60, 32 is going to be (more or less) bugged.

 

Man you really need to chill out. He didn't even say it's bugfree. Also "proper game experience" sounds like PR buzzword

 

"Cinematic frame rate" That excuse is getting more frequently used by those consoles developers these days.

 

RenderWare is lovely as to see how these older GTA games look but those limitations... Damn it!

[Silent]

RW handles high FPS properly. Proof? Animations.

[SilverRST]

But why does the physics gets f*cked up? And I keep reading flamethrower gets bugged at high FPS.

Can someone explain what happens exactly? Before I installed SilentPatch, I used Stream Ini Extreme to get 35FPS and never got something bugged.

Edited December 24, 2014 by SilverRST

[Silent]

But it's not RW. It's Rockstar's code.

[SilverRST]

Ah I see, my bad.

Edited December 24, 2014 by SilverRST

[savidge]

This may not be a bug, but why does the exhaust smoke stop whenever you travel at a high speed in III, VC and SA?

[bobbyprince]

This may not be a bug, but why does the exhaust smoke stop whenever you travel at a high speed in III, VC and SA?

Because it's dissolves in airflow fast enough? IRL I can notice pretty same behavior.

[savidge]

Because it's dissolves in airflow fast enough? IRL I can notice pretty same behavior.

Oh, I didn't know that. That's pretty embarrassing. Anyhow, thanks for clearing that up.

[uncredited]

Do you know the bug that makes the game add a value to the "mission attempted" stat each time you enter a gym, a driving school etc.? It may have already been fixed so I am sorry if I am bumping here.

[Zera]

Do you know the bug that makes the game add a value to the "mission attempted" stat each time you enter a gym, a driving school etc.? It may have already been fixed so I am sorry if I am bumping here.

That requires scm editing. All bugs related to stats do.

[bobbyprince]

Oh, I didn't know that. That's pretty embarrassing. Anyhow, thanks for clearing that up.

 

That was more like theory... Fumes density also depends on enviroment temperature and humidity, but it probably wasn't worth doing complicated algoritms for exhaust smoke density and volume calculations.

Edited January 9, 2015 by bobbyprince

[Blackbird88]

 

Do you know the bug that makes the game add a value to the "mission attempted" stat each time you enter a gym, a driving school etc.? It may have already been fixed so I am sorry if I am bumping here.

That requires scm editing. All bugs related to stats do.

 

 

Are you sure? This was fixed in GTAIII

• Shooting from M16 in 1st person mode now increments bullets fired stat properly (so you can't score Accuracy to be more than 100%)

[Silent]

This stat was hardcoded though. Mission attempts one is controlled by the SCM.

[TheFlareEntercounter]

 

^ Oops, the broken physics is now... broken XD

You mean car physics? They are fine. The video looks sped up, but in-game it looks less silly.

 

Turning the FPS limiter off makes the cars brake on their own when you release the accelerator.

[Silent]

True, I think something is wrong with friction.

[Blackbird88]

 

 

^ Oops, the broken physics is now... broken XD

You mean car physics? They are fine. The video looks sped up, but in-game it looks less silly.

 

Turning the FPS limiter off makes the cars brake on their own when you release the accelerator.

 

Not for me. Unless you mean anything over 60 FPS.

Edited December 26, 2014 by Blackbird88