Thomas Jentzsch

I don't do bB, sorry. But maybe someone else can help?

It interferes with the paddle controllers.

Digitized music might work too. Or is the frequency too low?

Unplug it.

The latest release candidate is obviously the final version.

I meant to use "R{1}L0x_BIT0_" here. Which does only use bit 1, no? I did a brief test and it seems to work and I got 5 free cycles which could be used to change e.g. the background color every 2nd line. Have you managed to replace "ldx #ENAM0, txs" with PLA? BTW: I am using the following colors: COL_BACKGROUND = COL_82 COL_HIGHLIGHT_BK = COL_86 COL_TEXT = COL_18 ; yellow as complementary color COL_HIGHLIGHT_TEXT = COL_1E ; or COL_AE if you want some color here

Why not for "sta.w ENAM0" in KERNEL_2 too? X is LEFT74_8 from KERNEL_1, so you only have to make sure at the beginning of KERNEL_B. But reusing X from KERNEL_1 could save even more. "ldx #LEFT74_8" would become e.g. "ldx #LEFT74_8 | {10}". You would have to modify the two ,X offsets accordingly. And then you do not have to "lda #{11}" in KERNEL_2 and can replace that with a NOP. And finally do "stx ENAM0" and "sta GRP0 - (LEFT74_8 | {11}),X" to save a byte. And maybe the two extra free cycles allow more? There are 2+3 = 5 in total now, enough for changing a TIA register.

Sorry, I lost track.

Who should have paid the VAT which is owed to the target country?

For a short term (or special niches like Atari retro games) you are right. But if the USA should continue to violate international trade rules, it would help the video game industry in Europe. And maybe even AtariAge might be tempted to move some production to someone in Europe eventually.

PHA should work here. And a brief test showed no problems.

Definitely. Even more after your post.

Sure. lda moveSum clc adc #SPEED ; e.g. 128 for 50% or 192 for 75% speed sta moveSum bcc .skipMove jsr MoveJoystick .skipMove

No idea. It is something which currently is not emulated by Stella. And I cannot identify where the wrong top and bottom pixel come from. Maybe, if you post more scores we can identify a pattern.

There are at least two methods: In case you have a frame counter, execute MoveJoystick only every 2nd frame. Use fractional numbers. For that you need a sum variable and a constant added to it each frame. Only call MoveJoystick when the sum variable wraps around. The latter is more flexible as you can fine tune the speed very gradually.

There seems to be a timing issue with your console (left side of rightmost score digit).

How long can you pretend working on a huge backlog?

Yes, color mixing with non black backgrounds requires some extra thought. But you could e.g. use a complimentary color for non-highlighted entries resulting into a (more or less) gray font display. And a bright color with a hue close to the background for a highlighted, colored font. Anyway, changing the background color is the better option. But for that the late HMOVE would have to be moved. @Omegamatrix is that feasible?

Not sure why changing text color would be impossible on-the-fly, it is read from RAM. The background color is a problem because not all HMOVE blanks invisible. Not sure if this can be fixed.

VAT exists globally (116 countries) with a few exceptions (USA, some Arabian and African States...). So when shipping from the USA e.g. to Canada or Mexico you have to pay VAT there. When shipping between two VAT countries, the VAT of the original country gets refunded (or not claimed) and you have to pay VAT in the target state.

Have you thought about outsourcing some production to someone in the EU?

Cool stuff. Thanks for sharing too.

The same what you would do with NTSC or PAL carts. Or maybe split the Brazilian carts into a separate collection.

But to be consistent, you would have to remove all existing Brazilian titles, no? 😃

If you are testing, please use the latest 6.5.1 R77 release (Mr. Paddles). It might have improved other controllers too.