123
-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0|291|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Blitz -> loadmesh vs copyentity
Wed, 26 Mar 2008, 13:52
Orion Pax
 		Ok, once I have my models loaded and need to duplicate them, which would be better to use? Should I just reload the mesh everytime or just use copyentity?
Wed, 26 Mar 2008, 13:58
Forklift_Fred
 		I would say copy entity is quicker because, at the very least, it doesn't require any disk access.

There may be other reasons but that's the one that springs to mind.

-=-=-
Come rain or shine...
Wed, 26 Mar 2008, 14:16
zebeste
 		Thats one, another is that copyentity creates a new instance of the mesh, not a new mesh. This means that the geoemtry data is only stored once in memory and all instances point to it.
Wed, 26 Mar 2008, 15:19
Orion Pax
 		so it is quicker and saves on memory. Sweet. Thats what I thought but I had seen some samples of some high profile peeps related to blitz that kept loading the same mesh. Didnt look right to me...thanks!
Wed, 26 Mar 2008, 16:21
GoliX
 		I think if you want to be able to deform the meshes individually(ie. damage to individual buildings) then use CopyMesh instead of CopyEntity, but generally if your having lots of the same model that aren't going to change then CopyEntity is better.

Also if you're using bone animations then make sure you get the model the right size in your modeling program first because scaling in blitz doesn't scale the bones with the mesh(at least not for me) resulting in all sorts of weird things.

I've tried scaling the root bone but then commands like MeshHeight etc stop returning the proper values. :/