Switch port is terrible with FPS below 30 (handheld)

[zack0niel]

The handheld mode on the switch runs very poorly falling below 30 often. The turning and looking is choppy as well. Why not simply reduce the resolution? It run great on the gpd win 2.Is this the final state of the game or will it be patched? I have it on pc but I wanted to support the switch version however this is just a very bad port for a twitch shooter that requires speed and precision.

[BESTER ITA]

The Maximum FPS limit for ION Fury PC Version is 240 FPS.

[kakiss4]

Ursprünglich geschrieben von zack0niel:

The handheld mode on the switch runs very poorly falling below 30 often. The turning and looking is choppy as well. Why not simply reduce the resolution? It run great on the gpd win 2.Is this the final state of the game or will it be patched? I have it on pc but I wanted to support the switch version however this is just a very bad port for a twitch shooter that requires speed and precision.

On Digital Foundry they said, that there is a Patch coming, making the Game smoother.
It seems like it is actually no FPS-Drop, rather than some strange behaviuor of the enginge.

I can recommend this Video, they really put much Work into the Ports, even starting with the Switch.

[Zaxx]

Ursprünglich geschrieben von Jinxs ITA:

The Maximum FPS limit for ION Fury PC Version is 240 FPS.

The only reason why you think that is because the devs were stupid enough to remove the unlimited fps option from the in-game options. There is a console command for it though, it's "r_maxfps 0".

The thing is they are afraid that PC gamers are so incompetent that they would fry their CPUs / GPUs with the thousands of fps the game can display sometimes even though it was proven basically 15 years ago that such a thing doesn't really happen and even when it does because of faulty hardware (for example when a ventilator dies) modern hardware has failsafes in place.

Also: an unlimited (=erratic) framerate makes the game's performance issues worse, you'll get more tearing and framepacing / timer related weirdness.

[Stiefn]

There is an uncapped option called NONE.
It's the first entry in the fps limit sub menu.

[Zaxx]

Ursprünglich geschrieben von Stiefn:

There is an uncapped option called NONE.
It's the first entry in the fps limit sub menu.

I stand corrected then, the last time I played "none" didn't exist... though I got so used to just setting my limit with r_maxfps that maybe I haven't even noticed it (my preferred option is not among the ones offered so I'm ♥♥♥♥♥♥ either way sadly).

[Stiefn]

Now I'm curious. What's your preferred setting?
Hard to imagine that there is a desirable frame target, which isn't covered by the presets in combination with the +-(0...10) fps offset.

[Zaxx]

Ursprünglich geschrieben von Stiefn:

Now I'm curious. What's your preferred setting?
Hard to imagine that there is a desirable frame target, which isn't covered by the presets in combination with the +-(0...10) fps offset.

I like to go higher than the refresh rate to reduce input lag the furthest so I usually just put in a limit that's generally very high and it's just a number I don't want the game to exceed rather than a proper fps limit. So for example in GZDoom I use 432 because that's three time my refresh rate so it feels good as a limit but a lots of time the game won't even run that fast, it's just there because I don't need more frames.

For IF things are different though (an erratic framerate makes tearing and pacing terrible) so I just set 288 (double the refresh rate) and the game will give me that most of the time.

Overall I just think that giving set values in the options is just a terrible solution if there is no engine reason for it because you don't really know what the user wants to do and you're sure as ♥♥♥♥ not future proofing (there are 360 and 480 hz monitors out there now). You know, they have this terrible "we give you a few options and then there's fps offset" so you don't have many options while half the players won't even know what fps offset means, why can't I just type in a number and be done with it instead of having two ineffective options for the same thing?

Edit: Another niche thing: you can actually overclock your monitor so a lot of different refresh rates are possible. For example back in the day when I had a 60 hz monitor I regularly ran it at 66 hz because that was the highest it could give me before messing with the image quality.

[Stiefn]

Ursprünglich geschrieben von Zaxx:

For IF things are different though (an erratic framerate makes tearing and pacing terrible) so I just set 288 (double the refresh rate) and the game will give me that most of the time.

Fast Sync/Enhanced Sync does the same and gets also rid of tearing.
But generally yes, a number input system would be preferable compared to presets.

[Zaxx]

Ursprünglich geschrieben von Stiefn:

Ursprünglich geschrieben von Zaxx:

For IF things are different though (an erratic framerate makes tearing and pacing terrible) so I just set 288 (double the refresh rate) and the game will give me that most of the time.

Fast Sync/Enhanced Sync does the same and gets also rid of tearing.
But generally yes, a number input system would be preferable compared to presets.

Fast Sync never worked for me on this game (like really: the option does nothing, fast sync doesn't work at all with IF) and I highly doubt that I'd get the same result even if it did. The game has a tendecy to show 1000 fps in one scene and then drop to 200 immediately after so fast sync would go crazy here.

[DR. Punishment]

the fact this game struggles to run 60FPS shows the switch hardware just struggles to run games at 60FPS I still want a switch myself its a great system but ya the hardware is not great for this game I mean the base PS4 and base XBOX are only 1080p but 60FPS

[Lyle]

I dont really mind the 30 stable frames on Switch, but if I could get stable 60 with lowered resolution Id prefer that. The sharp edges along with the lowres textures look odd to me anyway.

[mblackwell]

On PC you can type:

r_maxfps 123

in the console to set an arbitrary refresh value (where 123 is the refresh you want)