I have heard that it's a bad idea to use any 2D commands (such as plot or print) in a 3D application, because some 3D graphics cards have errors or slow down when they get fed 2D data. Coders have found clever ways to work around this, such as here, for example:
http://www.blitzbasic.com/codearcs/codearcs.php?code=1184
Anyway, I've noticed that there are some commands, such as Flip, that are listed under 2D commands in Blitz's command index, but are probabaly kosher to use in a 3D app, since there doesn't seem to be a 3D equivilent of the command.
So basically, what I'm asking is, is there a comprehensive list somewhere, of which commands in the Blitz language are 2D commands and thus need to be avoided?
I really, REALLY want my 3D app to run as fast as possible and to work on as many computers as possible. But I can't do this until I know which commands to avoid learning how to use, and which commands need a clever hacked implementation of 3D commands to replace them.
Thanks in advance for any helpful replies. :)
http://www.blitzbasic.com/codearcs/codearcs.php?code=1184
Anyway, I've noticed that there are some commands, such as Flip, that are listed under 2D commands in Blitz's command index, but are probabaly kosher to use in a 3D app, since there doesn't seem to be a 3D equivilent of the command.
So basically, what I'm asking is, is there a comprehensive list somewhere, of which commands in the Blitz language are 2D commands and thus need to be avoided?
I really, REALLY want my 3D app to run as fast as possible and to work on as many computers as possible. But I can't do this until I know which commands to avoid learning how to use, and which commands need a clever hacked implementation of 3D commands to replace them.
Thanks in advance for any helpful replies. :)