I just updated the ROM with version 1.1: https://github.com/santiontanon/talesofpopolon/releases/tag/...
The biggest change is MSX Turbo R support (thanks sd_snatcher and ARTRAG for help with this!). When playing the game on a Turbo R, you can press "R" in-game to switch CPU mode to make the game run faster or smoother. My favorite way of playing on a Turbo R is wither maximum viewport size with R800F mode (maximum screen size), or minimum viewport size with R800S more (maximum smoothness). But of course, the focus is swill MSX1 computers :)
The stack issue should be resolved (except for Sony HB F500P, but holding SHIFT seems to work for me).
Mmmm, weird this HB-F500P MSX model... As you are not using disk in your ROM, there should be ne problem, unless the disk driver installs an interruption handler (the Philips MSXs use this to stop the disk from spinning after a while). So maybe resetting the interrupt hooks (poke 0C9h at 0FD9Ah and 0FD9Fh) could fix the problem?
About joysticks, that should be already supported (let me know if it does not work). The only things you cannot do with joystick is switch weapons/armors (for that you still need to use the "1", "2" and "3" keys in the keyboard).
Ciao Santi,
I've tried the Joystick, and the buttons and arrow keys seems not properly associated.
For example:
buttons A = upward
buttons B = backward
UP = weapon
@Louthrax: oh! that could be it! I'll give it a try later today.
@journey: oh! ok, added to the to-do list! I'll look into it tonight. I re-used my joystick code from Transball, so I assumed it'd work out of the box. But apparently I was overconfident!
Oh impressive, a 3D game for MSX1!
The scrolling is less smooth on a real MSX. You should try to make direct access to the VDP.
A game can succeed the AcidTest but be incompatible with most of MSX and the reverse also.
I've tried the Joystick, and the buttons and arrow keys seems not properly associated.
Same for me.
A game can succeed the AcidTest but be incompatible with most of MSX
Hi GDX, I'm curious about that, do you have any example? I think the point of the AcidTests is just to ensure that the hardware is accessed in a "compatible" way, but it does not prevent to code weird things that will not work on all MSX.
and the reverse also.
Ok for that.
@gdx, really? is it less smooth on a real MSX? ouch!
I have only tried OpenMSX (my MSX is back in Europe in my parents place). A youtube video showing how it runs on a real MSX1 might help me see what is happening
Ok, confirmed Louthrax solution (poking C9 to FD9A and FD9F) fixed the problem for Sony HB F500P! I also fixed Joystick support (I hope ), and updated version 1.1 in GitHub: https://github.com/santiontanon/talesofpopolon/releases
Also, I recorded a small video showing the new MSX2+ Turbo R modes: https://www.youtube.com/watch?v=UBAOzYZJNV8&feature=youtu.be
Wow really original, first game of this kind for MSX1?
Other games in first person on msx1 do not use raycasting so yes it is pretty unique.
On msx2 I remember a great maze demo with tile based red walls, shadows and a bouncing ball, but no sources included.
On TR there is my bot demo https://youtu.be/8ffvdvpePY8 (sources are in the dsk file linked in the description)