Disspearing models

[Kithraya]

Hey.

I have a problem with some models. When I set camera in a determined angle or i make zoom, model disappears. What to do to get rid of this?

 

[asdfADRiAN]

Two reasons:

1. That is because either the camera is inside the mesh and shows it as invisible there for you have to zoom out a bit Or
2. The mesh or texture is not double sided. To fix this go to Material Manager, then select the appropriate material set and make sure that the material for that particular texture is set to Double-Sided by ticking the check box. This can be done in War3Model Editor as shown in the screenshot below.

Hope it helps!

 

[-Grendel]

hm, which model is it man?

 

[Nasrudin]

If the models are disappearing only partially it might be as Atmosferic said, just the camera clipping with them.
If, however, they are disappearing as a whole on certain camera angles, then it's more likely that their displaying bonds are simply too small.
Open the model with Magos and go to Edit -> Model Properties and increase Minimum and Maximum extent. Ideally you'd better check the coordinates for each axis in a modeling program, but if you wish a quick fix and are not worried about performance, just double the values, save and test ingame.

 

[Rao Dao Zao]

If the models are disappearing only partially it might be as Atmosferic said, just the camera clipping with them.
If, however, they are disappearing as a whole on certain camera angles, then it's more likely that their displaying bonds are simply too small.
Open the model with Magos and go to Edit -> Model Properties and increase Minimum and Maximum extent. Ideally you'd better check the coordinates for each axis in a modeling program, but if you wish a quick fix and are not worried about performance, just double the values, save and test ingame.

To add to this -- don't forget to also increase the BoundsRadius value!

 

[Kithraya]

It works! Minimum and Maximum extent was set to 0 everywhere. I copied correct extent from other model. Thanks.

 

[Nasrudin]

Mmm. Really weird that they were set to 0. I'm glad it works now, but note that if you don't adapt the extents to the actual geometry, you may still encounter this kind of error.
If you have downloaded the model from this site, please leave a comment to the author, so he might get it fixed.

 

[Kithraya]

No, this model was from Turbosquid. Hmn... i must fix something more, because sometimes, when I rotaing camara panned on this model, get Wc3 crashed. ;/ But this not happen always. From time to time.
I have never before anything like this. ;/

 

[anarchianbedlam]

for next time, just open your model in magos, and go to "EDIT>Calculate Extents" so you dont have to copypaste random numbers from other models. Magos will do it automatically for you.

 

[Deolrin]

...Yes, yes it will, but in the event that you have a stray vertex hanging high above the model, the only solution is to take the Z extent and lower it by ~10-30.

 

[Nasrudin]

Magos is not really accurate either, used it many times for a quick fix, and more often than not it makes extents too small.

 

[anarchianbedlam]

...Yes, yes it will, but in the event that you have a stray vertex hanging high above the model, the only solution is to take the Z extent and lower it by ~10-30.

i guess that would only happen if you fucked up your geo-edit. for most models though, you wouldnt worry about that.

 

[Rao Dao Zao]

Magos is not really accurate either, used it many times for a quick fix, and more often than not it makes extents too small.

Magos' only calculates the extents on the static geometry -- when animated, most models obviously tend to exceed their initial bounds. The best way to force it in this instance is to add a dummy bounding box that always encompasses your model and delete it after recalculation.

...Yes, yes it will, but in the event that you have a stray vertex hanging high above the model, the only solution is to take the Z extent and lower it by ~10-30.

i guess that would only happen if you fucked up your geo-edit. for most models though, you wouldnt worry about that.

I would go so far as to say that's a stupidly rare occurrence that's not even worth mentioning. Anyway, you'd delete the vertex and recalculate, not fanny around.

 

[Nasrudin]

Magos' only calculates the extents on the static geometry -- when animated, most models obviously tend to exceed their initial bounds.

Apart from that, I've had issues with static models too. Had to extend the bonds manually by a lot to fix it.