Wings 3D Development Forum

The update for Wings3D 2.0/2.0.1: yafaray.beam

Its work OK with my last TheBounty binaries. Thanks..

I discovered a bug in the "Transp Refraction" option, in Render Options Background. I have fixed the bug and posted an updated version of the Pre-Wings3D 2.0 version of the plugin on my website. I also removed "Backgroundmask" from the Background Alpha Channel options, since this was leftover from Old YafRay and is not available in YafaRay.

The following link shows what the "Transp Refraction" option is used for...YafaRay Refracted Background

Thanks,
oort

I discovered that the Texture Size (X,Y,Z) setting was not being exported. This has been fixed and the updated plugin is on my website.

I also changed the default rendered image file format from .tga to .png. I changed the default for the plugins folder from "c:/thebounty/bin/plugins" to "c:/yafaray/bin/plugins" to avoid confusion with the povmaniac TheBounty plugin.

There is a also a code improvement for how texture images are exported, thanks to Micheus.

oort

It was added some options to the plugin:
- Lights: Cast Shadows in the lights dialog;
- Materials: Visibility in the material dialog, for Yafaray settings under Objects Parameters tab.





The plugin update for v2.2.6 is available here.

Micheus,
Thank you very much for adding the shadow options to the lights and material object properties. I will test the plugin sometime soon.

Thanks again,
oort

Ooh, now this is interesting. I'll test the new functions as soon as I can.

Edit: I can already see a lot of shadow-play with this patch. Like adding new shadow dynamics where it shouldn't be possible, or even having the shadow cast by an object be the sole focus of a scene. Going further, this is definitely useful for background screens, as they can be placed anywhere with the shadow turned off and it won't interfere with lighting.

2nd Edit: I'm hitting a wall with installing the update. I installed it using the "install plugin or patch" button, but the file never arrived in the plugins folder. I went to go put it in the import_export folder for plugins, but it said there was already a file with the same name inside it.
I'm hesitant to mess with the files further, given how delicate a process it was to get Yafaray working for me.

VictorLincolnPine,

You can copy the old file to your windows desktop or other folder for safe keeping if you are worried that the plugin will stop working with the new .beam file. I do that myself.

I assume you are using Windows. It is just checking to make sure you want to replace the file. Sometimes Windows prevents the "install plugin or patch" from working. The workaround you are doing should work.

oort

Micheus,

I noticed that the "Visibility" setting in the Material/Object Parameters is showing up for all "Object Types". I expected to see it with the "Mesh" option but wonder if this setting works for all the other object types (Volume, Mesh Light, Light Portal) as well??? I could test instead of asking but thought I would just ask since I don't have time right now for fully testing the updated plugin.

Thanks,
oort

VictorLincolnPine,

1) the process of updating is using the patch option. It will never replace the original one in the installation folder. It's installed in the Wings3D's folder under the user profile - which should not cause any problem related to access control by OS.

Just remember, after apply the patch you need to restart Wings3D to get the plug-in active.

2) the visibility is per Material - that is why you find it on that dialog - not per object. Although I put the visibility parameter in that tab just for convenience, like part of a general settings.