-
-
Notifications
You must be signed in to change notification settings - Fork 20.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import .blend using Blender 4.0 #79124
Comments
It would be best to wait for blender 4.0 to be stable, as there might be some breaking changes along the way. |
Simple fact is that we don't currently support this version as it isn't guaranteed to be compatible, not really a bug here, but worth investigating the compatibility, but be aware that Blender 4.0 hasn't been released yet so there's no reason to support it until then |
Yes, agreed. But before 4.0 daily builds worked well. So you don't have check for maximum version. Also it is not possible check integration issues on blender development version. So all bugs will (if they will be) when new Blender release appears. In my opinion, there no reson to block dev blender version. |
It took Blender two decades to go from 2.0 to 3.0, so I guess Juan didn't expect 4.0 to come so soon. The editor setting is even named But yeah the test is likely overeager and could be removed. |
One suggestion would be to add a warning when using recent versions, indicating that it might behave in unpredictable and undefined ways (as it's not yet released as far as I can tell, and I don't know that we've investigated compatibility) and prepare for the release and check the compatibility While it should comply with the GLTF standard on the output, I assume there might be incompatibility with the command line interface or similar, or things like properties and things Partially to prevent bug reports because of a lack of information that it might not work at the moment, if we just enable support without any warning |
I really wouldn't recommend using Blender 4.0 for any serious work yet. There are massive breaking changes going on with the way mesh normals and smoothing work. These changes, when they are finalised, will have to be updated in the gltf exporter, which is what the Godot importer is using in the background for a blend file. |
People who install daily builds already know that it is unstable. I don't think that Godot should send another warning to the user. If something wrong with blender importer user should see an error in output and create a bug report here with included blender version. Godot developers will know all breaking changes before 4.0 release and will be ready. |
@hemulya the whole point is that Blender 4.0 itself is changing rapidly - no point engaging in a wild goose chase if some things end up reworked/dropped on their side |
This is correct. But as I see, you want block blender dev builds. So evere 2/3 monthes you need update Godot to not use version 4.0/4.1/.... And you will engaging goose chase. |
What we can do is allow using Blender development builds, but display a warning in the dialog after choosing such a version and printing a warning on startup (so you remember that you're using a development version). |
Hey, guys. |
This is being tracked in #82211 |
Fixed by #81194. |
Godot version
4.1
System information
Godot v4.1.stable.mono - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 (NVIDIA; 31.0.15.3640) - Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 Threads)
Issue description
When importer detects blend file next window apears:
I'm using Blender daily builds which recentrly updated to version 4.0
Steps to reproduce
Minimal reproduction project
Used newly created godot project
The text was updated successfully, but these errors were encountered: