|
Hmmm... I don't remember having a translator prefs tool or accents - are you sure you're not using some replacement voice synthesis library that needs extra stuff?
As for the blitting, it could be your code, it could be the size or complexity of the blits, or it could simply be the bandwidth of the A1200 leaving more time free for the blitter each frame. First thing to check though: are you running it from the editor with the debugger on? This eats up a lot of CPU time, and turning it off lets the code run at full speed.
Blitting shouldn't really be that slow, and 18 blits isn't a lot if they're moderately sized. If they're large blits however (in pixel count or depth), they take more time.
And sprites can indeed be animated, and you're right that GetaSprite shouldn't be used in this way, it's very slow. What you need to remember is that you have sprite objects (the graphical information) and sprite channels (the hardware used to display the sprites). You only have 8 hardware sprite channels, but you can have as many sprite objects as you want created in advance. You animate by creating a separate sprite object for each frame, then when you want to show a different frame, simply use the desired sprite object corresponding to the new frame in the same sprite object, and it will instantly replace the old frame. This is pretty similar to blitting different shapes as needed to create animation. having black borders around the sprite is possibly as simple as using the incorrect palette registers - sprites use particular colour registers and you need to take that into account when creating them. Colour 0 is always transparent though, so if colour 0 areas are showing up as black, there's something else going on.
Here's a little demo of using sprites in Blitz that I made for the upcoming Blitz tutorial in Amiga Future, to give you an idea of their capabilities:
[ Show youtube player ]
It's AGA, but the principles are the same other than limiting the size and palette.
|