Author Topic: initContainerBoxSearch units  (Read 1945 times)

What are the units for initContainerBoxSearch? They seem to be some strange thing like bounding boxes. For examples, 3 0.5 2, which should be the size of a 6x4 brick, seems to be some really huge thing like a 16x cube or something.


That topic does not specify what units it is in.

You could always calculate it by creating a 1x1x1 box and using bricks?

1x1 brick into torque units:
0.5 x 0.5 x 0.6

or 1x1F:
0.5 x 0.5 x 0.2

Looks like a simple case of too much Minecraft, the only game I know where Y is up and coordinates are routinely considered by players.

Looks like a simple case of too much Minecraft, the only game I know where Y is up and coordinates are routinely considered by players.
Y isn't height in Minecraft.


Yes it is, pain in the neck.
Well, technically Z shouldn't be height, should it?

It is a bit of a pain though, if you're used to Z being up.


But just remember the size of a plate in Torque units (0.5 0.5 0.2, as said above), and it'll be easier to determine the size.

ALTHOUGH if you do a search the same size as the brick, it'll also include the neighbouring bricks if you don't make the search a little smaller.

Well, technically Z shouldn't be height, should it?
What kind of crazy system has Z as not being height?

What kind of crazy system has Z as not being height?
Those crazy Swedes.

What kind of crazy system has Z as not being height?
People who think it's 'depth' because in a 2d world, Y is height (not all the time).

Looks like a simple case of too much Minecraft, the only game I know where Y is up and coordinates are routinely considered by players.
That's strange, because Torque is almost the only game engine I know that uses Z as up.

The surfaces of spheres (or the Earth) using latitude and longitude is X, Y. It only makes sense to use Z as height.

What exact value should I use for a 6x1x4 brick?