[Release] Vice3DS-C128 (C128 Emulator)

New 3DS again TT

 

what do you expect? The old consoles have shit for power. if people find it slow on new consoles. the old ones are not going to stand a chance.

 

This is really exciting stuff; I grew up with the C64 but never had a 128, this seems like the perfect time to jump on board.

I don't have any 128 software yet, so I tried loading up a few C64 games since I recall the 128 was backward-compatible, but they all seem to crash on a blocky green screen. Is there anything I can do on my end about that, or is that a non-starter?

Regardless, thanks so much for making this. Off to check out what 128 games were good!

 

Aha! Yep, this does the trick. Zeropaige's Super Mario Bros. C64 port correctly identifies the system as a C128. Thank you!

 

It really is amazing that the N3DS can handle GBA/SNES/MD etc... emulation, but can't even handle a C128

 

Been reading about the C128 a bit more and just found another tidbit: you can switch to C64 mode at any time from the BASIC shell by typing "GO64".

EDIT: I figured I should expand on why anybody would use a Commodore 128 emulator to play Commodore 64 games in backward-compatibility mode when there's already a perfectly good Commodore 64 emulator. The answer is pretty simple: both systems use 6502-based CPUs, but while the C64's is clocked at 1MHz, the C128 has a variable clockspeed that can run at 1MHz or, for C128 and C128-enhanced games, 2MHz. Because of this, there are several C64 games which take advantage of the bump to the 128's hardware to run better:

The disk for Qix had a normal C64 version on side A, and a C128-enhanced version on side B. Ultima V has no music on the C64, but play it in C64 mode on a C128 and it uses the extra processing time to have music playing throughout the game. This also extends to homebrew, like Zeropaige's Super Mario Bros. port, which runs pretty poorly on a stock C64 but can be enhanced by CPU addons or, drumroll, the C128. There's still some slowdown, but it's really night and day.

 

WoW! All the really good stuff happens when I'm out to sea. Can hardly wait to dig into this one. Perhaps I'll upload a disk image of some music I transposed into C128 BASIC when I was young Gotta test it out on this first though.

 

Anybody interested in this emulator should try out Elite 128, which is a highly modified and improved crack of the original Elite.
It runs in C64 mode on the Commodore 128, and utilizes the 2Mhz clock speed, which makes the vector graphic run smoothly. It also runs on a regular C64.
https://csdb.dk/release/?id=176103

The emulator is a little difficult to find on GitHub. Here is the direct link of V. 0.1
https://github.com/badda71/vice3ds/releases/download/1.5/vice3DS-C128.3dsx

 

Is it possible to port the Vice-VIC-20 Emulator to the 3DS as well? I think this should run at a good framerate on the Old3DS because I get around 2000% speed when in warp mode in the Vice-VIC-20 emulator on my PC. But on Vice-C64 I only get around 300% speed in warp mode.

 

@Badda I've just updated my firmware to the latest, and Luma to the latest, and the c128 .3dsx file no longer works. It crashes the system! The installed c64 still works.

Building from source is kind of messed up as well. I'm assuming that the couple of uses for GSPGPU_FramebufferFormats are meant to be GSPGPU_FramebufferFormat (in the latest libraries... unless it really needs gfxFramebufferFormats?)

But I can't wrap my head around sceneInit in SDL_n3dsvideo.c. There is an implicit non-static declaration at line 421, but then a static declaration at line 723, and in the end, I end up with a defined but not used error on sceneInit anyway.

Edit: sceneInit wasn't an issue (since apparently it isn't used), I had to look farther up to see another GSPGPU_FramebufferFormats that I missed taking the "s" off of. But at the end, there are a ton of "undefined reference" errors to a buttload of important stuff, as well as cart/magicvoice.c having some things WAY out of the array bounds. Something is really fishy when it comes to linking... it must be in the makefile, but I don't see what's wrong.

 

It works! Thanks for re-compiling! Wish I could simply clone and compile myself though. You have a perfectly good .cia for C64, and I'd really like to build a .cia for 128. One thing to note, in case people with weird boot choices try to report bugs. Background first... I boot into a franken GW emunand quite often because I like their cheat engine. It seems that now, the only way for me to load up HBL (in GW mode), is via *hax.

With that in mind, the UI (at least on 128... didn't check c-64 just now) is super sluggish, and either I am impatient, or it freezes on a red BOTTOM screen when trying to quit the emulator. Again, this is only when getting into HBL via *hax. When loading HBL via Rosalina, it seems pretty much perfect to me . This is my main reason for wanting a .cia for 128.

Edit: do you have local changes not committed to .git? In case you were using a wip ctrulib, I just pulled, compiled, and installed from the current source, and tried to build vice3ds again. right off the bat, it errors out on GSPGPU_FramebufferFormats (and changing that to GSPGPU_FramebufferFormat everywhere it appears gets past it). I still end up with linker problems in the end though. spits out a ton of undefined references that I know are actually in the source. All things installed under dkp-pacman are up to date, with a (now) fresh pull of the ctrulib source).

~/projects/vice3ds$ git checkout
Your branch is up to date with 'origin/master'.