question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Traceback errors on export from Blender 2.8

See original GitHub issue

First, I’d like to say that you folks are doing killer work, and I enthusiastically look forward to being able to use this regularly with the Principled BSDF shader in the upcoming Blender release.

That said, I’m not sure how well the exporter should be working currently, as I understand it’s still in development, as is Blender 2.8, which makes it difficult for me to pinpoint the source of the errors.

I can’t seem to export a simple cube to gltf or glb using the latest versions of both the exporter and Blender 2.8 with the settings below:

image

I use practically the same workflow and settings with Blender 2.79b and the glTF-Blender-Exporter, except I use the included glTF Metallic Roughness PBR nodes. In this case, I’m trying to use Blender’s Principled BSDF shader and I’m getting the following errors:

image

This seems to be happening specifically when I check Export selected only, which I use often in my workflow.


I’m getting similar errors when trying the other options:

image

image


image

image


The only combination that appears to work is this:

image

However, it only seems to work the first time. After trying to re-export with those same settings, the resulting file is corrupt. It also exports all layers and doesn’t let you select objects, which isn’t typically ideal.


Here is a zip with the .blend file and a sample of the corrupt file: exporter_test.zip


Blender version: image

Exporter version: image

OS: Windows 10 x64

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:13 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
juliendurourecommented, Nov 25, 2018

@emackey This error is already fixed in master and in blender 2.8 git. This will be available in tomorrow’s build

Still have to work on layer export option (see my TODO list on first comment of this issue )

2reactions
juliendurourecommented, Nov 27, 2018

Is now in Blender repo

Read more comments on GitHub >

github_iconTop Results From Across the Web

T58984 Traceback error during FBX export
While trying to export an FBX file I got the following traceback error;. Traceback (most recent call last): File ...
Read more >
Traceback Error while FBX export - Blender Stack Exchange
I got the same error today. I traced it down to one image texture. Once, I used a different for testing. The problem...
Read more >
Python Traceback error, unable to import/export anything.
r/blender - Python Traceback error, unable to import/export anything. ... It's either malware on your system or an out of date/dodgy add-on has ......
Read more >
Tracebacks | Avalab
Some errors are already classified by Avastar (here it found an Export Error) ... how to open the blender console, you can cut/paste...
Read more >
Traceback error - Soft8Soft
So I uninstalled Blender 2.79 from my system, and run 2.8 beta from the file folder. I have the current version of Verge3d...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found