-
Notifications
You must be signed in to change notification settings - Fork 17
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
On Export Error - Blender/plugin is looking for mesh that doesn't exist and export fails. #11
Comments
Also nothing is hidden, tried alt+h and there's nothing there. |
Solved by copying and pasting everything into a new project. |
Issue is still persisting location: :-1" |
Something happens in the file that makes export impossible. Even after deleting all the objects that error appears and the only solution is to copy everything and export to a new file and start over which of course is not ideal. |
related to #9 ?! have you tried to use the |
I ran into this problem today while testing and ran all cleanups. Make sure all the objects in your scene are good to go, because a cleanup could easily ruin a project. |
In my case, the object was in another scene. Linking it to the export scene caused export to work but I'm puzzled because that object didn't appear to be linked in any way with the scene I was exporting from. Also worth noting is I was using the Capsule addon which writes a hidden object to the scene, visible in the Blender File data view (Outliner), that halted export due to the |
Python: Traceback (most recent call last):
File "C:\Users\Kitae\AppData\Roaming\Blender Foundation\Blender\2.92\scripts\addons\aframe_blender_exporter-master_init_.py", line 579, in execute
obj.select_set(state=True)
RuntimeError: Error: Object 'Cube.004' can't be selected because it is not in View Layer 'View Layer'!
location: :-1
There is no "Cube.004" in my scene and there are no other View Layers. Yet export fails because it's looking for this mesh.
The text was updated successfully, but these errors were encountered: