Video

Like!

3:53 Useless fact: Sega Saturn cannot render tris, it renders quads instead since Sega considered better at the time plus Saturn was mainly made for 2D games and the whole 3D high-res 60fps thing was thrown in after they found out that Sony is making the PlayStation.

I've recently become fascinated with early 3D technology. This video was so fun! ^^

You forgot to explain how to make the PS1 styled games look jittery

is there a name for this technique? I would love a more indept tutorial on how this approach works and how to apply it to different models and model shapes!

Always wanted a full sonic game in this style

it's always interesting how people explain this

You would need to use arithmetic and do the wobbly calculations of vertexes and vertices in the 3D environment. It is not easy to pull off I think, but if someone manages to find the code for that exact calculation, it might be possible.

HEY, WHAT IF...? 😁😅 • SEGA PlayStation (1990) • SEGA PlayStation 2 (1998) • SEGA PlayStation 3 (2006) • SEGA PlayStation 4 (2014) • SEGA PlayStation 5 (2022)

why do you say characters like that

Please take this video with a massive grain of salt, as it mostly regurgitates info from Wikipedia and other retro game CZcams channels that they themselves mostly regurgitate it from Wikipedia. The whole N64 texture size thing is mostly a myth. Proof is several N64 games that have motion blur framebuffer effects. The way they do it is that they load chunks of the two framebuffers into the texture cache and blend them there before storing the result into the framebuffer. It seems like the N64 can actually handle any size up to 1024 pixels horizontally or vertically if it fits in the texture cache. I believe you can actually get up to 1024x1024 textures on the N64 by loading them 4K chunk by 4K chunk. However you also want to subdivide it into multiple long horizontal rectangles for each texture load for rendering efficiency. If you want accurate N64 style graphics, I'd suggest you Saauren and Kaze Emanuar's videos as resources for documentation.

Could you do something like this for like wii sports style art?

I love the bit with the lil scales dropping your models onto them with physics, great vid thank u

Here's before watching the full video to see if it was rendered obsolete by Kaze Emanuar's recent Mario 64 modding work.

would this work tutorial with something leaning more twoards the graphics of the original DS?

Great video! Just an English tip, the "ch" in "character" is pronounced like a "k". I can see why you mispronounce it because English makes no sense phonetically, but it sounds very strange to us native speakers =P

That's one way to make me feel old 👍

The ps1 polycount is wild... Becouse it could output actualy a lot more than you would guess. But they were such shitty poligons that every actual 3d game on ps1 used some form of tesselation so the textures dint became a mess. Funny is that there were some isometric ps1 games that becouse of the lack of perspective had amazing detailed scenes, wild arms 2 comes to mind

youre naturally good at this arent you

gogged beyond human comprehension

0:13 same

CDs have a 700mb capacity and DVDs 4.7GB with a few exceptions being bigger in some cases.

Can you make a Rom Hack of this on the PlayStation and Sega Saturn?

We all been here buddy. Hope you have a well rest and take ur time.

Can I just say I think the PlayStation one aged way better than the Nintendo 64 just because of how it draws textures it doesn’t it uses linear filtering and I think that single fact just makes everything look better than on the Nintendo 64 because it’s moved everything out making everything look bad

That is vewy cool. I have friend whos also in 3d animation, such an interesting art

one of the reasons it's hard to get a solid figure on polygon count limits for the consoles is because fill rate and overdraw were generally more limiting than raw triangle count

one thing to note about N64AA, its not true anti aliusing, its more like a soft blur.

Just a couple of corrections: 1- The N64 also does use dithering when outputting images to the screen. It has a higher color depth (21-bits I believe) than PS1's (15-bits). 2- The N64's largest texture can be 90 x 90, but it only allows a very low depth as a tradeoff. I don't remember all the details (you can look up at the N64 Homebrew scene if you want to learn in depth), but this is how I memorized for my 3D artworks and projects: - 32x32 = Full color depth, unnecessary because it devours texture cache space - 48x48 (or 32x64/64x32) = High enough color depth, for detailing - 64x64 = Low color depth, most common depth (see next paragraph) - 90x90 = Very low color depth Color depth and resolution aren't necessarily locked with each other, but rather neither can be exceed if you use any of the listed samples I mentioned. ALSO the N64 also supports greyscale textures, which occupy half the space (if I'm not wrong) for the same amount of colors if you were to include hue on them. That's where you'll want to use vertex colors even more (Link's clothing in both OoT & MM is the most omnipresent example I can think of). PS: TOOLS FOR TEXTURES: Both GraphicsGale and Paint.net can lower the color depth of images. Pro Motion NG allows you to edit a color palette (up to 256 colors, you can also manually allow a max number of colors). But I only use them for doing the fine-tuning I just described on each program - I do the main job on Krita (I know, not the best option, but it's good enough and free).

I luv the 90s!

Now id love to see sum games made this way

Me saying yes to everything then getting hit with the, "me neither!" Haha yeah, man. Totally, we young people gotta stick together hah yes hahaha

dude holy fuck thank you!

Wow thank you for making this video!

DUUDE! thank you so much for all this information in one video really pure gold here

they dont mention dreamcast, because at that point we get to high quality models

Thanks for this. Like for real, you helped me so much and im sure other feel the same.

Colour depth differed between the two consoles, with PS1 having a lower depth than N64. Hence the dithering, which, thanks to NTSC artifacting in CRT displays, could result in a higher perceived colour depth and overall smoothness in presentation. PS1’s instability was caused by not really handling floating point numbers, like at all? You can actually see similar results in modern game engines by looking at objects rendered at great distances from the local origin of the scene (the middle of the game’s current map space, or coordinates 0,0,0). If you want an easy example of this, load up the original 2011 release of Skyrim and head to the southeast corner of the city of Whiterun, on the road between the farmsteads and Honningbrew meadery, then look to the west at the mountains on the edge of the world space. If you slowly pan the camera from side to side, you should see the snow caps on the mountain where it meets with the rocks there “warble” a little bit. This is because that location is incredibly far from the local origin of your current cell, so when the engine tries to convert the polygons’ XYZ coordinates to a vector (a value between 0 and 1), each frame gets vastly different and inaccurate approximations due to decimal rounding errors.

Tú acento me dice que hablas español

Is pronounced karacter

I like 3K

This is soo beautiful it gives me some 80s vibes ❤

Great and entertaining tutorial, thank you

Hi how did u add the halftone effects on the Blender? Look so good tq fr the video

3:50 ese es el modelo de sonic r, el de sonic jam esta mas pulido y limpio

orgullo colombiano

has it been 2 weeks....

really cool! howd you do the old tv effect with the lines?

Another thing about Crash Bandicoot's graphics are that the actual model for Crash is all vertex Shading, This allows him to be animated more fluidly with a higher polygon count by using the PS1's untextured polygon mode.

Great video, thanks for sharing the knowledge!