[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/vr/ - Retro Games


View post   

File: 150 KB, 1280x720, maxresdefault.jpg [View same] [iqdb] [saucenao] [google]
10453598 No.10453598 [Reply] [Original]

When did 30FPS become the standard? Most of the SNES games ran at 60fps. Even the PS1 had mostly 60 fps titles.

>> No.10453605

>>10453598
>SNES
>PS1
Mostly 2D games

>> No.10453612

>>10453598
>PS1 had mostly 60 fps titles.
Nope

>> No.10453614

30 fps never was the standard

>> No.10453617

>>10453598
the sfc is not a benchmark for performance. and what do you mean became the standard? polygons happened. developers trying to capitalize on cinematic games neutered the industry prioritizing poly count over smooth play. now its the same thing, whatever bullshit they have to sell you on next.

>> No.10453618

>>10453614
ps2 era

>> No.10453621

Japs are unironically not good at programming and fuck up framerate related stuff to this day. It just took them a long time figuring out how to cap at 30 frames and tie all logic to it

>> No.10453620

>>10453598
>Even the PS1 had mostly 60 fps titles.
lolno

>> No.10453625

>>10453620
ps2 has more share of 60 fps titles than psx

>> No.10453626

You can do more with 30 fps. The real issue is when framerate isn't consistent

>> No.10453630

>>10453621
It’s way past time to stop giving FromSoft a pass for this sort of thing.

>> No.10453639

>>10453626
>You can do more with 30 fps.
What can you do at 30fps that you can't do at 60?

>> No.10453641

>>10453639
More complex graphics since you're targeting a lower framerate. It's a cheap and easy way to squeeze more flash out of lackluster hardware.

>> No.10453645

>>10453614
30fps was always the standard.
That's the frame rate of proper interlaced NTSC.
60Hz / 2 (even lines + odd lines)

That standard stems from analog times and was hard to recreate with early digital electronics. So old consoles struggled to handle 480i @ 30fps (also interlacing can look bad in games) and instead they cheated by only sending the same half of the lines at every pass which gives you 240p @ 60fps (this is also what causes "scanlines")

>> No.10453649

>>10453641
You can do that at 60fps too if the system is powerful enough. You said you can "do more" at 30. What can you do at 30 that is literally impossible at 60?

>> No.10453650

If you need your games to be in 60fps you're a permanent baby.

>> No.10453657

>>10453650
Why?

>> No.10453658

>>10453598
>Even the PS1 had mostly 60 fps titles.
It really didn't and those that were are usually 480i.
https://www.youtube.com/watch?v=hFUB5Xau59g

>> No.10453681

>>10453649
I guess literally nothing

>> No.10453705

>>10453598
>Even the PS1 had mostly 60 fps titles
LOL no the vast majority of games were 60fps until the move to 3D which resulted in a drop to 20-30fps.

>> No.10453715

>>10453645
>30fps was always the standard.
>That's the frame rate of proper interlaced NTSC.
That's using a fucked up definition of "frame rate" that predates video games. The temporal resolution is still 60Hz because the odd and even fields are not sampled at the same time (except in the case of telecined content with is always garbage and should never be watched). It should really be called 60 interlaced frames per second for consistency with modern terminology.

>> No.10453718

>>10453657
Framebabies throw their pacifiers out of the proverbial pram at anything less 60.

>> No.10453719

>>10453649
>You can do that at 60fps too if the system is powerful enough.
IF the system is powerful enough. IF.
>What can you do at 30 that is literally impossible at 60?
That depends on the hardware you're targeting. If you had an infinitely powerful system, then there would be nothing you wouldn't be able to do at 30 that you couldn't do at 60, 90, 120, etc.
Anyway, I'm not this anon: >>10453626

>> No.10453723

>>10453649
Stop being a stupid cunt. Basic arithmetic tells you that dividing a given throughput (in this case, the PlayStation's power) more frequently (in this case, higher framerates) results in less output per task. Unsurprisingly, this made 60fps Final Fantasy VII on the PlayStation impossible. Were you singing the praises of real time ray tracing in 1997 as well, fuckhead?

>> No.10453727

The shift from 60 to 30 happened when the shift from who was making the games changed from game centric developers to failed wannabe Hollywood directors like Kojima

>> No.10453734
File: 2.08 MB, 640x480, 1700748385364174.gif [View same] [iqdb] [saucenao] [google]
10453734

>>10453727
this anon gets it

>> No.10453739

>>10453598
Fwiw FF7 battles were capped to 15 fps

>> No.10453847

>>10453598
>When did 30FPS become the standard?
When consoles switched from tilemap graphics with a fixed 60Hz render period to framebuffer graphics with flexible rendering time.
>Even the PS1 had mostly 60 fps titles.
lmao, no.

>> No.10453848

>>10453727
correct.

>> No.10453903

>>10453598
Console performance + 30 being half v-sync of 60Hz, which most TVs are. That's more relevant to the PS2/3 era though and panels.

>> No.10453909

>>10453718
True, wouldn't go under 60 FPS for anything modern. Preferably 120+.

>> No.10454212

>>10453650
Cope. Stop producing cheap Chinese garbage so your games look at least half presentable

>> No.10454258

>>10453598
>Most of the SNES games ran at 60fps
Source?

>> No.10454261

>>10454258
My fps counter on the emulator

>> No.10454289

Refresh rate =/= framerate
60Hz means you can have up to 60fps being shown on screen. 60fps on a 30Hz screen will only show 30fps. The framerate is also dictated by the game itself, not an emulator fps counter.

>> No.10454381

>>10454289
yaah but if it isn't a 1:1 or dividable value it will teaaaaar

>> No.10454383

>>10453650
this. most "normal/average" people aren't going to notice anything past 60fps (and if you actually do you're unironically autistic and probably get bothered by florescent lights) while others aren't going to notice a difference between 30 & 60 unless it's an actual side by side comparison.

>> No.10454428

>>10453612
/thread

>> No.10454435

>>10454383
>t. someone who has never played a game at 120fps with a 120hz monitor

>> No.10454461
File: 621 KB, 1280x1773, 1432185536001.jpg [View same] [iqdb] [saucenao] [google]
10454461

>> No.10454487

>>10454383
They definitely would if they would try.

>> No.10455079

>>10453727
so it should've been 24fps then?

>> No.10455171

>>10453598
>emulators run games at 60 fps i don't understand why real hardware doesn't
you never used real hardware don't you.
snes/megadrive/ps1
>all games ran at 24 fps NTSC
>PAL games ran at 29.5 fps
>only exception would be DOA for ps1 that was the only game in playstation library that ran at 60 fps on either version (DOA2 for xbox and ps2 ran at 24 fps)
next time inform yourself,even arcade games ran at 24 fps,herz doesn't equal fps and has never been related to frames (we had 110 herz TV and monitors since 2000 yet they never related to frames)
this is why is said most emulators are poorly done

>> No.10455224

>>10455171
>>all games ran at 24 fps NTSC
>>PAL games ran at 29.5 fps

>> No.10455242
File: 58 KB, 632x932, f72d96f47f56f4b167d04de1d76df078d3a789bb881ccc118ed84b14fbf79354.jpg [View same] [iqdb] [saucenao] [google]
10455242

>>10453650
When did this fucking board, built upon the golden era of games that was rife with technological advancement by leaps and bounds every year until the turn of the millenium, now parading its retardation by speaking against improvement?
If a company failed to deliver the framerate it promised in an arcade port, it was eaten alive.

>> No.10456035

No one cared about the fps cap until 10 years ago. The actual issue was slowdown/lag.

>> No.10456041

>>10453598
VN fans be like
>1/10 fps is more my speed

>> No.10456069

>>10453598
It wasn't an issue with CRT's
It became a problem with LCD's due to motion blurring

>> No.10456109

>>10453612
Game Sack's newest video was about PS1 titles that were solid 60FPS and it was about 25-30. Some looked pretty good!

>> No.10456112

>>10453727
Retard. MGS2 was 60fps

>> No.10456113

>>10453658
Ahh shit, I should have read the thread before I commented. Exact video I was talking about.

>> No.10456116

>>10456109
Game sack… is actually good. Have you noticed that classic game reviews has been trying to release the same type of compilation videos as gamesack. In hopes of hitting the algorithm jackpot, but nobody is taking the bait, kek.

>> No.10456243
File: 322 KB, 755x711, 1000083759.jpg [View same] [iqdb] [saucenao] [google]
10456243

I always had lower end or older graphics cards so I don't mind 30fps at all

I usually play games below 30fps to this day lol

>> No.10456250

>>10456116
>classic game reviews

he sucks and you know what sucks even more? his sad attempt at making a comic book

he was making pretty nice patreon money from dummies

>> No.10456342

>>10456116
Love me some Game Sack. Miss Dave tho, it was better when they played off eachother. Joe's been doing a decent solo job tho.

Never watched Classic Game Reviews.

>> No.10456414

>>10453681
>>10453649
The laws of physics actually mean that even after an infinite amount of years of technological progress, there will be things that are not possible at 60fps. Energy transfers can only be so efficient, atoms cannot be infinitely small, and e=mc2

>> No.10456457

>>10456342
will he ever fix his teeth?

>> No.10456618 [DELETED] 

>>10454461
is that rob schneider?

>> No.10456626

>>10456243
30fps was pretty normal for pc gaming

the whole 60fps autism is a relatively recent thing that was aggressively pushed by youtubers like TotalBiscuit

>> No.10456636

>>10453723
What's wrong with real time ray tracing?

>> No.10456665

>>10455242
you know the answer. It rhymes with groomer

>> No.10456756

>>10455171
Tobal No.1 ran 60fps

>> No.10456789

>>10455242
>If a company failed to deliver the framerate it promised in an arcade port, it was eaten alive
What are you talking about, barely any arcade port lived up to arcade original in the SNES era, it was pretty much impossible for it to. Only later ports of old games managed to capture the arcade experience

>> No.10456810

>>10456636
>1997
>>10456789
Another RGBfag pretending console gaming in the 90's was all about bringing the arcade into the homes (still cannot explain why the best-selling titles were all console-exclusive kek)

>> No.10456882

>>10456109
>7,918 games
>30ish 3D ones are 60fps

>> No.10456883
File: 78 KB, 944x678, 1698741572030677.jpg [View same] [iqdb] [saucenao] [google]
10456883

>>10456626

>> No.10456886

>>10455171
Complete bullshit. No games ran at 24fps because it's not an integer divisor of 60fps. 2D games mostly ran at 60fps (with slowdown common on Nintendo consoles because they always cheap out on the hardware). 3D games mostly ran at 30fps or 20fps, with 60fps only rarely. 15fps/12fps/10fps wasn't unheard of. Arcade games generally had higher frame rates.

Divide all these numbers by 1.2 for PAL (and note that arcade games don't use PAL/NTSC).

>> No.10456901
File: 34 KB, 1107x482, 2023-11-28-135051_1276x1048_scrot.png [View same] [iqdb] [saucenao] [google]
10456901

>>10456883
sorry zoomer, but ass cancer man and his Framerate Police was instrumental in pushing it

>> No.10456907
File: 41 KB, 742x357, Untitled.png [View same] [iqdb] [saucenao] [google]
10456907

>>10456901
>zoomer
I guarantee I'm older than you retard

60fps was always the standard, everyone aimed for 60hz because most pc crts were 60 or 75hz monitors, it wasnt until the shitty ps3/360 era when pc was no long the primary platform that 30fps gained ground so of course that's why it became a topic at that time you absolute mong

>> No.10456920

>>10456907
lmao no
frame rate and refresh rate are different things, zoom zoom.

>> No.10456930

>>10453598
When framebuffered graphics became standard, so when the IBM PC started getting mainstream vidya support.

>> No.10456934

>>10456907
Developers aimed for factors of 60 (not limited to 60 itself) to avoid improper framepacing. It's less that developers aimed for 60 HERTZ specifically since that's the inevitable hardware the game was going to be played on (unless you're a sorry PALnigger like myself), but they did have to target a framerate 60 was divisible by.

>> No.10456941
File: 62 KB, 632x1034, file.png [View same] [iqdb] [saucenao] [google]
10456941

>>10456907
>60fps was always the standard,
Not on PC, on console. PC had the appeal of running older games smoother but new releases always choked. 7th gen brain damaged PC gamers into believing 120fps at max settings 1080p was the norm. Now they're still running at 1080p 15 years later.

>> No.10456953

>>10456934
>(unless you're a sorry PALnigger like myself),
NTSC/PAL didn't matter at all for pc gaming.

>> No.10456971

>>10453641
>More complex graphics since you're targeting a lower framerate.
I can't think of a single practical situation where this is actually meaningful. You're increasing the polygon count but ensuring you will never have smooth animations. At best this gives you good screenshots to bait people browsing through a gaming magazine.

30 FPS is largely just a red flag that the developers either didn't have enough time to or didn't care enough to optimize the game.

>> No.10456975

>>10456934
>>10456941
Look at any old PC magazines and the gold standard test was 60 fps.

>> No.10456983

>>10456975
>Look at any old
Prove it. Show a new release.

>> No.10456986

>>10456975
Maybe, but the latest games always ran like shit. Don't even get me started on the ports, God PC gamers have it so good with ports these days

>> No.10457062

>>10456983
He probably means benchmark tests using the latest high end 3D accelerator cards. Most users weren’t getting that experience.

>> No.10457091

>>10456953
Then explain why Doom (a pinnacle of PC gaming) targeted 35FPS.

>> No.10457226

>>10456907
>most pc crts were 60 or 75hz monitors
In the DOS era 70Hz was standard. Doom runs at 35fps because that's 70 divided by 2.

>> No.10457236

>>10457091
That's neither NTSC nor PAL.

>> No.10457491

>>10456971
You're moving the goalposts, bud. More complex graphics is a common reason for 30 instead of 60. Simple as that.

>> No.10457527

>>10456971
a lower framerate doesn't just give you headroom for better graphics, but also larger levels, more enemies on screen, physics, etc. The games themselves can become conceptually more ambitious at a lower framerate

>> No.10457553

>>10455171
You got that backwards you retarded nigger.
And it was fields per second, not frames per second, so it was equivalent of 60FPS, not 30FPS.

>> No.10457564

>ITT: Tech illiterate /v/ tourists
It's not rocket science, my dudes. Come on now.

>> No.10457598

>>10453598
>snes
At that era no one talked about frame rate.
No one. This is a revisionist discussion that is irrelevant. There was no standard.

>> No.10457624

>>10457564
The board is so fucking tech inept it is unbelievable. Considering the board topic everyone should be at minimum in their late 20s or early 30s, which means they were front and center during the giant boom of home and portable technology, but yet 95% of the posts read like a grandmother in 2000 trying to access her e-mail.

>> No.10457627

Most of these games couldn't maintain the 60 fps to save their life.

>> No.10458771

>>10456457
Ehhh I don't really care and I doubt he's out chasing women lol

>> No.10458828

ITT: Absolutely wrong answers.

OPs questions is wrong and gay too.

>> No.10458926

>>10453715
it's fucked up but it's factual.
>called 60 interlaced frames per second
not how it worked. takes two frames of odd/even lines to make 1 frame. this is how you end up with 30fps.

>> No.10458975

>>10453847
You really had to go out of your way to make a 16 bit game run at 30 fps, you required extra logic to wait for an extra frame and do more calculations, it really had to be severe as it needed more work than just running at 60 fps. Streets of Rage 1 made the choice for the handful of times when you have a huge number of enemies on screen.

>>10457527
I think also because are moving into the screen so its less noticable at first than a sidescroller.

>> No.10460629

>>10453598
>Most of the SNES games ran at 60fps.
[citation needed]
>>10458975
>You really had to go out of your way to make a 16 bit game run at 30 fps
SNES games frequently struggled to try to keep up at 60 FPS.

>> No.10462216

>>10460629
If you're talking about slowdown
it was common on all 4th gen consoles

>> No.10462253

>>10453598
The advent of 3D graphics made it harder to hit

>> No.10462316

>>10453598
They learned early on consumers don't care.

>> No.10462363

>>10462216
Wrong, it was used for stylistic purposes occasionally on the other 16-bit hardwares, but performance problems were largely confined to the SNES, with it's severe relative lack of CPU power really holding it back.

>> No.10462370

>>10462363
Are you one of the dumb cunts that thinks the MegaDrive didn't have slowdown?

>> No.10462391

>>10453621
>Japs are unironically not good at programming
lol

>> No.10462434

>>10462316
really why should we?