@foone This triggered a vague memory: on PS2 I don’t think you could pass command line arguments when launching an executable. The solution was to write them to a text file, and read them at startup if they existed.
(This was well over 15 years ago, so I don’t know 100% if my vague memory is true!)
@foone Is it a port? Is it a multiplatform engine? My first thought would be there’s a PC version (maybe dev-only) and for PS2 they burned a file with the command line in the DVD
@foone@vi Betcha they've got a command line underneath for testing, QA, and dev. Every imaging, surgical, or other embedded platform I've worked on has one (sometimes you've gotta do weird rituals to get at them, but they're there.)
@foone You're reminding me of a Java-based installer on Windows years and years ago that hit the end of the window and the installed % bar kept going past.
I figured it was an excellent value, where else will you get 379% of your program installed!?
@foone
This reminds me of the Chromium development “getting started” page which warns people that their git repo cannot be cloned into a FAT32 drive because it contains files over 4 GB.
@foone "Microsoft Minutes" have been the hidden standard for learning patience since the 90s when I crashed an Exchange server waiting NT 4.0 to shutdown based on a similar prompt.
@foone It's SPU BRR, a weird ADPCM variant that Sony introduced with the SNES and CD-i of all things and then kept using basically forever (reportedly even the PS4 and PS5 use it). Each 16-byte chunk decodes to 28 mono audio samples; the first byte is a header containing parameters to decode the chunk, the second byte holds loop flags (hence why it's usually 00 or 02) and the remaining bytes hold up to 28 nibbles. Shouldn't be too hard to decode.
Add comment