Game Scale?

[Ardy123]

What is the 'Scale' of the game, ie 1 pixel and a depth of 0 (origin) represents a 3d block of what size? (1meter, 1cm)?

[Karnak]

Polygons don't work that way.  Only thing I can think of that might is voxels.

[Ardy123]

Polygons don't work that way.  Only thing I can think of that might is voxels.

You are right, pixels is not a good example, I should have asked how does the coordinate space equate to real life measurements but I think you knew that.

ie,
in real world measurements, what does a line segment from <1,0,0> to <2,0,0> measure too?

[Easyscor]

The in-game sector grid is laid out on 25 miles centers. So starting at one sector line and moving to the next will traverse 25 miles. Often you'll see + marks within each sector, those are roughly 8 miles apart.

Your pixel "size" will vary depending on the terrain size because the clipboard map (CBM) has always been 1024 x 1024.

I think both the wiki and the help files cover this.

Oh, and in the terrains based on real life, the terrain builder my vary the scale to compress the time it takes to travel the distances need for a special event.

[Karnak]

You are right, pixels is not a good example, I should have asked how does the coordinate space equate to real life measurements but I think you knew that.

Actually, I hadn't correctly inferred what you were asking.  I'd have given more information if I had rather than what would have been just a snarky answer, had I known.

[BaldEagl]

ie,
in real world measurements, what does a line segment from <1,0,0> to <2,0,0> measure too?

That would be totally dependant on it's distance from you.

[Ardy123]

Your pixel "size" will vary depending on the terrain size because the clipboard map (CBM) has always been 1024 x 1024.

pretend I never said pixel... so each integer increment in 3d space along any axis is 1024/25miles so 1 unit - 4.16 miles?

Say if one was to make a model, to accurately represent 30 ft between two vertices would be a distance ~0.0003283245 units?

[Easyscor]

pretend I never said pixel... so each integer increment in 3d space along any axis is 1024/25miles so 1 unit - 4.16 miles?

Say if one was to make a model, to accurately represent 30 ft between two vertices would be a distance ~0.0003283245 units?

No, not really, but I'm not sure I understand the question.

Both the Terrain Editor and the Object Editor use feet as their unit of measure. To understand what happens to the CBM, you must realize that all terrains use a square array of 1024 vert per side, 512 x 512 miles. The CBM on the other hand, while a constant width and height, may only show a fraction of the area in the terrain. A 256 mile CBM is only showing the center portion of the underlying 512 terrain.

If you're trying to determine the distance between two points in the terrain based on the CBM, then you can determine this by knowing that each sector on all CBMs is 25 miles.

If you're considering building a 3D shape to include in the game, you can, and you'll use feet as the unit of measure, but you must use ac3d or a program capable of exporting to the ac3d format. The Object Editor only imports and converts ac3d files.

Hopefully that answers your question.

[Shuffler]

I know for a fact that when a tree fills your screen.... duck then enjoy your coffeee while in the tower.

^^^
First hand informarion.....

[2bighorn]

What is the 'Scale' of the game, ie 1 pixel and a depth of 0 (origin) represents a 3d block of what size? (1meter, 1cm)?


pretend I never said pixel... so each integer increment in 3d space along any axis is 1024/25miles so 1 unit - 4.16 miles?

Say if one was to make a model, to accurately represent 30 ft between two vertices would be a distance ~0.0003283245 units?

I could imagine they scale it so that textures looks pretty enough and aren't too pixelated -> plane, vehicle skins.

Plane length vs skin pixel length would be a good starter. On the other hand AH uses few diff sizes, so you'd have to figure out for which one the scale is optimized.

[hitech]

Ardy there is no integer size, all is done with floating point.

Your question really doesn't make any sense. You may be trying to ask something different.

Are you asking what is the basic unit of AH? If so we work in feet. But the units are really quite irreverent as long as all sizes are of the same scales.

When it comes to 3d graphics , there really is no concept of size until things end up on the screen, and then the screen size along with how far your head is from the screen determines sizes.

If you are asking about textures, that is also not really a scale. It changes constantly, each texture has multiple sizes via power of 2, I.E. a image will be stored at 2048,1024,512,256 ....  it's called Mip Mapping. Which image is used is determent by the current screen size of the poly being displayed.

HiTech

[Vudu15]

Here I got ya, yall are thinking to hard.

http://www.youtube.com/watch?v=eWM2joNb9NE

[wil3ur]

Where's the fat girl?

Here I got ya, yall are thinking to hard.

http://www.youtube.com/watch?v=eWM2joNb9NE

[Ardy123]

Ardy there is no integer size, all is done with floating point.

No I understand that the it uses floating point. Maybe if I try and explain it like this....

When objects get transformed to world space from object space, I am guessing they get scaled as well...

If I build a 3d box that was <10,10,10> units  in object space, (width, height, depth) and imported it into the game, how many square 'feet' would each surface represent in the game engine in world space? 100sqr feet?

When it comes to 3d graphics , there really is no concept of size until things end up on the screen, and then the screen size along with how far your head is from the screen determines sizes.

Arn't the verts getting translated into the canonical view volume in camera space (-1,-1,-1)-(1,1,1,), then getting scaled by the screen resolution?

I guess I should state my assumptions...

the graphics pipeline of this game is

[obj space] *(transform/scale/rotate)->[world space] *(transform/scale/rotate)->[camera space]*(projected/transform/scale/homoginize 4v4 mtrx)->[screen space]

[hitech]

No I understand that the it uses floating point. Maybe if I try and explain it like this....

When objects get transformed to world space from object space, I am guessing they get scaled as well...

If I build a 3d box that was <10,10,10> units  in object space, (width, height, depth) and imported it into the game, how many square 'feet' would each surface represent in the game engine in world space? 100sqr feet?
Arn't the verts getting translated into the canonical view volume in camera space (-1,-1,-1)-(1,1,1,), then getting scaled by the screen resolution?

I guess I should state my assumptions...

the graphics pipeline of this game is

[obj space] *(transform/scale/rotate)->[world space] *(transform/scale/rotate)->[camera space]*(projected/transform/scale/homoginize 4v4 mtrx)->[screen space]

As I said in my previous post our units are feet. So that would be a 100 sqr foot surface. But If i said it was meters , that box would display exactly the same when 10 units away. So hence the units have absolutely no bearing on anything except the preference of the designer.

When objects get transformed to world space from object space, I am guessing they get scaled as well...

Scaling is not normally done, scaling in graphics is only to change the size of objects relative to each other. When object are bigger or smaller on the screen it is do the the projection, not the scale.
Scaling really has nothing to do with units.

I am not trying to be obstinate, I just really do not understand what you wish to know.

HiTech