Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I've been mostly working on the internal systems lately for my #Dreamcast engine. The PC port gave me the debugging tools I needed to improve complex systems like the memory manager. • Audio is now working on the Dreamcast version • The renderer runs 20% faster on the Dreamcast...

294,839 Aufrufe • vor 1 Jahr •via X (Twitter)

10 Kommentare

Profilbild von Zsewq The Wolf
Zsewq The Wolfvor 1 Jahr

I like to ask but once it’s all done the engine can be used to make other kind of 3d games right? If so then Dreamcast is going to get new homebrew games for sure.

Profilbild von A Flock of Meese
A Flock of Meesevor 1 Jahr

This engine is made just for block games, so it can only be used for that. If the game is successful after release, I'll consider developing a plugin API.

Profilbild von Luna 🦊🇩🇰 (@lunafoxgirlvt.foxgirls.gay)
Luna 🦊🇩🇰 (@lunafoxgirlvt.foxgirls.gay)vor 1 Jahr

I see that the hotbar is being rendered behind the transparency drawlist. Would be drawing the UI in a secondary pass be too demanding? I know the PVR implementation in KallistOS needs a lot of work though.

Profilbild von A Flock of Meese
A Flock of Meesevor 1 Jahr

I could just draw entire UI in the transparency draw list. It's probably cheap enough to render.

Profilbild von 💜🎃 Mr. Dawn 🎃💜
💜🎃 Mr. Dawn 🎃💜vor 1 Jahr

What are you doing for shadows/lighting that gives it this blue glow aura?

Profilbild von A Flock of Meese
A Flock of Meesevor 1 Jahr

Fog

Profilbild von started
startedvor 1 Jahr

oh neat, anamorphic widescreen too?

Profilbild von A Flock of Meese
A Flock of Meesevor 1 Jahr

Yes. If I could find a widescreen VGA capture card, I would showcase anamorphic widescreen.

Profilbild von Cereal
Cerealvor 1 Jahr

Genuinely curious are you using something like KallistOS for this or something else?

Profilbild von A Flock of Meese
A Flock of Meesevor 1 Jahr

KallistiOS

Ähnliche Videos

The #GTA 3 port to the Sega #Dreamcast has been progressing at an incredible pace. It's been amazing to see the whole DC community come together to tag-team this "impossible" project... Here it is running on a stock DC, no longer requiring the 32MB RAM hardware modification, only a few weeks into development. Since I finally got the time to sit down, build the codebase, and look into some of what I think is the critical path for performance, let's talk about some technical shit, and some of the future steps I think can be taken to further improve performance. First of all, I want everyone to take note that this is NOT a port of the PS2 version. This is a port of the PC version, which has extra content, increased draw distance, improved textures, and other things that have actually increased the challenge here... Whether the DC version will ultimately have these additions or not will remain to be seen, but we're running into plenty of shit that the PS2 didn't have to worry about (like these big-ass PC replay saves won't fit onto a Visual Memory Unit!) Secondly, lets talk about what is and isn't currently optimized, because it's absolutely vital that the DC's hardware is fully utilized here for the sake of performance and achieving a competitive polygon count. Unlike with modern devices, where the whole graphics pipeline is handled by the GPU, both the PS2 and Dreamcast were responsible for transforming and doing lighting calculations for each vertex BEFORE they got submitted to the GPU. The PS2 had a vector coprocessor to do this, while the Dreamcast had a few extremely important SIMD and fast math assembly instructions on its CPU to do these computations. Up until literally just a few hours ago (not shown in this footage), the Dreamcast's SH4 was doing 100% of these operations in slow-ass plain C and C++ code, which is absolutely sub-optimal and is immediately bogging down its CPU with just transforming vertices, bottlenecking the entire graphics pipeline on the fist T&L stage, and also leaving less CPU time for handling other gameplay logic... this is going to absolutely have to be addressed (and already has begun to be). Another issue that is crippling performance here is the fact that the models are all using individual triangles rather than triangle strips, which the Dreamcast's PVR GPU was designed to handle better... Converting these models to use strips rather than individual triangles will result in MANY different gainz for the DC, as you're going from 3N to N+2 vertices per triangle. Converting the models to triangle strips will 1) reduce load times, since model assets will be smaller 2) reduce the amount of video memory required to hold these vertices on the GPU 3) reduce the amount of shit that must be transferred from the CPU to the GPU and 4) give us back a bunch of CPU time, since the SH4 will be less bogged down transforming redundant vertices! TL;DR: This is still EXTREMELY suboptimal in terms of fully utilizing the graphical potential of the Dreamcast. There is going to be a LOT that can be done still to both improve performance and polygon counts, so stay tuned! FINALLY: Mad respect and love to Stefanos Kornilios Mitsis Poiitidis, for doing an amazing job leading this project, and to Frogbull , Esppiral, and everyone else who is helping us stick it to the PS2 by making this happen! #gamedev #retrogaming #cplusplus

Falco Girgis

88,356 Aufrufe • vor 1 Jahr