BASIC Vertical Scroller
Moderator: Moderators
- Mike
- Herr VC
- Posts: 4842
- Joined: Wed Dec 01, 2004 1:57 pm
- Location: Munich, Germany
- Occupation: electrical engineer
Sdw has done a proper full screen height vertical scroll as last part in his 'Ancient School' demo.
- Mike
- Herr VC
- Posts: 4842
- Joined: Wed Dec 01, 2004 1:57 pm
- Location: Munich, Germany
- Occupation: electrical engineer
That's no reason to be pissed off.
You're still free to write your own routine, analyse Sdw's demo, or ask him for the source. Or whatever.
As for the scroll routine itself, it is of course only a single 'effect', where there's possibly not much variation (except for the scroller/images contents) - and the resulting code will bear many similarities.
You're still free to write your own routine, analyse Sdw's demo, or ask him for the source. Or whatever.
As for the scroll routine itself, it is of course only a single 'effect', where there's possibly not much variation (except for the scroller/images contents) - and the resulting code will bear many similarities.
Thanks for that code MRaider, very nice, and thanks for keeping the hi-res out cause Mike still never told me how to get it running and blamed it on me, then blamed it on VICE for not being able to paste correctly, but even when i pasted line by line of the loader , the program still did not work. I asked for a working .prg but got nothing... no more posting minigraphik in my thread, thank you , But this is good stuff here, really informative, thanks!!
- Mike
- Herr VC
- Posts: 4842
- Joined: Wed Dec 01, 2004 1:57 pm
- Location: Munich, Germany
- Occupation: electrical engineer
You're lying.Legacy wrote:[...]I asked for a working .prg but got nothing...
I posted a link to a *.d64 file image of MINIGRAFIK, but you either didn't see it, or ignored it.
You're quite a bigmouth for just posting here a months worth. I really won't waste my time anymore discussing with you. PLONK.
Agreed!Schlowski wrote:Legacy, just look into a mirror then you will see whos fault this is. Or as someone told: The problem sits always in front of the screen.
The only one who is lame is you.
After review of the thread, (which had read previously) I found Mike to be providing clear and accurate details.
Last edited by 6502dude on Fri Feb 06, 2009 8:46 am, edited 1 time in total.
Mega-Cart: the ultimate cartridge for your Commodore Vic-20
Legacy is giving me strong Wildstar vibes, if you know what I mean.
MRaider: I think by POKE 36867,74 or even greater you get 37+ rows which is more than both PAL and NTSC screens will ever display. Then use double buffering like you already are considering, but instead of storing an additional bitmap you should be able to just store another copy of the screen matrix. While moving (scrolling) the screen eight pixels upwards, at the same time you copy its contents to the other display. Then you swap the two, and repeat the process. Even at 22x37 virtual characters it is only 814 bytes of data to move instead of a couple kilobytes. It however relies on the fact that you can define a screen area much greater than what you can see. In order to get this really smooth, I think machine code is in order.
MRaider: I think by POKE 36867,74 or even greater you get 37+ rows which is more than both PAL and NTSC screens will ever display. Then use double buffering like you already are considering, but instead of storing an additional bitmap you should be able to just store another copy of the screen matrix. While moving (scrolling) the screen eight pixels upwards, at the same time you copy its contents to the other display. Then you swap the two, and repeat the process. Even at 22x37 virtual characters it is only 814 bytes of data to move instead of a couple kilobytes. It however relies on the fact that you can define a screen area much greater than what you can see. In order to get this really smooth, I think machine code is in order.
Anders Carlsson