- May 3, 2020
Yes maybe this is the problem. On true hardware I am directly working with the hardware but I have considered that it is an emulated hardware which could potentially have buffers and different draw cycles with bugs of its own.when you're working with memory from 1024 to 2024 (40x25 tiles) they are directly affected by you, there's no doublebuffer of any kind; you're in direct control of the true hardware.
It is also totally possible the code is wrong. For now it is not that important, it doesn’t bother me. I’ll come back to this an other time. Thank you for the help.
Yes but even if emulated, I was hoping an actual hardware with HDMI, does some optimisation to compensate for this and this is why I didn’t want to use just an emulator on a Raspberry Pi. Figured it might be better.You also have to remember that it's also using a modern television. It's one of the reason why those that collect vintage computers will try to get hold of CRT monitors
I would have loved to use actual hardware but old hardware can fail, I can’t repair it myself though would be interesting to change a couple transistors I guess.
New hardware is crazy expensive though tha AgonLight2 board is pretty cheap and I am surprised it is not out of stock. Maybe I try that and put that in to theC64 case if I can. It is not Commodore but I did want to have an authentic retro case and now I have, maybe I’m going to play with different boards if I can.
For now I stick with theC64 board though. Apart from this little glitch, it works fine for the most part.