Does 30 fps look too uncanny for a retro style game?
Moderator: Moderators
-
- Posts: 40
- Joined: Wed Jan 19, 2022 9:52 am
Does 30 fps look too uncanny for a retro style game?
In my WIP engine, I am doing a lot of heavy things, including handling 32 actors in a scene, depth sorting, keeping off-camera actors busy, pixel-perfect collision detection, 4 way scrolling, dynamic front-back priority for hiding behind overhead objects.
I have about half the tools and code finished. I am quite sure I will blow available single frame cycles, even with keeping things tight.
From experience, would results look too jarring or uncanny if I went to 30 fps? Are there other notable 30 fps games, other than TMNT, I could use to gauge?
I have about half the tools and code finished. I am quite sure I will blow available single frame cycles, even with keeping things tight.
From experience, would results look too jarring or uncanny if I went to 30 fps? Are there other notable 30 fps games, other than TMNT, I could use to gauge?
Re: Does 30 fps look too uncanny for a retro style game?
I would think the best answer is "it depends on how things move, you'd probably just have to try it and see".
My guess is that if things generally move slowly, then it would be fine. But if it's a fast-paced game where things are moving rapidly (multiple pixels every one of your double-frames) then it's going to start looking bad.
My guess is that if things generally move slowly, then it would be fine. But if it's a fast-paced game where things are moving rapidly (multiple pixels every one of your double-frames) then it's going to start looking bad.
My games: http://www.bitethechili.com
Re: Does 30 fps look too uncanny for a retro style game?
Is it possible for your program to become aware of dropped frames and throttle back dynamically? Then you could have a dynamic framerate that could even drop multiple frames at a time if necessary. Not sure I have ever seen this done on an NES. Everything would have to be coded such that it could advance N frames instead of always assuming it is advancing 1 frame, and I am sure that costs a lot of overhead to do something like that.
Re: Does 30 fps look too uncanny for a retro style game?
Wizards and Warriors 3 cheated, running the game at 30FPS but interpolating the player's coordinates and the camera at 60FPS.
Here come the fortune cookies! Here come the fortune cookies! They're wearing paper hats!
- rainwarrior
- Posts: 8734
- Joined: Sun Jan 22, 2012 12:03 pm
- Location: Canada
- Contact:
Re: Does 30 fps look too uncanny for a retro style game?
30fps was the most common framerate target through the whole 360/PS3 era. 60fps was an exception. (On earlier generations in the 3D era it was often even less.)spaceharrier wrote: ↑Wed Sep 21, 2022 1:30 pmAre there other notable 30 fps games, other than TMNT, I could use to gauge?
I think there are quite a few games on NES that operate at 30 or 20 fps, though I don't have a list offhand. Solar Jetman and Solstice are two I remember that haven't been mentioned.
It's quite easy to count frames via the NMI. Finding a way to update dynamically is harder. The easiest thing is just to skip rendering and do the simulation/physics twice, but that probably only buys back 25% of a frame at most. It's a lot easier on modern stuff where it's reasonable to multiply a floating point time delta by everything... though doing that results in less deterministic behaviour than a fixed timestep.
Re: Does 30 fps look too uncanny for a retro style game?
That cheat is great, I've used it in the past and I guess lots of games have used it without people noticing.
For example, you can do collision detection with half of the objects in odd frames and with the other half in even frames.
If you split your most CPU intensive tasks in half, it's like running the game at 30FPS but showing it at 60FPS.
The same concept can be applied with sprite animation, for example.
Re: Does 30 fps look too uncanny for a retro style game?
It's totally fine to run at 30fps as long as it's stable. So no "sometimes 60, occasional drops to 30" - if you can't do 60, have the fast frames sleep so they are 30fps.
-
- Posts: 1565
- Joined: Tue Feb 07, 2017 2:03 am
Re: Does 30 fps look too uncanny for a retro style game?
And the PS2 and the PS1 erarainwarrior wrote: ↑Wed Sep 21, 2022 5:22 pm 30fps was the most common framerate target through the whole 360/PS3 era. 60fps was an exception. (On earlier generations in the 3D era it was often even less.)
Re: Does 30 fps look too uncanny for a retro style game?
Aren't many games on the Switch, a very successful and current-gen console, also 30fps?
I don't think that 30fps games on 8 and 16-bit systems are particularly bad. If it's well made, fun, and the frame rate doesn't hurt the controls, I'd rather have a game running steadily at 30fps than constantly switching back and forth.
With limited hardware, something's gotta give... you're not gonna be able to make incredibly complex games with perfectly smooth 60Hz animation in a short period of development. Optimization takes time, and there are cases where even with the highest levels of optimization, the hardware is simply maxed out.
-
- Posts: 1565
- Joined: Tue Feb 07, 2017 2:03 am
Re: Does 30 fps look too uncanny for a retro style game?
star fox, stunt racer SFX ran at what 12~15fps and they sold millions.
Re: Does 30 fps look too uncanny for a retro style game?
They had a pretty good excuse for that though, which was plain to see. If a game isn't doing much out of the ordinary, or if it is but that isn't obvious to players, then a lower frame rate won't be as easily excusable.Oziphantom wrote: ↑Thu Sep 22, 2022 5:41 amstar fox, stunt racer SFX ran at what 12~15fps and they sold millions.
-
- Posts: 1565
- Joined: Tue Feb 07, 2017 2:03 am
Re: Does 30 fps look too uncanny for a retro style game?
if it has a solid reason then sure, if its just poor programming then no.
-
- Posts: 40
- Joined: Wed Jan 19, 2022 9:52 am
Re: Does 30 fps look too uncanny for a retro style game?
I really like the interpolation idea. It doesn't seem to cycle intensive to do so, spare some extra memory for storing a few deltas.
This is why I am standing on the backs of giants.
This is why I am standing on the backs of giants.
Re: Does 30 fps look too uncanny for a retro style game?
30 FPS games feel noticeably less smooth than 60 FPS games. They're still fine, and a stable framerate is worth a lot, but almost every game on the NES is 60 FPS and so it's definitely noticeable when you play one that runs slower. That's not necessarily a problem, and being able to do more at a lower framerate can be a good tradeoff, but I'd still aim for 60 if it's possible to do with what you have in mind.
- TmEE
- Posts: 960
- Joined: Wed Feb 13, 2008 9:10 am
- Location: Norway (50 and 60Hz compatible :P)
- Contact:
Re: Does 30 fps look too uncanny for a retro style game?
I'm not fond of 30fps for anything that scrolls, there are double image artifacts that come from it which make things look blurry when motion begins (it stems from eyes tracking motion and the doubled image blending in with new stuff, but I'm not fully sure about the mechanism), it doesn't look particularly smooth anymore. This also is a problem with 100/120Hz frame doubling CRT TVs that were popular in Europe, I managed to work in a "black frame insertion" method into the signal path on mine and that made games look fine again, at cost of dimmer image.
If half rate can be avoided it should be, at least for scrolling games. WIth 3D things it isn't as offensive though it is clearly visible when image is turning and in edges of the screen when moving forward as motion is biggest in there but center stays good. Modern variable refresh rate displays are able to fix this problem to a great degree.
If half rate can be avoided it should be, at least for scrolling games. WIth 3D things it isn't as offensive though it is clearly visible when image is turning and in edges of the screen when moving forward as motion is biggest in there but center stays good. Modern variable refresh rate displays are able to fix this problem to a great degree.