Recent content by mrkotfw

Are you certain that your texture generation is correct?

This is excellent work. I think that using the original font is the best way to go.

This looks great! I take it that your SD card adapter has a 5v to 3.3v convert built in? If so, which one did you purchase?

I'm interested in buying a GREEN LED USB DataLink so I can fully test the device for my tool. I have the documentation and implementation, but I'd like to physically test it. If anyone is willing to part with it, please let me know.

Similar to the issues you've opened on GitHub for libyaul (and other projects), I've asked you to provide detailed information regarding your issues.

Copy any example and edit the Makefile, along with the main .c file.

The GNU assembler is an option. You can also look to see if there are any 32X ones... Worst case, you take an existing assembler and add SH-2 support. You don't need anything special. It's just a raw binary.

How much did all of this cost? This would be good to have for people who don't have access to a USB dev cart.

What first started as a port of ndiddy's code base from SBL to Yaul, ended up as a new-ish game with major changes to the code base. Sound may not work on real hardware. If the game does not work on real hardware, please run via Mednafen. Original code base: shicky256/saturndevsbl

This is great to see! Thanks for writing the articles.

It's confusing, really. The priority bits in the color bank code (VDP1) is an index into the sprite register priority (VDP2). So let's say you set sprite register #0 to be 7, sprite register #5 to be 2. In your VDP1 command table, if your priority bit(s) is 0, then your sprite will have a...

The ports themselves might just be fundamentally broken, as is the case with SS SoTN. But it would be interesting to start a quick decompilation to see if there are any clues as to what they're doing.

Use Jo-engine to get started. It looks like you're on the wrong path (for now). https://www.jo-engine.org/tutorial/

Shouldn't the correction on pg. 40 where it's written: "If the timing for frame change is known in advance in normal or high resolution screen modes, specify erase then change and perform erase/write during the display period. In this case, erase/write of the entire display screen is possible."...

pg. 39 where it says "Set the value of the VBE and FCT bits to "0.", it should be "Set the value of the VBE, FCM, and FCT bits to "0."