XRToolsStaging: Should warn if no Fade is added as a child #629
Comments
esodan
added a commit
to esodan/godot-xr-tools
that referenced
this issue
Apr 1, 2024
XRToolsStaging requires a MeshInstance3D to hold a transition fade. This adds a new property so the user is warned to add this node to staging. Fix issue GodotVR#629
|
The script is intended to be used in conjunction with the provided staging.tscn scene file which includes the fade mesh. Instantiating it separately would require the developer to manually create many nodes - or for the script to programmatically construct those nodes. Unfortunately Godot currently adds all named scripts to the "Add Child Node" wizard; making it difficult to prevent people from instantiating new nodes rather than the configured scenes. |
esodan
added a commit
to esodan/godot-xr-tools
that referenced
this issue
Apr 3, 2024
XRToolsStaging requires a MeshInstance3D to hold a transition fade. This adds a new property so the user is warned to add this node to staging. Fix issue GodotVR#629
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
XRToolsStagingshould warn if no$Fade, aMeshInstance3Dusing aQuadMesh, hasn't been added as a child.The warning should be shown and a new property
fadehasn't been set by the user. Also, reference to$Faceshould be replaced with this new propertyThe text was updated successfully, but these errors were encountered: