|  Post Your Message | |
| |
| | Previous Messages | Posted By
Fuzzweed
on 2024-11-27
03:00:31
|  Re: Bad lines
Thankyou. This is the info I need. I will look at the link too, I haven't seen this yet it looks very useful
|
|
Posted By
gerliczer
on 2024-11-27
00:43:52
| Re: Bad lines
The CPU always does your stuff, so it is the TED which causes the badlines. Badlines are those where TED reads the character/colour map or the colour/luminance map. These are the last two lines of a character row and the last two before the topmost one. You can do splits in badlines but you must do it carefully. Have you studied the Ultimate Map, yet?
|
|
Posted By
Fuzzweed
on 2024-11-26
18:31:26
| Bad lines
So reading through here I think I understand a badline is where the CPU, or maybe ted is doing its own stuff, so you're short on cycles for your own use.
If I'm doing a raster screen split I assume I should make the split NOT on a bad line so I have most cycles available to run the interrupt handler to make a cleaner split.
So if my visible screen range is ~$04 to ~$CB how do I know which ones are 'safe' to use. Is there a list?
Or possibly I'm completely wrong about all of it....
|
|
| |
Copyright © Plus/4 World Team, 2001-2024. Support Plus/4 World on Patreon |
