Asmusr

My first attempt to add real textures to the raycaster. It looked like chaos at first, but wait, there is a shield on that wall! js99er-20200807185454.webm Now I have some debugging to do.

I'm sure if any original AMS cards exist then @Ksarul will have one. Maybe I will try to implement the card in JS99er, but if would be nice to see some proof first that it does in fact enable Expanded BASIC 3 to use AMS memory for program and/or stack, which would be unique.

I'm sure someone can hack it to fix the detection, unless the hardware is working differently [edit: in a non-backwards-compatible way]?

JS99er is only interested in whether the ROM is inverted (paged379) or not (anything else).

I'm still not sure if Expanded BASIC 3 is expected to be able to use SAMS memory if only it could detect the card?

I added sprite editing a long time after the original author stopped maintaining the program. I have not kept the binary format up to date since I have no need for it, but the code is now on GitHub so it's possible for anyone to contribute. You should be able to extract the sprite data in hexadecimal either from the .mag file or from the assembly export.

What does the SIZE command report?

I wonder if these games are developed by a single person or the MSX community is big enough to put together teams of programmers, graphic artists and music composers?

The TMS9918A video chip sets the upper limit for characters and color.

@jedimatt42 perhaps you can explain how it's working?

In JS99er I'm using the Google Drive HTTP API, and the TIPI software on the RPi could possibly do that as well, but perhaps there is an out-of-the-box solution where you just map a directory on the RPi to your Google Drive? Anyway, it's probably better to discuss that in a TIPI thread.

Connecting the TI via the TIPI to cloud storage, e.g. Google Drive as I have done in JS99er.net, would probably be quite simple, but connecting to git via the TIPI would require a much more advance API than a DSR to be useful. You would have to be able to resolve merge conflicts, for instance.

I don't really understand your workflow, but wouldn't you obtain the same if you entered FC when the computer was reset rather than when you left XB?

I haven't thought this through, but maybe Omega needs an XB cart with a startup routine that bypasses the title screen and loads FC directly?

Best bang: F18A Least bang: PEB

Fixed.

Yes I also noticed that yesterday. I will work on a fix later today.

Whoa. What is CD sound?

I have released a new version.

It's not much of an editor, but if you insist on using sound lists then I guess it will help. However, for producing sound and music playable from assembly, working with VGM and a tracker on the PC combined with the tools developed by @Tursi is far better solution.

No I haven't worked on it since the last update. I would like to turn this into a full game, but the work of designing levels, puzzles and background story is not appealing to me. More features would also be needed to keep up the interest for more than a few levels. Switches, for instance, that remove part of the wall somewhere, could turn it into more of a puzzle game. And for the action part at least one type of boss, some different weapons and health kits. It's all technically possible, and I like working on new features, but I'm not sure it's worth the effort if it doesn't turn into a full game anyway. I think I will add a boss, which will at least complete the one-level demo. It would have to be done with very few characters, probably reusing characters from the existing guard. And if anyone is interested in designing more levels [edit: easy using Magellan], those should be possible to add too.

Which part of your screen is black (I assume it's not all black)?

Here is a a crash course on the debugger. It's quite simple, but it has been good enough for developing several games. Only one breakpoint (CPU, or F18A GPU) is possible To set a breakpoint, enter hex value in the Breakpoint box, or click Stop and then click the left side of the disassembly list to toggle a breakpoint at that address Click Step to single-step Click Start to run to your breakpoint Shift-click Step to run to two words after the current PC. If the current instruction is a branch this is effectively a Step Over Enter hex address of view address in the View Address box The memory split view allows you to view a disassembly of your program together with a selected memory region Note that unlike Classic99, the disassembly is a view of the current memory and not a history of executed instructions. This means you can 'disassemble' data and possibly get offset from your program's instructions The Graphics tab may be useful for inspecting tiles and sprites Classic99 has a far more powerful debugger, and I use it once in a while when I need to do something special like break on memory access or count memory cycles.

What is the value of R2 at >A070?

I would start with that option because it sounds doable within a reasonable time frame.