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

Exporter needs to check each blender object is in starter Scene #411

tkyler opened this issue Jan 30, 2019 · 2 comments


None yet
2 participants
Copy link

commented Jan 30, 2019

Using root mode export in "Scene A". Auto-detect textures OFF, manual paths/names for albedo and normal. Exporting gives me error of "ERROR: Circle.1667: No Material found"....except that Circle.1667 is a mesh, unparented to anything and in a completely differing Blender scene, i.e. 'Scene B'.


This comment has been minimized.

Copy link

commented Jan 30, 2019

FWIW, Additional Note. When I open a new blender file and 'append' the scene I am trying to export, it exports out fine.

@tngreene tngreene changed the title error message of "No Material Found" on meshes that are in differing scenes Exporter needs to check each blender object is in starter Scene Jan 30, 2019


This comment has been minimized.

Copy link

commented Jan 30, 2019

The issue turned out to be that since the exporter only looks at parent-child relationships it could recuse down the parent-child tree into Datablocks that were in other scenes, including them or finding errors there. Very unexpected, since the Outliner doesn't show those relationships.

The fix breaks the workflow of anyone who is depending on this kind of behavior, which I hope is no one.

tngreene added a commit that referenced this issue Jan 30, 2019

@tngreene tngreene closed this Jan 31, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.