> On 2020-05-30, at 14:40, tokafondo <tokafondo_at_gmail.com> wrote: > > Thanks for your email and having the time and patience to answer my > questions. Sure thing. It's also important for us to gather what are the thoughts/doubts about BeamRacer that come to people's minds, so that we can improve information available on the pages/docs. > The VIC will always draw pixels in the bitmap area, and as you said in the > border you will be able to put sprites but not actual bitmaps or > characters... unless they are also sprites themselves. Did I got it right > now? Side-borders yes, you got it right. When it comes to Upper/lower borders, they can now display both gfx (although not all modes) AND sprites :-) > And also, running at the same 8mhz clock speed (I > assume, or even more?) that the VIC-II runs, As the specification says - we do not do any modern "cheating" there. We use 100% pure, old-fashioned, CBM-grown clock frequencies, all of which were there since the dawn of C64 time :-)) > I imagine that the WAIT instructions are triggered by IRQs, aren't them? No. VASYL can trigger an IRQ https://docs.beamracer.net/doku.php?id=isa#irq but it doesn't have anything directly to do with WAIT instruction > Or are they raster line independient and there is an internal counter that > matches where the raster line is and acts accordingly? Exactly so. Since VASYL has all relevant clocks available, it "knows" exactly where VIC is drawing screen at any given cycle. > Saludos y cerveza. Gracias, y las dos para ti! ;-) -- SD!Received on 2020-05-30 18:00:03
Archive generated by hypermail 2.3.0.