I’ve been trying for some time to get yafray (0.7) to work with Blender (2.34). Blender works just fine, and I’ve installed yafray, I can start it from the commandline. The problem is, when I try to render from Blender with “YafRay” instead of “Blender Internal” as renderer and try to use the plugin (“xml” switched off) I get:
Starting scene conversion.
Scene conversion done.
Loading plugins …
YafRay plugin loaded
Rendering with yafray via export works fine, it’s just sooo much slower than the internal renderer…
I’m running Debian, kernel version 2.6.6 (custom). My graphics card has 3d acceleration and the drivers work fine.
I am unable to use yafray as well. When I render with yafray selected, the render screen comes up as a black screen. when I render with the ‘blender internal’ everything renders as it should in the render screen.
I’m completely stumped. Since blenderman’s site is temporarily down, I can’t consult their guide either…not that it was helping me solve this problem a few hours ago…
What you have been missing ois most probobaly the export settings. If you pull the border of the uppermost window down, you’ll expose the user preferences. There, select “FilePaths” and set the YFExport value. (Under Linux, this is necessary anyway). If I unselect the xml button, as you described, blender crashes with the segmentation faut I’ve described.
The difference is, if you select the xml button, the scene gets exported to a file in the YFExport path, then yafray gets called to render this file, and when it’s ready, the result is displayed in the render window. In between, you don’t see the progress.
If you deselect the xml button, Yafray gets called as plugin, the scene is not exported, and you can see the rendering progress in the render window. This is most likely what you’re doing (and what, as said before, causes blender to crash in my case).