116
Sega Saturn Slim: The Classic Console, Reimagined for Today’s Gamers
(www.retronews.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Sep 2024
116 points (98.3% liked)
RetroGaming
19541 readers
118 users here now
Vintage gaming community.
Rules:
- Be kind.
- No spam or soliciting for money.
- No racism or other bigotry allowed.
- Obviously nothing illegal.
If you see these please report them.
founded 1 year ago
MODERATORS
Okay, people will likely bash me for this hot take, and if this is for you feel free to enjoy it, but...
...why do this instead of using a FPGA or emulation-based solution?
If you don't want to run original media or don't want to output original video out signals, why bother to use original hardware at all? I can see it as a way to upcycle heavily damaged Saturn units, but there aren't that many of these in the wild in the first place, why dismantle an existing piece to make what is effectively a completely different product? I don't see the point.
Why bother? Because feeding data into the console and getting audio-visual signals out of it are both very well understood and can actually be replicated with essentially total accuracy. But the complex operations and subtle interactions of CPU, VDUs, RAM, and other support chips can't. That's the important part of the console, not the optical drive or the analog video output.
Software emulators and FPGA-based systems give it a good try, and can often run the majority of software for a console at an acceptable fidelity for most users, but they're a long, long way from being 1:1 perfect, and the more recent the console, the more games either don't run properly or don't run at all.
Right, but now you're giving me arguments for using original hardware, not for modifying it.
See, that's the part that loses me. I use original hardware all the time, I have tons of original hardware and software for a whole bunch of platforms, including ones that are trivial to run in cycle-accurate emulators and FPGA reproductions. All good there. I even have some flashcarts and softmods to allow cross-region usage or to consolidate libraries. No problem with that.
But that is based on using the original hardware, unmodified. Once you start gutting it for mods then you're working against your argument that complexities and sublteties of original hardware are important. I mean, yeah, I do care to at least have a way to go back to sanity check the sublte ways in which original hardware parses the code in a rom. But for that same reason I want to see how the default composite or RF signal subtly interacts with that output and with a period-accurate CRT display. I want to hear the CD spinning when it's supposed to spin and the original loading times.
To be clear, I think this is just a case mod, but I'm talking about the modding scene more generally. I don't see why you would think "total accuracy" is important in the interaction between the CPU, VDUs and RAM but not on the I/O. Wouldn't the CD drive and the video signal be part of "total accuracy"? Wouldn't the form factor of the shell and the controllers be a part of that accurate experience as well? If you push me I'd even say I consider a MiSTer FPGA solution with a correct analogue out signal and an original controller feeding into a CRT is far more accurate to the original NES than the original Analogue NT that was made from gutted NES parts, or even than an original console pushed through an HDMI scaler or mod.
I guess there is no accounting for taste, but I do struggle to follow the logic where running the original CPU and video chips on completely different I/O is justified by trying to maximize for accuracy.