Commander X16

Hi. I'm really liking the cases. Much prefer the white case over the black one. The thing that stands out to me is the clear top. That looks really classy showing the CX16 Board, which itself looks great. Much prefer the look of these cases over the CX16 console style case too. Not to keen on the dr...

Looks like a really useful tool.

Thankyou.

I really like that.

Gives me sort of fractal planet vibes.

Pity about the render speed, even in warp mode.

Amazing what can be achieved in just a few lines of code.

Update 20.03.23 ------------------- I've reposted my irq keyboard routines as the first version contained some errors. It turns out several keys share the same scancode, which i was unaware of and the result was that some keys were getting tested and others not. The reposted code now also has an ear...

Thanks for the heads up Yazwho.

I'll keep my eye on that.




Thankyou DragWx.

Great info.

I was unaware of.

I'll get to work amending my code.

For future reference. I've been double checking my code and found an error. There are 94 entries instead of 96 and i have removed the $9f27 section. As it seems as though it's not needed. key_loop_3 inx cpx #94 ; 94 entries instead of instead of 96 bne key_loop_2 And amended the code. I also found a...

As i understand it, they keyboard generates an irq whenever a key is pressed or released, regardless of whether raster irq's are enabled or not, or triggered. There are 2 software vectors i use, one for normal irq's ( raster irq) the other for keyboard irqs. I'm guessing the kernal irq routines dete...

Here is my normal IRQ handler vector. vector $0314 - $0315 Here is the keyboard irq vector $032e - $032f Both different. I have both irq's triggering. i'm not sure if lda $9f27 ; ( Only Working In Windowed Mode ) and #1 beq is actually needed in the keyboard handler. Incidentally, i can only read a ...

Ahh i didnt realise you were using C. I was using the VBCC compiler recently and had to drop it because it was just using up far too much memory. Out of curiosity which C Compiler are you using ? I would suggest putting the array and variables into specific memory locations, 1024 - 2023 is 1k of fre...

That looks great.

Very reminiscent of the real arcade cabinet joysticks i used to use.