Skip to content
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

Open
kitaedesigns opened this issue May 14, 2021 · 8 comments

Comments

@kitaedesigns
Copy link

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.

image

@kitaedesigns
Copy link
Author

Also nothing is hidden, tried alt+h and there's nothing there.

@kitaedesigns
Copy link
Author

Solved by copying and pasting everything into a new project.

@kitaedesigns
Copy link
Author

Issue is still persisting
"line 521, in execute
obj.select_set(state=True)
RuntimeError: Error: Object 'Object' can't be selected because it is not in View Layer 'View Layer'!

location: :-1"

@kitaedesigns
Copy link
Author

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.

@kitaedesigns
Copy link
Author

image

@s-light
Copy link

s-light commented Aug 16, 2021

related to #9 ?!

have you tried to use the Fileclean up functions?
and close and reopen blender after deletion of objects?
internally blender only removes the links to objects - the object data itself will only be cleaned up / deleted on close / reopen or with the mentioned command..

@octu8re
Copy link

octu8re commented May 7, 2023

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.

@garyritchie
Copy link

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 > character in the object name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants