Blender has fixed the issue with custom node display. Try a new daily build .
1 Like
Not able to help with so little information.
Hello,
as first, many thanks for the absolutely great work and lovely looking renderer! I admire your code, time and effort spent for it.
I would really like to use it, but no matter what i do in B27 or B28 (and B28 - daily builds), i get in the same way as my predecessor black objects. As soon as i apply any shader to it, it turns black.
Before applying shader, the scene renders in viewport gray, without shadows. I think something got busted 
1 Like
You’re using the Cycles output node. Use the AsClosure2Surface node for the materials to work properly.
1 Like
See screenshot, as @jdent02 just wrote you need to feed the surface shader output of your material into an asClosure2Surface node.
aaagrhhhh… sometimes i should really go to optician or maybe better to some brain neurologist…
thank you, guys, a lot for the help!
best regards
No problem!
It is a bit confusing for new users because the Cycles nodes and default node tree unfortunately cannot be hidden when switching to appleseed render engine. Added to this, when one creates a new material and switches to Use Nodes a default Cycles material node tree is automatically created.
So users may be tempted to mix Cycles with appleseed nodes, which does not work in appleseed. Cycles nodes are ignored by the exporter, there is no need to delete them but they don’t have an effect in appleseed render.
1 Like
Hello,
I want to ask If you know when is planning release date for Blender 2.8 for linux?
Unfortunately we do not have an estimated date for a Linux build. For some reason Blender 2.8 is basically not working with our Python bindings on Linux and we still don’t quite know why.
Ok, thanks for info.
Some more info on the Linux build problem.
appleseed as well as Blender depends on an array 3rd party libraries, Python, OSL, OIIO, LLVM, Boost, OpenEXR and others. To work flawlessly together, the versions of these libraries linked into Blender and appleseed need to be compatible. Blender has its own custom Python interpreter built in and this one is unfortunately not compatible with the one appleseed needs to be compiled with for its Python bindings.
To avoid these problems, under Linux exists a common consensus on which libraries and tools should be used that major CG application can work together . It is called VFX Reference Platform
Unfortunately Blender does not currently follow the VFX Reference Platform standard, while appleseed does (so that it can be integrated into Maya and Gaffer).
For a longer term solution we started to reduce dependencies, better isolate api functions and maybe we add a simplified C API which would make interfacing with Blender more robust.