Posted: 25th Feb 2004 11:35
Instead of using for-next to load the same model, it is much faster to make a mesh from the object then make objects from that mesh. By putting the object into memory (I think that's how make mesh from object works) you could save time from having to read the object data from the disk again. l337
Posted: 26th Feb 2004 1:18
Now imagine you have a model that use multiple textures you have something like texture1.bmp texture2.bmp etc and when you load the model in dbp he automatic will load the texures without needing to do the "load image" and you dont want to make a image with all the textures inside how you gone do this with mesh command is that possible ?
Posted: 26th Feb 2004 6:01
Sorry, I'm dbc. I'm not sure if dbpro's mesh command will create a white model or a textured model, but I suppose you could try removing load image and maybe replace make object i,1,1 with make object i,1 and see if it also loads the texture.
Posted: 26th Feb 2004 14:37
Yes, it's a good thing to know. Just remember you will lose any animations.