Stride3D configurable for Left-Handed Axes?

[najak3d]

Both Unity3D and Urho3D use Left-Handed, while Stride3D is Right-Handed. We're coming from Urho3D.

Our map app, uses X+ = East, and Z+ = North. And Y+ is Up. Left-Handed Axes work naturally with this convention.

Since most games/engines say "Y = Up" (as well as most models you get), that seals the convention that Y = UP. It's hard to deviate. And "Yaw" means to rotate around the "up-axis", also a sealed convention.

A Left-Handed Axes would be more natural for how MOST games are thinking, IMO.

  Z+ == Forward or North,  X+ == Right/East,  Y+ == Up / Increasing Altitude.   (No Exceptions)

But for Stride (and Godot), using Right-Handed, you are stuck with a small conundrum

Either Z+ == Backwards/South,   OR    X+ == Left/West.     (Stride3D chose Z+ = Backward)

(One of these will have to go against the convention of Geo Coordinates, where East = Longitude+, and North = Latitude+).

With Right-Handed (and Stride3D), one of those is an oddball -- so you are sorta screwed.

Since we are planning to switch from Urho.NET to Stride3D, I was hoping for a Left-Handed system here. I imagine it's a PITA for Stride3D to support "either" (user-configurable).

====
NOTE: IF we were able to feasibly deviate from the pretty concreted standard (in 3D gaming) of Y+ == UP, and instead could have Z+ ==UP -- then the Right-Handed Axes makes better sense, as X+=Right/East, and Y+=North/Forward. But I don't think we can feasible do this without worse issues, as it changes the meaning of "Yaw" and also doesn't match the convention of most models you buy off-the-shelf.

[najak3d]

As I'm really wanting to port to Stride3D (since it's all .NET, and momentum seems to be building) - I'm going to comfort myself by thinking of it this way:

The XZ map coordinates will instead:
"Like Reading a Book" or "How Bitmaps are layed-out".

Which is Left-to-Right, and Top-to-Bottom, which will coincide with X+=Column+, and Z+=Row+ -- which is the direction of reading a book, or reading pixels from a Bitmap.

So if we just change our thinking away from Cartesian-Coords, and think "Reading a BooK" - then we could make sense of Right-Handed axes better, and it won't seem to be a "mutant".

When thinking in terms of GeoCoords -- We'll just think of "NorthPole is the origin", i.e. "Z=0"... then Z becomes "Distance from North-Pole" -- just as "Row#" is "# of rows from the top of the grid/page".

I can live with this.