Jump to content

PeteE

Members
  • Content Count

    386
  • Joined

  • Last visited

Community Reputation

962 Excellent

1 Follower

About PeteE

  • Rank
    Moonsweeper

Profile Information

  • Gender
    Male
  • Location
    Beaverton, OR

Recent Profile Visitors

6,183 profile views
  1. If I were redesigning a true 16-bit 99/4A, I would love to have access to the VDP RAM through the 16-bit bus in addition to the VDP read/write port. Would this require some sort of RAM chips that can be accessed by two different buses simultaneously, one for the CPU side and one for the VDP side. (Is that what dual-ported RAM means?) To access the RAM on the CPU side, I would want it to be accessible directly, perhaps by mapping it by 8K chunks into the DSR address space from >4000 to >5FFF. Using the CRU to activate the mapping and select which bank is active. There would be no need to limit it to 16K VRAM either, since it could access more by bank-switching. If external peripherals also need to share the DSR address space through the 8-bit bus, then the 8-bit multiplexer and wait states would need to be disabled when accessing the banked VRAM. Having fast access to the VRAM would make it possible to develop more advanced and better performing graphic demos and games.
  2. Are you familiar with bitmap mode on the 9918A? Familiar with sprites and transparency? Which programming language would be best for providing an example for you to understand?
  3. I too picked up a Phoenix on the hopes that there would a be a TI 99/4A core eventually made for it. I was going to build my own core in the process of learning VHDL, but I got as far as getting the F18A test screen to show up before losing interest. I noticed that the Phoenix CV core on github had a massive commit about 12 months ago... haven't gone through to see what changed. Maybe someday.
  4. I added one more song, and put all the source files together in the zip to show how to use the vgmcomp2 player with xas99.py. The .snm files are converted to .vgm using SnevenTracker, and the .bat file converts using the vgmcomp2 tools to .sbf. Then the Makefile builds the cartridge using xas99.py with a hacked-up version of Tursi's player code. f0music.zip f0music8.bin
  5. I was playing around with vgmcomp2 today and made a little something. Actually, I found SNevenTracker by accident and then found this F-Zero arrangement, and then put them all together for your listening enjoyment on the TI. There are no graphics because I am lazy; audio only. f0music.bin
  6. I couldn't wait to get home and hear it on my real TI. I like it!
  7. Check out this multicolor sprite solution for the Turmoil clone on 99/4a. It only works for a solid background color though.
  8. I escaped from zontron27. Fun little game.
  9. Same here. Thanks for the fix.
  10. Cool idea! I've got a mechanical cherry mx red keyboard for my PC and I love how it feels similar to the TI keyboard. For making the keycaps level, could you break up the pcb into one per row of keys, then 3d-print stair stringers to support each row pcb?
  11. Thanks for the encouragement. I will try to make progress soon.
  12. Funny story, at Fest West 2017, your system with F18A was the very first time I was able to test Tilda on real hardware, and it worked! Later I was showing to someone with 9918A system, and the scrolling would cause wrong characters to appear all over the screen - all due to no delay after setting the VDP read address before reading the data. I added the delay instruction, recompiled the code on my laptop and tried it again, success!
  13. I've estimated LI Rx,data to be 24 cycles, since the R0 is actually the VDP write data port, that incurs the 4 cycle penalty as well. 12+4+4+4=24 cycles
  14. Could it be... a pair of pain-sticks? (TI 99/4a joysticks) That's really clever, and probably more comfortable to use in that orientation.
×
×
  • Create New...