Jump to content

AndyMt

Members
  • Content Count

    173
  • Joined

  • Last visited

  • Days Won

    7

AndyMt last won the day on April 5

AndyMt had the most liked content!

Community Reputation

162 Excellent

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This sounds familiar . I do something similar in Brixx and Invaderz for the laser sprites and explosions. The main player sprite and some others use fixed slots, though. I'm very much looking forward to the end result.
  2. Just press the "Try it now" button on the download page of the program . This will run it in the web based emulator in your browser.
  3. I'm seriously considering planning this! Right now both my games use slightly different variants of a lib for sprite handling and music - due to "historical reasons" and lessons learned. I want to migrate both to the same code base. Then I think it would be time to release it to the public.
  4. Yes, that's something I was looking at, too. And in the comments there were some references to the X16, so who knows...
  5. Thank you very much! I'm thrilled to see my games made it into the top spots . I took inspiration from "Chase Vault" when I started this, so thank you very much that you shared the code on GitHub. I'm still too embarrassed on my code quality, but I promise to share my repos when I've finally managed to clean up the mess. Both games were written mostly in C, but some parts in assembler, like the IRQ based soundfx and music player. To my surprise sprite/collision handling, controller and gameplay coding is possible in C, even though CC65 doesn't really optimize. Of course as you mentioned, it is important to be aware what the compiler will do with the code. So in my brain there is a "compiler" running in parallel while coding, to avoid performance issues. I'm sure on a C64 with it's 1MHz CPU this would have been impossible.
  6. I had the same question here: I settled into detecting which ROM version is present, here are the details:
  7. Almost certainly, as the controllers were moved from VIA#2 to VIA#1. I haven't looked into this at all as I don't have a game controller to test this with. Keyboard emulation works in the emu, though, I don't know how that's done.
  8. During the last few days I've spent a lot of time debugging my software in the emulator, running from an SD card (VHD file). This is because some things in the emulator behave differently when loading stuff from SD card instead of the host file system. Anyway: in Windows I found it quite fiddly to update the SD card VHD file for every debug cycle, so I came up with a solution to do speed things up. After a cc65 build I now only have to run a single cmd file which even puts the LOAD"MYPROGRAM.PRG" and "RUN" into the clipboard. Now I just have to press CTRL+V and the PRG is loaded and started. Prerequisites: VHD Attach tool (OSFMount wasn't flexible enough for this, but maybe someone else figures it out) an SD card VHD image (this is the one from the X16 github repo) X16-emulator install directory is added to the system PATH environment variable VHD Attach install directory is added to the system PATH environment variable compiled PRG and BIN files of your software are to be found in the "out" subdirectory Preparations: attach (aka mount) the vhd file once by right clicking and selecting "attach" note the drive letter which is assigned (in my case X:, it will stay the same) put a first set of your files into the VHD detach the VHD file (right click) Now create a batch or cmd file which does the following: attach the VHD file wait 2 seconds copy PRG and BIN files to the assigned drive letter wait 2 seconds detach the VHD file (so the emulator can use it) put the load command into the clipboard run emulator Here is a sample .cmd file I've used: VhdAttach.exe /attach test.vhd ping 127.0.0.1 -n 2 > nul copy out\*.PRG X:\ copy out\*.BIN X:\ VhdAttach.exe /detach test.vhd ping 127.0.0.1 -n 2 > nul (echo LOAD"INVADERZ.PRG",8 && echo RUN) | clip x16emu.exe -sdcard test.vhd -scale 2 -keymap de-ch Replace "test.vhd" with the filename of your VHD file, the PRG name with yours and also select the correct keymap parameter (or remove it). This saved me a lot of time, maybe it helps others, too.
  9. I've updated my Repo so now waitvsync() uses RDTIM instead of the TIMER memory address. This makes it compatible with more ROM versions, but also a bit slower. I'll change this back as soon as the TIMER address has settled. My cc65 repository: https://github.com/AndyMt/cc65
  10. Do you happen to have a Windows build of the latest r39? I could not get this to compile, I have neither Mac nor Linux machine.
  11. Thanks - maybe I should use the Kernal function to get the timer value for the moment. Even though that's less efficient.
  12. The PRG format is just about loading a program into memory. Loading other things into VERA memory or banked RAM is independent of how the program got into memory. This happens by using the KERNALs API and for example loading BIN files into any memory type. A PRG can optionally contain a small amount of graphics data which then has to be copied into VERA by the program itself.
  13. I branched the cc65 repo and started changing the cx16 lib. It now works with Invaderz and Brixx and both would now run on R39. In case anyone wants to check it out: https://github.com/AndyMt/cc65 I'll do some more testing myself before creating a pull request.
  14. I've now created a test version running on R39 and maybe (?) on real proto #2 hardware. I won't put this in the download section, but if anyone wants to try, I attach the file here. Not sure if this works on a SD card, I just load from device 8. @Michael Steil: I understand you have one of the few existing boards. So just in case you find the time, maybe you can test the attached file ? INVADERZ R39.ZIP
  15. Added a Kernal/ROM version check. Will only run on R38, as well as on custom ROMs on your own risk. This is in preparation for the upcoming R39 on which the current game won't work.
×
×
  • Create New...

Important Information

Please review our Terms of Use