Ripping problems

I'm no expert on DC dev hardware but I'm guessing it was developed on something like the 5.24 with a really old SDK. Sounds like much older than the commonly available r9 SDK floating around.

Its executable are compatible and work just fine with the GD-ROM interface as well as the maple bus and so on. Just no VMU support, et al. Suggests to me that it was/is nearly complete hardware just not finalized in terms of peripherals and SDK software. Wanna bet you could find a Sonic Adventure beta out there somewhere in a similar state?

The main difference between set 5.24 and a retail DC is the form factor. I've never seen the inside of a 5.24 but I'm willing to bet the hardware is better cooled than the inside of a DC. FYI the DC isn't exactly a marvel of cooling technology but realistically it didn't need to be either.

Thing is I've never heard/read about the DC having any sort of thermal protection circuitry. When a DC resets on its own typically that's because the power supply pins move out of alignment causing a system reset. If I had to guess the thermal expansion induced by this game could be enough to cause those pins to move enough on a regular Dreamcast to reset the system. Of course Sega's engineers would have to be idiots not to put something in there to protect it from being stuck inside a plastic box for kiosk purposes.

 

well i guess we know why they never came out with giest force
and they didn't wanna recode the whole game from scratch

and it also confirms my theory that giest force was made before the GD-rom API's were finished and again they didn't wanna recode the game just to fix it

the developers were basically doing bang bang coding and very good at it

this is gonna be fun to play with

 

Seems pretty unlikely to me that it's overheating the system (at least, not any more than other graphically intense games do). Surely it's just crashing under load because it's slightly buggy and unfinished?