proposal: instead of using x/y/z for 3d coordinates, use h/v/d, horizontal, vertical, depth

[eniko@mastodon.gamedev.place]

proposal: instead of using x/y/z for 3d coordinates, use h/v/d, horizontal, vertical, depth

now nobody will be confused which axis is up

(note: proposal is tongue-in-cheek)

[ratsnakegames@mastodon.social]

@eniko what's your proposal for UV coordinates?

[gbargoud@masto.nyc]

@eniko

Make all of your coordinates using a radial system with the character as the origin point.

Sure you need to recalculate the position of every object in the universe any time the character takes a step or turns and the lag would be horrifying but it's extremely unambiguous

[ratsnakegames@mastodon.social]

@gbargoud @eniko ... except you still need two angles so order still matters

[mdreid@mastodon.social]

@eniko
eXpand (gain width)
Yeet (upwards)
Zoom (away)

[eniko@mastodon.gamedev.place]

@ratsnakegames those are 2d so x/y works but h/v also works i suppose

[dsilverz@catodon.rocks]

@eniko@mastodon.gamedev.place Inspired by Kerbal Space Program and flight simulators, I'd suggest pitch/roll/yaw for rotation as well.

[ratsnakegames@mastodon.social]

@eniko yeah but you can't use the same letter twice

[ratsnakegames@mastodon.social]

@eniko (at least i always assumed they were UV coordinates because X and Y were already used for a vertex's 3d position)

[eniko@mastodon.gamedev.place]

@ratsnakegames ohhh that's what you mean lol

yeah idk why it's uv but i assume it is because xyzw were already taken

[dequbed@mastodon.chaosfield.at]

@eniko sub-proposal to rename 'depth' to 'stabby' because it measure how close something is to stabbing you!

[eniko@mastodon.gamedev.place]

@ratsnakegames so actually if you use h/v/d then that opens up x/y for texture coordinates, perfect!

[jordan@sometimes.social]

@mdreid @eniko thing is, I’m gonna remember this one

[oblomov@sociale.network]

@eniko «ok but which horizontal is which»

[oblomov@sociale.network]

@eniko jokes aside, it's not a bad proposal. It's the same reason why I use row/col instead of x/y or i/j as indices in matrices.

[maia@mastodon.art]

@eniko i mean depth is already used for size in the z dimension, like width and height are for x and y, so it should’ve been obvious already

[jessechounard@hachyderm.io]

@oblomov @eniko I avoid row/col because that's y/x (not x/y) and I have to stop and think about it every time.

[gilesgoat@toot.wales]

@eniko What about row mayor / column mayor matrices ? ( and row / column vectors V * A or A * V ? )

[staringatclouds@mstdn.social]

@eniko

h/b/d - height/breadth/depth ?

[oblomov@sociale.network]

@jessechounard @eniko see, your problem is that you're using y for the row, which is obviously wrong 8-D