JSpeccy can play the games up to x10 faster, but it meets the Spectrum behaviour, one interrupt every 69888 (or 70908) t-states. Could be possible to generate one int every N frames, but not all games tolerate these behaviour.

ZEsarUX allows setting turbo modes, found on Next and zxuno, which increases t-states per frame. And also allows changing overall emulation speed, which affects all the emulator (also interrupts and sound frequency)

... normally runs in under 14K T states (roughly the time it takes ... CALLs (a 'main loop') wouldn't significantly suffer from these effects ... ; an occassional PUSH/POP woudln't hurt.

... />
11,751 x 6 T-states for INC BC instructions equates ... to around 70,500 T-states so that looks about right ...

... /> [/quote]

You don’t need to PUSH and POP ... ]. That way you save 21 T states per loop iteration.

t need to reset the position ... of the sprite. You won’t benefit from LDI when drawing ...

... /> However, some games that count T-States in order to maintain their ...

... to give 140k/280k/560k T-states per frame, instead of 70k ...

... /> However, some games that count T-States in order to maintain their ... if turbo mode means more T-states per frame, or more frequent ...

... fixed intervals of about 350 T states. Not a small feat by ...

... ;[7]
[/code]
19 T states vs. 24.

... sides too) where contention isn't an issue.[/quote]
I ... fluctuations up to about 12K T states, as well as maybe help ...

... .. that's interesting. I hadn't though of doing that. Does ... (give or take a few t-states) when I sync.

... .. that's interesting. I hadn't though of doing that. Does ... (give or take a few t-states) when I sync.

Good, but could be optimized a tiny bit to shave off 20 T states and 3 bytes:

[code]
ld (quit_sp+1),sp

...
...

quit_sp ld sp,0

[/code]

... bit to shave off 20 T states and 3 bytes:

... or may not correspond to T states at which these bytes are ...

... or may not correspond to T states at which these bytes are ...

... or may not correspond to T states at which these bytes are ... normal though). If it doesn't, well, too bad!

... border or the four #FF T states between each two bitmap/attribute ...

... +2A/+3 is displayed at T state 14365 and the contention ... border and the blank (#FF) T states. Odd how it repeats the ... on the actual hardware. Don’t know whom to believe anymore ...

... and the blank (#FF) T states. Odd how it repeats the ... the actual hardware. Don’t know whom to believe ... other, like a few T states maybe, but that's ... perhaps they just aren't referring to what I ... port reading and whatnot shouldn't be affected by contention ...

... .[/quote]
Ah, no. Can’t do that, because I’m ... bitmap bytes. At all. Counting T states seems to be an exercise ... (LD A,(0) [i]doesn’t[/i] work).

This ...

... rock solid. Sadly, I don't think this sort of magic ... ]

Different timing (25 T states vs. 21) yet it’s ... bitmap pattern), but it doesn’t. No contention, mind. I’ll ...

... have empty gaps of 100 T states (corresponding to the border at ...

... very different anyway. I don't see the need for this ... seen what is returned at T states 'before the screen' in Woody ... , but not my test (the T state listing part). If it ...

... into side border time (100 T states). You have a LD A ... time is reduced to 100 T states per line again, in turn ...

... border or during the four T states in between reading the two ...

... border or during the four T states in between reading the two ...

... the game (yes, those 28 t-states per screen update will really ...

I've managed to lose another 10880 t-states (a whopping 0.003 seconds!) from a complete build cycle by moving a few bytes around, but not managed to save any more bytes....not YET

Oh hang on...-1 byte, so now [b]725 bytes![/b]