KuRiX,
Ross C does a good job explaining the need for Single Surface Sprites. I haven't seen 'Single Surface' mentioned in other game dev forums so I suspects its specific to Blitz3D.
There is a great deal more work that needs to be done with Single Surface 'Sprites' when one considers Single Texture Image Sets, Pixel Perfect Resolution, Transformation, and Collision. You have to code this functionality. I have a good discussion going here to unlock its mysteries.
Coding the functionality I mentioned above can be tricky and there are several Single Surface Libraries that can make your life easier. After playing with several, I decided to give a crack at my own. I'm writing a open source single surface lib.
One of my first goals with the lib is create a 3D command set to replace Blitz3D's 2D Image, Graphics Drawing, and Collision commands. This will allow folks to transform there 2D games into 3D with relatively small fuss.
Ross C does a good job explaining the need for Single Surface Sprites. I haven't seen 'Single Surface' mentioned in other game dev forums so I suspects its specific to Blitz3D.
There is a great deal more work that needs to be done with Single Surface 'Sprites' when one considers Single Texture Image Sets, Pixel Perfect Resolution, Transformation, and Collision. You have to code this functionality. I have a good discussion going here to unlock its mysteries.
Coding the functionality I mentioned above can be tricky and there are several Single Surface Libraries that can make your life easier. After playing with several, I decided to give a crack at my own. I'm writing a open source single surface lib.
One of my first goals with the lib is create a 3D command set to replace Blitz3D's 2D Image, Graphics Drawing, and Collision commands. This will allow folks to transform there 2D games into 3D with relatively small fuss.