YafaRay Plug-in

[oort]

There is now a 32bit build of YafaRay 0.1.5 in the following thread... You will have to look for the posting by povmaniac... YafaRay 0.1.5 RC 32bit

I had to update the Wings3D plugin due to a change in how the mesh code is written in YafaRay 0.1.5. The new version of the plugin is backwards compatible with YafaRay 0.1.3 for those who want to play with SSS. Ready for download.

oort

[povmaniac]

Hi oort..
I forked the Wings repo for add the YafaRay exporter code.. with your permision, of course.
(sorry, my english is not very good)

[oort]

povmaniac,
Your English is fine. Since the releases of new versions of Wings3D is so slow lately you may be better off just modifying the plug-in code instead of creating a fork. I am assuming that it is your intent to work on the plug-in. My code is probably very messy and not written in the best way. My goal was to just get it working. Do you have anything specific that you plan to do? If you are interested in cleaning things up maybe it could be added to the 0.1.5 Snapshot release, assuming dgud is ok with that.

P.S. Welcome to the Wings3D forum...

oort

[povmaniac]

Today I have started cleaning and arranging the code as practice to learn a little of Erlang. He can find the modifications in my fork of the repository of Wings3D:
https://github.com/povmaniaco/wings
in the branch 'yafaray_exp'.

[oort]

povmaniac,
Thanks for taking on the task of cleaning up the code. There are still some things from old YafRay 0.0.9 that have been left in the code. Some I left in the hope that those features would be added to YafaRay and others may just be code I didn't take the time to clean out.

Be sure to add your name in the credits at the top of the code. I still needed to give Micheus credit for helping fix the problem with spaces in file and folder names.

I assume you will also move id to the front of mesh code (Line 4630). I hadn't fixed that yet....

oort

[povmaniac]

I have not managed to compile the exporter to verify if it works after the changes in the code.
I have installed the last version of Erlang and, also I have cloned the repository of Wings3D to my PC.
Do you have any script for compile the exporter?

[oort]

I use Cygwin to compile all of Wings3d. I do not just compile the yafaray plugin. I go to the wings-1.4.1 (or whatever version you are working on) folder and type "make". You do need to modify the Makefile under the plugins_src\import_export folder. You need to add "wpc_yafaray" to the list of MODULES near the top of the file.

I hope that answers your question.

oort

[povmaniac]

I use Cygwin to compile all of Wings3d. I do not just compile the yafaray plugin...

All Wings3d?? Non, merci..
I have 15 'compilers environment' in my PC ( more or less)..
My proposal..: I could help to you with the exporter code, but you make a builds..
Greetings.

[oort]

Yes, I will gladly make the builds.

Edit: I think that MinGW can also be used to build Wings3D.

Edit2: I compiled the github copy of wpc_yafaray.erl and only had one error. Line 1020. I had to add "[" before hook.

], [hook(open, [member, ?KEY(shader_type), shinydiffuse])]

oort

[micheus]

All Wings3d?? Non, merci..
I have 15 'compilers environment' in my PC ( more or less)..

povmaniac, I think you don't need.
As you already have cloned the wings repository from git, you would just have to enter in the wings/plugins_src/import_export and run make.

I did a test here (on my dev. environment) by leaving only the wings source folder and removed any .beam file previously generated and I was able to compile all the export/import plugins.
_____________

I noticed that you will need to add the yafaray to the makefile file:

Code:

:
MODULES= \
    wpc_3ds \
        :
    wpc_x \
    wpc_yafray \
    wpc_yafaray

TARGET_FILES= $(MODULES:%=$(EBIN)/%.beam)
:

By supposing that you didn't cloned esdl, you would need to remove the $ESDL_PATH references in the makefile:

Code:

:
WINGS_E3D=../../e3d
# *** removing ESDL reference
# ESDL=$(ESDL_PATH)

ifeq ($(TYPE),debug)
:
# ----------------------------------------------------
# FLAGS
# ----------------------------------------------------
#ERL_COMPILE_FLAGS +=  -pa $(WINGS_EBIN) -pa $(WINGS_INTL) -I $(WINGS_INTL) -I $(WINGS_SRC) \
#  -I $(WINGS_E3D) -I $(ESDL_PATH)/include -W $(TYPE_FLAGS) -pa $(ESDL_PATH)/ebin \
#  +debug_info
# *** replacing with these lines ***
ERL_COMPILE_FLAGS +=  -pa $(WINGS_EBIN) -pa $(WINGS_INTL) -I $(WINGS_INTL) -I $(WINGS_SRC) \
  -I $(WINGS_E3D) -W $(TYPE_FLAGS)  \
  +debug_info

You will find the output beam at wings/plugins/import_export.

You may need to check these environment vars:
PATH -> should include the erlang bin folder (i.g. /c/.../erl5.10.1/bin) and the C compiler location (i.g. /c/MinGW/bin)
WINGS_SRC_PATH -> should point to the wings source root (i.e. /c/sources/wings)

Please check this. I'm sure that would be good if you could get the compilation feedback by yourself.

Thanks for help our community.