Some strange unit problems.

[Subdivision]

Good evening all,

I just downloaded the 3Dsmax 2012 trial and decided to fiddle with it for a while. I haven't done major changes to it's settings so that should be fine and all, then I compile the .qc with WallWorm's tools (so not the model, only the .qc)

I create a file named compile.bat with this in it

Code: Select all

"%sourcesdk%/bin/orangebox/bin/studiomdl" -nop4 %1
pause

because otherwise it will give errors complaining about write permission. This proces goes just fine.
Then after placing all the files in the proper folders for SDK and EP2, I open Hammer to place the model.

Here is where shit goes wrong.
After placing the model in my map, I took a good look around but didn't see the model. It turned out to be 20 000 x 20 000 units big.

So the problem is, I use regular, generic units for 3DSmax, but it get's rather large after compiling.
I asked a friend about this, he says he uses the exact same file to compile the model but it doesn't give such big models when he tests them.

Does anyone have a slightest clue about what's going on here?

Edit:
I think it will be also be helpful to state that, 1 generic unit equals 1 inch. (even with centimeters, still no result)

[Sathor]

Just a guess ... should your model be 20x20 units big? 20,000 or 20.000 ... can make a big difference, depending on what the program uses?

20,000 in European terms would mean 20, while 20.000 in European terms would mean 20k ...
Just a guess though, might be completely wrong assumption.

[Subdivision]

The object is 50x50 generic units big in the editor, so in my case, 1 unit equals 1 inch as said. So it had to be 50x 50 inch large. And since 1 Hammer unit = 1 inch as well, it should correspond.

Edit
Bloody hell, you're right. I triple checked everything but your reaction made it clear. My buddy has set it on 1.0 inch and I have set it on 1,0 inch.

Big thanks for this one!!

So, right I figured out the main cause thanks to Sathor ( ) but the program tends to set the value back to 1,0 when I change it from 1,0 to 1.0 Any way to prevent 3dsmax from doing this?

Unbelievable that such small mistakes can end up in such big things (literally)