search

appleseedhq / blenderseed

appleseed plugin for Blender
https://appleseedhq.net/
MIT License
275 stars 43 forks source link

Default render, no textures, no glass material? #109

Closed zohozer closed 6 years ago

zohozer commented 6 years ago

I just installed the latest Blenderseed 0.6 and I opened the Red_interior.blend file in Blender 2.79 and I just pressed the Render button.

Seems that the output is quite different than the one that need to be. Seems that it is missing shaders and textures.

I checked the textures and they are loaded in blender but for some reason they are not assigned to shaders?

Also, another weird thing is that if I press the "appleseed Node" under Surface Shader, the material disappears.

blenderseed_0 6_defaultrender

dictoon commented 6 years ago

Looking into it, thanks for the report.

dictoon commented 6 years ago

I can reproduce, we're looking into it.

dictoon commented 6 years ago

It appears that we somehow broke compatibility with previous .blend files. We're investigating.

Narann commented 6 years ago

As we tends to provide various integrations, peoples will start to spend time playing with appleseed in their favourite software. I think we should also start to think about "regression tests suite" into those applications. Open and render some scenes could help. A repo like blenderseed-regression-test-suite (appleseed-max-regression-test-suite, etc.) or something like this aimed to detect this kind of bug.

It could be a shame to be in the same situation than Inkscape and Pepper & Carrot.

dictoon commented 6 years ago

@Narann I completely agree. While we have fully automated, high coverage tests for appleseed itself, we don't have anything automatic for the integrations/plugins at the moment. We do however perform manual regression tests before releases.

The case of blenderseed is slightly different: we decided to move fast and fix many issues post-release, but we're still learning the code base (the plugin was originally written by an exterior contributor) and clearly we broke compatibility unwillingly (and unknowingly). And we failed to perform the most minimal regression tests.

We learned out lesson and will do better next time!

dictoon commented 6 years ago

@zohozer We have identified the source of incompatibilities. We were not declaring material properties and rendering settings correctly inside Blender. Unfortunately we have no choice but to break compatibility one more time in the next release. Sorry for that.