BMAX is 2d in 3d, each image is made up from a textured quad. If you have a large image then you are going to suffer from the same old fill-rate problem you would get with any game written in any language.
Things like blendmodes and rotation and scaling do not kill FPS, large images, large amounts of different images will kill FPS. You still have to play by the same rules you did with Blitz3d to keep FPS rates up. Keep the amount of surfaces to a minimum, BMAX will create a new surface for each image you load, try to pack many images into a single image as this will require only one surface to draw. Try to keep image(texture) sizes ^2, BMAX will resize if the image does not conform - hence major amounts of extra vidmem is used.
Conclusion: Treat the BMAX graphics engine like a Blitz3d single surface system.
Things like blendmodes and rotation and scaling do not kill FPS, large images, large amounts of different images will kill FPS. You still have to play by the same rules you did with Blitz3d to keep FPS rates up. Keep the amount of surfaces to a minimum, BMAX will create a new surface for each image you load, try to pack many images into a single image as this will require only one surface to draw. Try to keep image(texture) sizes ^2, BMAX will resize if the image does not conform - hence major amounts of extra vidmem is used.
Conclusion: Treat the BMAX graphics engine like a Blitz3d single surface system.