size limit on imported models

(Machine for to kill) #1

Is there a size limit (dimension wise) on imported models for radiant (.md3 models). I’m trying to put in this model and when I scale it beyond a certain limit it starts to fold onto itself.

(kat) #2

yes, it’s basically a box 1024x1024 (512 in any direction from the point of origin centerpoint). If any part of the model goes out of those bounds the vertexes get folded back on themselves. You may need center the model in dead center of mass rather than trying to center it on it’s baseline (where it touches the ground)

(Fluffy_gIMp) #3

I assume you are talking about scaling in the 3d package it was created in? As Kat rightly points out there are restrictions to the md3 format that constrain the size of models you can export, however you can scale the model up in Radiant without any problems.

-Fluffy_gIMp

(Machine for to kill) #4

Yeah it’s a 3ds max model so that’s where I’m scaling it. I tried scaling it with radian but it didn’t do anything. The scaling had no effect. Maybe the scaling does not show on the editor? I’m gonna try that again see if it works.

Thanks to the people that replied.

Now I have a new question, is there a limit on size for ase models as well, and does using very large imported models (both ase and md3) reduce performance for the map.

(Machine for to kill) #5

Ok I figured out how to use the radiant scaling properly. Before I was using the selection menu scaling and wasn’t doing anything but then I tried the entities menu scale command and that one worked fine.

I still want to know though if using very large .ase and .md3 models has a negative effect on map performance. I mean what’s stopping me from making the whole map in 3d max and then just exporting it.

(kat) #6

large models have the oposite effect on performance… but it depends if you have any wierd shaders covering the models. I just use ASE models in my SP map to get around the weapons_flash bug, works quite well…!

I read somewhere that ydnar said if an ASE model is over 1000 verts it need to have a shader with certain parameters in it by default

q3map_forceMeta
q3map_shadeangle 120 (recommended value)
q3map_??? - can’t remember this one I think it was ‘nonplanar’ not sure though