Quote:
Originally Posted by Toni Wilen
Done
What do you mean? Why is there any need to mask cycles that don't exist?  |
After executing v -5 / vm 0 0 / vm 1 0 / ... / vm 8 0, I expected the screen to look normal (only interrupt level overlay visible) instead every other vertical line is black, there also seems to be some other "miscoloring" which looked like they might correspond to when DMA is IDLE (which is why I guessed at that as the cause).
See attached screenshots (apart from the black lines there's also a distinct pattern noticeable). Mode is 5 and "vm" reports the following:
Quote:
0,0: 00222222 -
1,0: 00444444 Refresh
1,1: 00444444 Refresh
1,2: 00444444 Refresh
1,3: 00444444 Refresh
2,0: 00a25342 CPU
2,1: 00ad98d6 CPU
3,0: 00eeee00 Copper
3,1: 00aaaa22 Copper
3,2: 00666644 Copper
4,0: 00ff0000 Audio
4,1: 00ff0000 Audio
4,2: 00ff0000 Audio
4,3: 00ff0000 Audio
5,0: 00008888 Blitter
5,1: 000088ff Blitter
6,0: 000000ff Bitplane
6,1: 000000ff Bitplane
6,2: 000000ff Bitplane
6,3: 000000ff Bitplane
6,4: 000000ff Bitplane
6,5: 000000ff Bitplane
6,6: 000000ff Bitplane
6,7: 000000ff Bitplane
7,0: 00ff00ff Sprite
7,1: 00ff00ff Sprite
7,2: 00ff00ff Sprite
7,3: 00ff00ff Sprite
7,4: 00ff00ff Sprite
7,5: 00ff00ff Sprite
7,6: 00ff00ff Sprite
7,7: 00ff00ff Sprite
8,0: 00ffffff Disk
8,1: 00ffffff Disk
8,2: 00ffffff Disk
|
Quote:
Originally Posted by Toni Wilen
Tall modes moved to top of screen but you still lose some lines.
|
Quote:
Originally Posted by Toni Wilen
It is only done when/if new parameters are finished enough.
|
Totally understandable, just mentioning it for completeness.
Also I just noticed a small annoyances with the debugger (Perhaps I should open another request thread?): When pressing shift+f12 with the debugger window already open, it'd be nice if it (the debugger window) was activated.