SpritesMind.Net

You need to either avoid using the 68K->SH2 "DMA" channel, or add error detection to it as it's buggy. Real games that use the 68K->SH2 DMA do retries for when the transfer fails. My own experiments have shown it's really damn buggy. I go with a processor polled exchange of data through the communi...

So, did anyone figure out how to get this working on HW?

I'm thinking about doing some tile-heavy 32X work and it would be amazing if I could get graphics anywhere near this

Almost 10 years passed since I wrote my "monitor". It's simple text-based command processor with small amount of directives. Nothing special, but it supports PS/2 keyboard on 1 joystick port, uses some interrupts and able to work with memory. Able to launch code that manually entered to the RAM. Wr...

Interesting idea. I've thought of doing this myself but haven't gotten around to it proper, though you could see the Forth I wrote as a simple operating system.

I could write a proper editor in it, and it almost has cooperative multitasking.

Pretty cool idea, but it would require at least keyboard support to be "not painful" to use. :D True, but I don't have a megadrive keyboard to use :lol: Anyway, the interactive mode, while cool, is probably best used for testing, afterwards you should be able to type in the same code on your pc and...

That's pretty cool. I also did some Forth stuff for the Megadrive a long time a ago. But I used cross-compilation rather than interpretation (I had written a Forth compiler that could generate M68k assembly, which I then assembled and linked with the GNU binutils). A cross-compiler is probably more...

I've been working on a small forth system for the Megadrive part-time for about a month now, it's very rough around the edges and buggy, but someone suggested that I upload it. It might be fun to mess around with. https://dl.dropboxusercontent.com/u/3581058/mega-forth.gif Source: https://github.com/...

That animation is very useful, thanks for recording that. From looking at what you're doing, I think it's actually just a user interface update issue, I think the register is in fact being set correctly. On those debug windows, when you put the cursor into one of the text boxes, updates are frozen ...

I found a bug while working on some code.



Basically, the line isn't updating the A6 register.

much better :) but still slow :( Heh, don't worry. I just got a much faster algorithm working on my pc, and your post has inspired me to get it working on the genny. I'm (obviously) not hoping to get this kind of resolution on the genesis, but here's a hint http://www.youtube.com/watch?v=W9EF-Ug0oH...

Ok, so I've figured out what the bottleneck was. It's not the memcopy, or even the cell processing, but the drawing. I restructured the program to use DMA to draw the whole screen at once, so that's very quick now. I have to speed up the algorithm (or use a different one) if I want it to be faster n...

You will need gcc compiled for 68k development, some other tools and Makefile changes, etc. This is all already done for Linux, including SGDK here: https://code.google.com/p/gendev/ And some forum posts: http://gendev.spritesmind.net/forum/viewtopic.php?t=1248 Oh, awesome, now I don't have to rebo...

Is there anything in particular that prevents sgdk from working properly on Linux or OSX if I swap out the gcc/ld binaries?

I'm guessing some of the tools are windows only, and I might need to tweak the makefiles, but other than that?

Adding long can be not faster though. I don't really know. Updated previous post, and I'm still thinking that bits->bits lookup is possible. Do you use DMA to write name table into VRAM? I don't know which way is faster. I don't do any DMA except for perhaps when loading tiles on startup.. I don't ...

ok then only lookup table will help. Haha, well, my solution already has most of the benefit of the lookup table anyway. A lookup table requires a bunch of reads (and shifts/ands to create the bitmap) to check cells, I only require one read (and a couple of compares) to check a cell, then a bunch o...