-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
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
OBJ files and DAE (better dae) are not imported correctly. Absent in .import folder. #8741
Comments
I think reopening Editor fixes .dae imports. |
You can also re-export the mesh after the initial import, then that seems to fix it also without closing the editor. |
I can't reproduce this, so any help with more steps to reach this situation are appreciated |
@reduz Restarting editor seems to import them correctly. |
Is this still valid now? |
I seriously can't reproduce this, did you maybe switch to godot before the file is done exporting? if so Godot might find it invalid and you will have to reimport manually.. but this is normal behavior. |
Will check it later, sorry can't right now. :B |
@reduz It creates |
I played around with a 3.0 windows build today (12/13th June build) and I noticed when I updated an OBJ file, godot detected the change and showed the import progress bar, but once it had finished, it was still the old version of the mesh being displayed. Even when I deleted the meshinstance node, re-added it and selected the mesh file again, it was still the old version. The only way I could make it work (didn't try restarting the editor) was to save my OBJ file with a new name so it did a fresh import |
I did many changes to this, would appreciate testing again. The type and resource should definitely be recognized always now.. |
Maybe close this if there are no further updates? |
Ubuntu - Godot 3.0-master (e883cda)
Issue description:
3.0 Obj and DAE are not imported correctly. They are absent in .import folder.
Loading .obj to mesh instance is not working - "not a resource".
Opening DAE also - "Error loading scene".
The text was updated successfully, but these errors were encountered: