Denial

Hey, it's all good - nobody gets born knowing the ASCII character set.

There will be a test at the end of the thread, however.

Are you saying that you store 96 into a screen RAM location, but when you read it back it's 32? This actually sounds like a memory chip fault. What happens if you store 64 there? Do you get 64 back, or zero? And if you store 128, do you get that back or something else? EDIT: oh wait - are you saying...

Hmm, not quite getting your point on this - 32 is the standard ASCII code for a space, which is reflected accurately in PETSCII. 160 is a 'shifted' space (also known as an inverse space) and 224 is a 'Commodore' space (i.e. space pressed whilst holding the C= key). These two are PETSCII-specific. I'...

What was the reason for not using the latest stable release anyway? If it was something quite fundamental to the way the project works, it's a decision between switching and reworking to overcome that defecit, or sticking with the release you're on and writing this subroutine in assembly. Which woul...

Yes, that's true - my thinking is coloured slightly at the moment because I'm working on a new process for establishing a cycle-exact stable raster. I'm coming at it from the point of view of needing to know exactly how many cycles of the current instruction (anywhere from zero to seven) still have ...

Hmm. Presumably the cart sets the VIA timer to different values though, to accommodate the variability of instruction lengths? Since the CPU will not interrupt the currently-executing instruction if it has just one or two cycles left, the cart would have to be doing an in-place disassemble-and-emula...

I've often thought that Microsoft really missed a trick when they decided not to implement the POKE command in the version of BASIC they licensed to Commodore. Can you imagine how much easier it would have been to set memory locations to any given value if there'd been a way to do it without having ...

I was thinking that too. I also wondered whether any of these extended graphics mode are making use of undocumented opcodes in general? I know I've benefitted significantly from the use of LAX, SAX, SLO/ASO amongst others in VIC++ particularly to maximise screen update speed in the 40x25 display log...

Genuinely impressive. Looking forward to seeing where this goes next.

Nobody else over at the 6502.org forums then?

I like this - it's a much slicker solution than posting re-pasted links in threads with downloads in. Good work!

Just do your own thing. Use whatever tools you want, however you want, with whatever VIC configuration you want. Be creative. Have fun. Don't let anyone tell you their way is the only way, the best way, or that if you're not doing it their way you're wrong, or doing it wrong. Remember the mantra: Th...

I'd certainly be interested in seeing THAT routine.

KingTrode wrote:I even managed to revamp my 40 column code a bit and get it drawing a full 40x24 screen with 24 Locates in approx 0.26 secs

I can beat that. 40x25 in 0.18...

There's only one way to settle this - FIGHT! (that'll only be funny if you're a Harry Hill fan)

Oh, welcome back btw!

Gets my vote.