Wings 3D Development Forum

Full Version: YafaRay Plug-in
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11
Always the same error.. "undefined parse transform
'tools'"
Code:
make TYPE=opt common
make[1]: Entering directory `/h/yafmaster/wings/plugins_src/import_export'
erlc -pa ../../ebin -pa ../../intl_tools -I ../../intl_tools -I ../../src -I ../
../e3d -W  +debug_info -o../../plugins/import_export wpc_3ds.erl
h:/YAFMAS~1/wings/PLUGIN~1/IMPORT~1/wpc_3ds.erl:none: undefined parse transform
'tools'
make[1]: *** [../../plugins/import_export/wpc_3ds.beam] Error 1
make[1]: Leaving directory `/h/yafmaster/wings/plugins_src/import_export'
make: *** [opt] Error 2

Sorry.. my 'tools':
- Win XP SP3 32 bits...
- MinGW 4.7.1 with msys 1.0 ( the same for build YafaRay..)
- Erlang R16B (erts-5.10.1)
- esdl, rebar , cl.. from github
I think you need to make the content of /h/yafmaster/wings/intl_tools.
EUREKA!!
The exporter is build well.. but show this error on startup wings3d:
Code:
Trying OpenGL modes
  [{buffer_size,32},{depth_size,32},{stencil_size,8},{accum_size,16}]
Actual: RGBA: 8 8 8 0 Depth: 24 Stencil: 8 Accum: 16 16 16 16
wpc_yafaray:init/0 bad return value: {'EXIT',
                                      {undef,
                                       [{wpc_yafaray,init,[]},
                                        {wings_plugin,init_plugin,2},
                                        {wings_plugin,init_plugins,1},
                                        {wings_plugin,init,0},
                                        {wings,init,1}]}}

... and not work.
I just compiled the file that was on github and it works fine for me. I wonder if it has something to do with the fact that you only compiled the plug-in and not all of wings3D??? Maybe an issue with Edit > Plugin Manager???

oort
(06-02-2013, 05:29 PM)oort Wrote: [ -> ]I wonder if it has something to do with the fact that you only compiled the plug-in and not all of wings3D???
I thought the same thing too.

Quote:Maybe an issue with Edit > Plugin Manager???
I don't think so. I've cleaned the whole yafaray information in the Preferences.txt and It still worked fine for me.

povmaniac, is there any chance you try to build wings just once? (make under the wings' source root)
Or, maybe, just install the latest wings snapshot and move the wpc_yafaray.beam to the proper folder and check if it will work fine? If so, then maybe you would only change the beam destination into the makefile:
EBIN=../../plugins/import_export
to
EBIN=<wings install dir>/lib/wings-1.?.????/plugins/import_export
and then run your wings installed for test the plugin.

Just trying give you some options. Smile
Quote:povmaniac, is there any chance you try to build wings just once? (make under the wings' source root)
Or, maybe, just install the latest wings snapshot and move the wpc_yafaray.beam to the proper folder

Thanks !! is working well in your build (wings-1.5.pre1.74.g2aee.exe).
Great!!

Goo!!
[attachment=76]
povmaniac,
Very glad you got it working. As Micheus already said, thanks for helping the Wings3D community... Smile I look forward to seeing what you do with the plug-in.

oort
I just found this today and I think it could be useful when we are trying to find a good setting for lights: Comparison of point, area and mesh lights

Maybe later we can produce ourselves lights references. Smile
I discovered that two of the Ambient Light > Backgrounds (Constant and Gradient) did not produce light when UseBkgnd was enabled under YafaRay Render Options. I found out that there was a change that went into effect with YafaRay 0.1.2 that moved this setting to the Background settings for Constant and Gradient. They now work the same as Image and HDRI Backgrounds. YafaRay 0.1.2 Notes. Note that this now works for Direct Light, Photon Mapping, and Pathtracing.

I have updated the Wings3D Yafaray plug-in to reflect that change. I also did some edits in the help info under Edit > Plugin Preferences > YafaRay.

I changed the default setting for Gamma under YafaRay Render Options from 1.0 to 2.2 based on what I have read in the YafaRay forum. YafaRay Gamma. The info is a bit confusing since it applies to Blender but in tests I found that Gamma at 2.2 seems to give better results. I may be wrong and can change the default back to 1.0 easily.

The updated version is on my Wings3D page. I have tested it on Wings3D 1.5.3 and everything seems to work.

You will also want to get the YafaRay 0.1.5 SSS build by Povmaniac that is on my website. Using the official version of YafaRay will not give you access to Subsurface Scattering.

oort
Pages: 1 2 3 4 5 6 7 8 9 10 11