GetChild bug?

[Thareh]

Hi!

I'm doing a lil' loop to go through all the children for my loaded Mesh like this:

 

For local X:Int = 1 to CountChildren( Mesh )
   Local Child:TEntity = GetChild( Mesh, X )
   Print GetEntityKey( Child, "name" )
Next

 

And this throws an error like this: "List index out of range".

Am I doing something wrong or is this a bug?

[Marleys Ghost]

For Local X:Int = 1 To CountChildren( scene )
   Local Child:TEntity = GetChild( scene, X )
   Print GetEntityKey( Child, "name" )
Next

 

 

Works for me in Bmax with a loaded scene.

[Thareh]

I'm using it on a mesh, and it seems to be very random.

Sometimes when I export my mesh I get this problem, sometimes not.

[Canardia]

If it works with the same mesh all the time, and it never works with a mesh with never works, then it's probably not a bug in the engine, but in the way how you export or in the modelling program you use.

[Thareh]

I'm modifying the same mesh, and exporting it again etc.

I can load the mesh just fine, and it shows up just fine;

But as soon as I loop through the children it crashes with that error.

Shouldn't CountChildren() just not count the parts that isn't correct if my mesh is faulty?

I'm exporting it using the 3d studio max exporter in the downloads section.

[Canardia]

There might be a difference when you export it after you first opened 3DS Max, and when you export it a 2nd time while 3DS Max is still open (some internal variables being set differently). You could try if it works always when you close 3DS Max, open 3DSMax, then export it, and close 3DS Max again.

[Guest Red Ocktober]

try limiting your loop to CountChildren( scene )-1

 

i just put the same code into a scene and looped to -1 less than the child count and it showed the exact same children with an key named "name" as if i wound it out to the full count...

 

this may solve your problem... maybe...

 

 

--Mike

[Thareh]

I've tried that, It works sometimes

I'm gonna try exporting with a freshly started 3d Studio Max.

[Thareh]

I tried exporting it with a freshly started 3d studio max, still the same issue.

Even if it's my meshes fault, shouldn't CountChildren & GrabChild skip invalid parts of the mesh?

The mesh shows up fine on the modelviewer, with the names of all entities etc.

So how does the modelviewer loop through all the children?

[Canardia]

Maybe ModelViewer skips illegal pointers, kinda like this:

For local X:Int = 1 to CountChildren( Mesh )
Local Child:TEntity = GetChild( Mesh, X )
If Child Then
	Print GetEntityKey( Child, "name" )
EndIf
Next

[Thareh]

Can't do that, It errors at the line with GetChild :/

It's not a null pointer issue ^^

[Josh]

Post an example we can reproduce.

[Thareh]

Found the issue now, I'm freeing a child in this loop which makes the CountChildren count go down so that GetChild goes short

There isn't any easier way to move an entity to another world other than change world => copy it => remove the original => change world back; right?

[Josh]

Possibly, but I don't feel comfortable right now with the bugs that might raise.

[Thareh]

Perhaps you should make a new command; SetEntityWorld ^^