silverslade / aframe_blender_exporter

Blender Exporter for A-Frame VR
MIT License
103 stars 17 forks source link

On Export Error - Blender/plugin is looking for mesh that doesn't exist and export fails. #11

Open kitaedesigns opened 3 years ago

kitaedesigns commented 3 years ago

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 commented 3 years ago

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

kitaedesigns commented 3 years ago

Solved by copying and pasting everything into a new project.

kitaedesigns commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

image

s-light commented 3 years ago

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 commented 1 year ago

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 commented 5 months ago

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.