YafaRay
He is part of the YafaRay team
I just made some fixes and provided a test build to oort.
Kerkythea
But, no. You don't need to reassign the material.
What I do in these cases:
- In Wings3D I selected the changed object (mesh or UV) and use the option Export Selected->Kerkythea naming it "Temp.xml";
- In Kerkythea, I use the File->Merge with the option for Models -> "Name Collision: Replace Mesh" and for everything else "Keep Current" (except when I need any other to be changed).
* We have the option to go to the Models->Edit Material and bellow the preview image I use the right buttom to store the current material settings in the Current Library (for safety)
Since Kerkythea isn't in development for long time I never tried to play around with its export. It would be better to implement a new one for a free render still in development - like LuxCoreRender. dgud has been waiting for someone to work on it for long time. It could be a good start point for your Erlang adventure.
Quote:Thanks oort for making available the unofficial Yafary plugin, and thanks a lot Micheus for going on improving things for Wings3D. I like all these new tabs with plenty of new parameters to testIn the Yafaray case, the credits for the improvements are for david.bluecame - YafaRay Plug-in - reviewing for Yafaray 3.0
He is part of the YafaRay team
I just made some fixes and provided a test build to oort.
Kerkythea
Quote:OK, does it mean that in your workflow, you basically use Wings only for the geometry and the UV mapping, then go to the Kerkythea GUI for all the material, light and texture stuff ?Yes.
Quote:But each time you want to change the geometry or the UV mapping in your scene, do you have to reassign the materials and textures for all objects of your scene?I avoid to go to render before I finish my work.
But, no. You don't need to reassign the material.
What I do in these cases:
- In Wings3D I selected the changed object (mesh or UV) and use the option Export Selected->Kerkythea naming it "Temp.xml";
- In Kerkythea, I use the File->Merge with the option for Models -> "Name Collision: Replace Mesh" and for everything else "Keep Current" (except when I need any other to be changed).
* We have the option to go to the Models->Edit Material and bellow the preview image I use the right buttom to store the current material settings in the Current Library (for safety)
Quote:Or can the geometry be kept in a separate Kerkyhea/XML file and included as a file in the XML file defining the materials, the light and the rendering parameters (kind of a "#include" or "import" mechanism that exist in programming languages) ?Not that I know about that is possible.
Since Kerkythea isn't in development for long time I never tried to play around with its export. It would be better to implement a new one for a free render still in development - like LuxCoreRender. dgud has been waiting for someone to work on it for long time. It could be a good start point for your Erlang adventure.