Hi. It should work fine on hardware too. It's just that the boot code I've been using is screwed up in some way so it only works properly when booting it from GD via USB, not SD card.
I'm gonna fix that soon across all my Jaguar projects (I have more on my main itch https://happy-ferret.itch.io/, but they all exhibit the same issue).

neoprium
Creator of
Recent community posts
I mean it's ok if he feels disappointed and there's no need to attack him (love to all the moms in the world. I wish I still had mine) but yea, it definitely didn't feel very constructive.
But hey. I did spend a night performance tuning and adding more of the first stage after his comment, so maybe in a way he was constructive.
This isn't a product. I'm in no way related to Fonzie or the official Paprium devs.
This is a tech demo.
I'm just confused what triggers comments such as "You've still managed to disappoint me" or "I was expecting a proper conversion" when I've made it abundantly clear from the start that this isn't a finished project.
No offense, but what part of "Vertical Slice" wasn't obvious? I built this from scraped together parts of my Duck Engine (which, admittedly, kind of explains the hitboxes needing to be fine-tuned. My friend's game we're building in that engine is an homage to Virtual Boy Warioland, so hit detection is quite a bit different) in a relatively short amount of time. I never pretended it was a fully completed conversion.
It probably still beats any AI slop attempt, even at this early stage. At least I'm not wildly dropping frames.
The same digital sorcery I'll probably employ for the Neo Geo, stripping things to their bare essentials first. :)
Trying to base everything on a relatively heavy decomp and my earlier N64 port was a bad idea.
With this newer, slimmer and trimmer codebase, I can bring Paprium to Neo Geo, Atari Jaguar, 3DO and other platforms with room to spare (I could totally do it with the original as well. But it's a lot more fine tuning than recycling the code I already have for these platforms, thanks to my Duck Engine) and leave the original decomp in place for modern PCs and 5th gen consoles, as well as preservational purposes.
Yea. He sure loves to focus on Paprium and act like he owns it, while his customers (like Fonzie's) wait for stuff he never delivers.
Dude claims credit for a generic for-loop that calls directly into the Paprium VM (which is technically Fonzie's code) and thinks me using asset extraction code from another project means the other project's license is being infringed upon even though the extraction code never ends up in the linked binary (only the assets themselves do which are, again, Fonzie's).
Imagine how desperate for attention somebody has to be to file a DMCA for code for an essentially pirated project. He's no better than Fonzie and his customer's agree.
Well no, the unpacker isn't part of the shipped product so that alone wouldn't force a GPLv3 license on my codebase. Otherwise the Paprium assets themselves would have to be GPLv3 licensed, going by that logic.
I'm gonna put up the source tarball later today when I'm hopefully no longer bedbound (I'm posting from my phone and the computer is in another room). I haven't gotten around to writing a README yet. Hope that's ok.


