Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by SlithyMatt

  1. No, I just use direct manipulation of VRAM. The Kernal routines are limited, and not terribly useful unless you are doing something exactly like what they were written for, and the VRAM interface is really just as simple to use. Here's the video:
  2. That was definitely the highlight of the games I've discovered with this console. Never knew it existed, but it's a really good game! I think if it hadn't been shoehorned into the Street Fighter franchise, it might have fared better, as it's such a completely different kind of game.
  3. I did a couple livestreams playing around more with the "620 in 1" NES Classic clone, and edited them into a single video: If you want to see the original, unedited streams, they are on my second channel: https://www.youtube.com/channel/UCNPJDAcKcAUYfemAMwqa56g
  4. I bought one (well, actually two) of those NES Classic knock-offs from Wish out of sheer morbid curiosity. Turns out to not be quite as horrible as I had feared (which was really bad), as captured in my latest video:
  5. Target whichever one you are more comfortable with. Both are going to be on the X16. The PSG is going to give you something more like the C64 SID (but not quite) while the YM2151 will give you something like the AdLib or Sound Blaster FM synthesis (but not quite). The PSG can be programmed much more easily, but you can use commercial software (namely Deflemask) as a tracker for the YM2151 and get all the register writes and timing that you need to do. I made videos about both so you can see how they work: PSG: YM2151: I will also be making a video on how to use the PCM in the future, as well.
  6. Congrats! Hopefully it goes better for you than.... Leisure Suit Larry?
  7. I just happened to have these lying around:
  8. I'm not a professional educator, but I do actually make a living as a technology communicator, which has also driven my side gig as a creator of programming tutorials on YouTube. Please feel free to use my X16 tutorial series for any folks looking to go the extra mile (or kilometer, depending on location) and learn 65C02 assembly language: I have also dabbled in mixing C with assembly language:
  9. Oops, forgot Episode 3: And now, Episode 4 is out:
  10. He tried to add it, but the flux capacitor kept leaking.
  11. The last prototype had a YM2151 and both PSG and PCM in the VERA, just like the emulator. The SAA1099 is no longer on it, and was never emulated, anyway. Kevin made no mention of any changes to the sound for the third prototype, so it looks pretty set right now. The FAQ is a bit ambiguous, mostly due to staleness, just like the 8BG videos are very old now, the last coming out right after the first prototype was up and running. The only difference in the sound since the R38 emulator is a change to the addresses for using the YM2151, which is reflected in the most recent commit to the repo, which will eventually R39.
  12. I've had success using Krita for the actual drawing part, and then exporting it to Gimp to do the palette conversion.
  13. I use Gimp, and that works just fine on any desktop platform.
  14. I don't doubt you could pack a very simple C++ program into that much memory. But you are also dealing with a MUCH faster processor than an 8MHz 6502, and a much simpler system that doesn't have to do things like manage VERA graphics and play PSG sound effects. As for C++ on mid-80s DOS PCs, it was not really a common thing, and I don't know of any commercial software that was developed using C++ for that platform in that era. C++ didn't really take off on Wintel PCs until the advent of Visual C++, and that was really for 486 machines and better. Look, I don't want to discourage people from trying anything, but just to manage expectations. We have the gift of the X16: a machine so beautifully simple and yet so capable it becomes a joy to program in assembly language or in very simplified C and create really wonderful software. Adding all this complexity and abstraction is just going to give you something watered down, a less capable PC. Again, JUST MY OPINION, but this goes into the territory of just getting a Raspberry Pi and doing C++ development there. Or python or whatever.
  15. Even if it's a freestanding application with no iostream or other standard library calls, this is still not a bare-metal Raspberry Pi were talking about here. The X16 is much, much smaller. You will still need a separate frame stack and probably a heap to make C++ worthwhile. You could allocate everything statically, and then you just have classes standing in for structs and not doing any of the actual OO things. The question really becomes, "what is the value added by developing with C++ over C for the X16?" Sure, you COULD do it, but is it really going to make development any more efficient or enjoyable? Or is it just a parlor trick of "hey, look: 8-bit C++" and then you go back to assembly or just plain old C to develop a real application?
  16. It's about what kind of 6502/X16 code would be generated from an LLVM iostream implementation. Using C++ is nice, but using the language as intended on a 6502-based system is a bit dicey. What's lean and efficient on an x86-64 or ARM64 with GB of RAM could still be bloated and sluggish on a 6502 with kB of RAM.
  17. cout << "Hello, World!"; Hello, World!
  18. It would help to better define what you mean. Are you looking for something like a 486 motherboard?
  19. This is the best one I've found: http://map.grauw.nl/resources/sound/yamaha_ym2151_synthesis.pdf
  20. This reminds me of a stash of faxes from the 70s that were from my grandfather's desk at AT&T. They were totally memes, and early fax adopters did share them with their social network. Like, political memes from the 1972 election, but then they would have just called them cartoons. Anyway, to get back on topic, if Commodore did the right thing and hired me (a grade school kid) to replace Jack, I would have made much better decisions. I mean, it would be hard to make worse decisions. First off, when the C128 failed to expand the 8-bit market, that would have been the end of it. Keep selling C64s and software and peripherals until the market dried up, just like Apple did with the ][ line, meanwhile concentrating R&D and marketing efforts on the Amiga. If they hadn't tried coming up with 50 different 8-bit platforms that nobody wanted, they could have made the investment that would have prevented PCs and Macs from overtaking the Amiga in capability in the early 90s. As I recall, the Amiga barely existed in the US -- I only knew it was still around because of magazine articles mentioning that certain games were also on Amiga (to only a slightly greater extent that Atari ST support). They should have been matching Apple's marketing budget dollar for dollar, and making sure the tech stayed just ahead of PCs as Apple did and managed to survive long enough for Jobs to refocus and reinvigorate the company. Who knows who the savior of Commodore could have been in the mid 90s (besides a now-adult me, of course), but I bet they could have pulled through if they didn't make half of the staggeringly bad choices they made in the late 80s and early 90s.
  21. It's really hard to beat a Chromebook for value: https://www.amazon.com/Samsung-Chromebook-Celeron-Processor-Gigabit/dp/B07XL4JHXR?ref_=Oct_DLandingS_D_d11b2207_65&smid=ATVPDKIKX0DER&th=1 You can run python and all sorts of games on them now. Not really for learning about low-level stuff, but it's a great option for a kid's first PC and meets all their needs, including learning how to code. If you are marketing something less capable at the same price point, you might as well just make a bonfire with your money.
  22. You could try contacting the developer. There is an email on the Google Play page. Chances are they are not active in this community anymore, but may be willing to share their code.
  23. Actually, there is: https://play.google.com/store/apps/details?id=dk.applimate.x16emu&hl=en_US&gl=US Funny thing, that Google. You can actually search for apps on the Google Play store for the Google-controlled Android OS. Just note that this is not an official build of the emulator, and it is using a very old version of the emulator code and ROM. Also, without a bluetooth or USB keyboard, it's pretty useless. But the work has been done, and it shouldn't be too difficult to update the build.
  • Create New...

Important Information

Please review our Terms of Use