[ 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

Search:


View post   

>> No.6532286 [View]
File: 44 KB, 609x308, 98259252768.jpg [View same] [iqdb] [saucenao] [google]
6532286

>>6531216
>the PS1 spending polygons mitigating texture warping managed to look more detailed than N64 games which did not have this concession to make. The N64 clearly did not have the polygon crunching power the PS1 did
Actually the PS1 has a fairly similar "visible" polygon count to the N64, if not actually somewhat lower. A good example is Rayman 2. Because the PS1 version has to tessellate so many polygons on the landscapes (which are still cut-down in detail from the N64 version) in order to prevent insane texture warping, they had to cut polygons from the character models to compensate (see pic). And Rayman 2 wasn't a bad port. Unlike MM64 which is a straight-port of the PS1 engine to N64 (even the fucking tessellation is still there despite not being needed!), Rayman 2 on PS1 had its own dedicated engine created just for the console.

And don't give me that "but what about those high-poly FF8 summon models". That's just called frontloading the polygon budget into one part of the picture, with bare backgrounds. N64 has its own equivalent with Neon Genesis Evangelion which also has high-poly character models (perhaps even more polygons than any of the FF8 summons) and the bare backgrounds.

What PS1 often has the advantage in is higher resolution textures, but not always. Later N64 games like Conker surpass PS1 there.

>z-buffer and texture filtering were too intensive and wasted too many system resources
Texture filtering is basically "free" on N64. Well, to be specific, bilinear filtering is completely free. Trilinear filtering is not free, but it works out to be free in practice. Because the N64 can trilinear faster than it can z-buffer, with z-buffer enabled (which was almost always) the console can do trilinear in the time it takes for memory to respond to the z-buffer stuff.

>> No.6495775 [View]
File: 44 KB, 609x308, 98259252768.jpg [View same] [iqdb] [saucenao] [google]
6495775

>>6495762

>> No.4805879 [View]
File: 51 KB, 609x308, 98259252768.jpg [View same] [iqdb] [saucenao] [google]
4805879

>>4798976
you know you are objectively wrong about this right

>> No.4576006 [View]
File: 51 KB, 609x308, 98259252768.jpg [View same] [iqdb] [saucenao] [google]
4576006

>>4575998

>> No.3600254 [View]
File: 44 KB, 609x308, 98259252721.jpg [View same] [iqdb] [saucenao] [google]
3600254

>>3600252

>> No.3552990 [View]
File: 44 KB, 609x308, 98259252721.jpg [View same] [iqdb] [saucenao] [google]
3552990

>>3546756
>The Nintendo blurry low fps made me feel sick even in 1997

When the N64 was released the vast majority of PC gamers ran Quake in 1996 at 320x200 at 20 FPS because they couldn't afford Pentiums faster than 100mhz. It's stupid to say "durrr hurrr in 1997 PC graphics was better" obviously technically improved and became more affordable the following year.

Pro tip: When Goldeneye was released, PC's best looking FPS was still Quake 1.

>>3547648
>N64 had a lower polycount

Pic fucking related.

>>3552262
>The N64s low res is a fatal flaw imo

Most PS1 games are exactly the same resolution as most N64 games - 320x240.

>> No.3432725 [View]
File: 44 KB, 609x308, 98259252721.jpg [View same] [iqdb] [saucenao] [google]
3432725

As long as you avoid the PS1 version you should be alright

>> No.3312821 [View]
File: 44 KB, 609x308, 98259252721.jpg [View same] [iqdb] [saucenao] [google]
3312821

>>3311338
>Just curious, what's wrong with it?

Everything

>> No.3125889 [View]
File: 44 KB, 609x308, 98259252515.jpg [View same] [iqdb] [saucenao] [google]
3125889

N64 was a piece of shit.

But not relatively speaking.

>> No.3093147 [View]
File: 44 KB, 609x308, 98259252515.jpg [View same] [iqdb] [saucenao] [google]
3093147

ps1 version is typical butchered port

Navigation
View posts[+24][+48][+96]