Assigning quaternion to basis problem

z80

Hello!

Godot version 3.4.2, platform Windows 10. When I assign a Quat to a Basis, result depends on where I run the game. If started in editor, everything is fine. But if from PCK file, it doesn't work, and Basis is IDENTITY after the assignment.

Why does it depend on how I run the game? Is it a bug or a feature? I'd appreciate any advice!

func _update_orientation( rotation: Quat ):
    var n: Spatial = get_node("Orientation")
    n.transform.basis = rotation

See the screenshots attached.

cybereality

Basis and Quat are two different classes, though you can convert between them.

https://docs.godotengine.org/en/stable/classes/class_basis.html

z80

@cybereality said: Basis and Quat are two different classes, though you can convert between them.

It doesn't answer the question why conversion result depends on if project is run in editor or as a packed PCK.

Shouldn't is work the same way in both cases?

cybereality

No, it shouldn't work in either case. Probably some undefined behavior.

z80

@cybereality said: No, it shouldn't work in either case. Probably some undefined behavior.

So basically you are saying it's an engine bug, correct?

The point of the very first post was that the behavior is not quite undefined. As it is possible to see on screenshots, if executed from editor, Basis = Quat, causes correct conversion to rotation matrix.

I've just checked, if executed in editor, both Basis = Quat and Quat = Basis assignments work correctly and cause implicit conversion of one to another. The last one works only if Basis scale is 1. If scale is not 1, resultant Quat is always identity quaternion.

My guess is, if it was not supposed to work, it should have risen an error.

Megalomaniak

This is perhaps a question best presented to a engine developer. @Calinou tends to be the most active one on the forums, perhaps they can give a more definitive answer.

cybereality

That would be my understanding. I've never tried to do that, maybe there is some implicit conversion, but my intuition is that it is either a bug or some unfinished/unintentional behavior. Based on the API and what I know, it seems like it should not work, and should generate an error (or at least a warning).

Calinou

This is likely because type hints behave differently between debug and release mode, which is a known issue that probably can't be fixed in 3.x (due to how typing was shoehorned into an existing language, rather than being included from scratch). This is likely fixed in Godot 4.0alpha already.