You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a regression since v4.0.beta16.official [518b9e5], though I haven't bisected the commit that caused it.
When using change_scene_to_file to load into a new scene, a CSGCombiner3D with a child CSGPolygon3D is modified from how it looks in the editor (or running the scene first).
Observe how the MRP scene looks in the editor:
How it looks when using Run Current Scene (F6):
How it looks when running the project with a simple script that loads into the same scene:
The script:
extendsControlfunc_ready() ->void:
get_tree().change_scene_to_file("res://node_3d.tscn") # res://node_3d.scn is the same scene but it wouldn't open in Beta 16 that I used to test (corrupt)
The hole is gone. The remote editor seems to show the same values and the nodes are all there.
I don't know if something else broke with change_scene_to_file, if someone knows a workaround please share it.
Steps to reproduce
Run the MRP. Note: the 3d scene .scn binary format won't open in Beta 16, the .tscn is the same scene and it opens, that might be a clue.
I used Windows Builds artifacts to narrow it down (it takes me a long time to build Godot):
v4.0.beta.custom_build [045822e66] - no bug
v4.0.beta.custom_build [f5cf2d992] - no bug
v4.0.beta.custom_build [5bcf016] - has bug
To properly bisect using GitHub artifacts, you should use only artifacts from "Merge pull request" commits. The other ones are from PRs, and may be based on older branches and not include what caused the regression (even if the build happened later).
I am running into this too, and I found that everything works when collision is enabled. Based on the original bug #71240 that was fixed by #72427, I think this should be an easy fix. I'll attempt it.
Godot version
v4.0.beta.custom_build [2bd5302] ; v4.0.beta17.official [c400205]
System information
Windows 10, Vulkan
Issue description
This is a regression since v4.0.beta16.official [518b9e5], though I haven't bisected the commit that caused it.
When using

change_scene_to_file
to load into a new scene, a CSGCombiner3D with a child CSGPolygon3D is modified from how it looks in the editor (or running the scene first).Observe how the MRP scene looks in the editor:
How it looks when using Run Current Scene (F6):

How it looks when running the project with a simple script that loads into the same scene:

The script:
The hole is gone. The remote editor seems to show the same values and the nodes are all there.
I don't know if something else broke with
change_scene_to_file
, if someone knows a workaround please share it.Steps to reproduce
Run the MRP. Note: the 3d scene .scn binary format won't open in Beta 16, the .tscn is the same scene and it opens, that might be a clue.
Minimal reproduction project
csg bug.zip
The text was updated successfully, but these errors were encountered: