Theoretically: no.

If you compile with BSP tree, your map should have the same visibility tree as if it would be smaller (it doesnt depend on the view frustrum during pre-calculation). Clipping: this is dynamically adjustable, so you could increase/decrease the standard values to make it fit with your measurement.

it depends on the quality of the specific level, and in the required amount of detail, by default I use 64, but sometimes 128

It really depends what kind of game I'm trying to make. Scales are quite different in certain genres, like RTS games for example. It would be quite foolish to take 32quants as 1m for a RTS game (unless you want to be able to zoom in and have FPS quality, and unfortunately zoom out and have zero fps ).

I think 32q = 1m is a pretty good standard.

Cheers

If I make a 3D tetris game, I dont look at the scale at all.
If I make a FPS, I just create the level from models, taking the average c-babe-, warlock- and guard.mdl size as a reference for the height and scale of objects.
If I make a RTS, I do the same with smaller models (aprox. half the size of CBabe).

I never looked at the scales, but I was aware of it. But the 0.75 Cbabe / Meter is not in the poll so I choosed 32 Quants / Meter . I think most of the time I took the 32 Quants / Meter scale, though without actualy using it.

Since my levels are built out of models, I just load the main character model(vehicle) into the level, and build around that. Once your done the basic floor plan, then you build the walls and so on... Just keep things relative to how big your main model is, and how fast your code moves that entity.

I have to agree with the last few. I allways just load my player, then build around that. But I do see the importance of meter/quant scale now. I used to just test it constantly to find out which speed to move the player and AI seems best. Although I guess I've been quite lucky, because i've never really had to resize anything, except my textures.

Its quiet suprising (for me) that most repliers in this thread are using that "lets see how big it is"-method as well as most voters take 32 quants as one meter.

Whatever, I will take then 32 quants per meters as default setting if the user doesnt change it manually.

Cheers and thank you,
Christian

I am confused by the measurement system used in 3D Game Studio. I found out that a 3D character like Hero or Inmate is about four small square units high. A man is about six feet tall. If I'm creating levels based on real-life buildings, cities, etc, how do I convert 3DGS units to feet or meters?

Stick with the advise in manual.

Quote:

---

How much inches a quant shall be depends on the relative size of the models. We recommend one inch per quant for person based games (shooters or adventures), and 4 inches per quant for vehicle based games (war games or flight simulators).

---

For instance, the length of M1 tank is 32 ft, which is 384 inches. 384 / 4 = 96 quants. (Edited)

And in MED I found it is 4 quants per small square.