sometimes99er Posted December 7, 2010 Share Posted December 7, 2010 (edited) Now I will attempt to draw the entire viewport in the proper location. I will leave the border out for now... That's why I can't really pad the write data, because on the left and right of the viewport there will be a permanent border. Blasting 2 ">20's" on each side of the map data would blow out my border. This is one reason I had thought about doing individual maps as opposed to one BIG map and doing math to display the proper section... CALL LINK (MAP2) could have the entire border in the map data... that adds 160 or so extra bytes to each map though... With many of my demos, I have quick load and lots of memory, so I might very well have included the border in my map data. Two top and two bottom rows (of the border) wouldn't need to be in the map data. Moving 4 bytes to the VDP in between the rows of the viewport could certainly be done, and overall we would then "only" have to tell the VDP where to put the incoming byte once - instead of doing it 12 times (=height of viewport). I'm not sure we will save any time or memory - I think execution time would be about the same, and we would use some extra memory (storing and moving those 4 bytes). Edited December 7, 2010 by sometimes99er Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.