>I have 6 sprites per line left, and 20 in total (others are for border
>cloacking). Only BUT is that only very few 'fences' per screen can be
>created. And it requires some extra calculations. But it is indeed a good
>idea, since it doesn't need extra (slow) copying.
wasting 2 sprites for borders indicated you want to smooth scroll.. WHY
smooth scroll ! sd-sn didn't too .. does sd-sn. suck ? :)
You waste lotsa vdp speed with this, better use 8x8 'scroll' and have more
vdp power left for characters running around.. etc.
By the way, would somebody have objections against an engine based on 16x16
>tiles??? (that would make my engine faster and I then won't have to make a
>nifty workaround for the current speed problem I have).
a top-view game like Bastard could be 16x16.. a bird-view rpg is better
when using 8x8... more detailed editing.. (less gfx in ram too).
\/\/
Maarten van Strien,
* composer
* sounddesigner
* Ixalance-sound developer
-----------------------------------------------------
http://www.shortcut.nl/
mailto:[EMAIL PROTECTED]
-----------------------------------------------------
Shortcut Software Development B.V.
Julianaweg 9, 3603 AP Maarssen, The Netherlands.
Phone: ++31 (0) 346 579 659
Fax: ++31 (0) 346 579 745
-----------------------------------------------------
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED]
and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in
the body (not the subject) of the message.
Problems? contact [EMAIL PROTECTED]
More information on MSX can be found in the following places:
The MSX faq: http://www.faq.msxnet.org/
The MSX newsgroup: comp.sys.msx
The MSX IRC channel: #MSX on Undernet
****
