loading multiple objects; much faster than using for-next

developer forums

Code Snippets / loading multiple objects; much faster than using for-next

Author

Message

Arkheii

Years of Service

User Offline

Joined: 15th Jun 2003

Location: QC, Philippines

Posted: 25th Feb 2004 11:35

Link

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

Profile PM

Marvey

Years of Service

User Offline

Joined: 15th Oct 2002

Location:

Posted: 26th Feb 2004 01:18

Link

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 ?

Profile PM

Arkheii

Years of Service

User Offline

Joined: 15th Jun 2003

Location: QC, Philippines

Posted: 26th Feb 2004 06:01

Link

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.

Profile PM