Closed mhusinsky closed 1 year ago
i just noticed that the transform is not applied at all currently (but probably should for flexibility reasons - see post above).
however, there is a bug with setting the y/z components, which are flipped (due to imprecise Pin alignment in the AppendV3 node).
thanks for that report. i've fixed the zy swap which revealed another issue: the face-winding was off, which could be seen when loading an .obj that was saved with ObjWriter. it is not entirely clear to me why this is the case since both stride(dx11) and obj should have counter-clockwise ordering of faces.
so if you encounter normals/face-winding issues, please reopen.
also exposed the Transform input so you can do custom CoordinateSystem conversion on export.
Is your feature request related to a problem? Please describe. The OBJ writer assumes a certain type of output coordinate system that does not necessarily comply with the coordinate system of the target application where the OBJ will be used (even VVVV would display the OBJ differently).
Describe the solution you'd like Exposing a transform input for the CoordinateSystemConversion on the OBJWriter node would allow for setting the coordinate system yourself, instead of the node's internal assumption.![grafik](https://user-images.githubusercontent.com/3253299/230496025-2c8e4ae5-0513-47cb-9cf3-8cf62340692f.png)
Describe alternatives you've considered An additional Transform input pin. Unconnected would output the model as it is represented in Stride. With (any) transform connected, the target output would take the respective orientation.
Additional note It should be easy to implement and I'd be happy to create a PR if you agree with this idea.