Wings 3D Development Forum

Micheus,
I will move "Delete" to the end of the line.

I had noticed that problem of the material properties dialog and I think I posted a gripe and grumble about that a long time ago. I originally noticed the problem when I was playing with ggaliens work on the renderman plugin. I remove all of the other rendering software in the plugin manager and that helps some.

I was going to see if I could figure out how to get that window to be scrollable like other windows at some time. I bet you could figure it out faster....

Yes spaces in file names is a problem just as it is for folders. I guess I should add a note about that as well. Maybe the YafaRay team will fix that one day.

Thanks for the feedback,
oort

I have posted an updated .tar file...

I have added the ability to set the number of threads under Render options. The default is auto (Auto Checked). To use another value remove the check mark and set the number of threads. I set the range to 1 thru 8. Should the upper limit be higher or lower? I am not up to speed on what is available these days.

Also, please test to see that this new option is working. Since I only have a single core machine I cannot do any real world testing.

I added more help info to get people started under Plugin preferences > YafaRay > ?.

I also added a new feature to glass material called "Internal Reflection" that improves the look of glass.

Edit: I almost forgot... I tried to move the "Delete" button but haven't figured it out yet. I think it is an issue with the order of the code.

Thanks,
oort

(03-25-2013, 11:41 PM)oort Wrote: [ -> ]To use another value remove the check mark and set the number of threads. I set the range to 1 thru 8. Should the upper limit be higher or lower?

I don't think you need limit it. Even if users setting more thread than the existing cores the render will act as only the max available core was informed - that was I had noticed here (maybe need more tests).

Quote:Also, please test to see that this new option is working. Since I only have a single core machine I cannot do any real world testing.

It's working.

Quote:I tried to move the "Delete" button but haven't figured it out yet. I think it is an issue with the order of the code.

I can help with this...

On Wiki I notice that Intel has made an experimental 48 core processor. I will set the limit to 100. It is so easy to change this I see no reason to set it to infinity.

Thanks for testing to make sure it worked.

Getting the code right for menus can make you crazy. Even if it compiles right it may not work right... Thanks for any help.

oort

Here is an example of how the new Internal Reflection setting helps glass. The sphere to the left is with Internal Reflection set to 3 and the sphere to the right is with Internal Reflection set to 2 (set value before the new feature was added).

oort

ooohh that's nice. Internal reflection setting. . . I'll have to request that in my rendering app.

(03-23-2013, 11:54 PM)oort Wrote: [ -> ]Yes spaces in file names is a problem just as it is for folders. I guess I should add a note about that as well. Maybe the YafaRay team will fix that one day.

Oort, I think your code must have it fixed.

This is the command line you code displayed in the Erlang console:
c:/Temp/yafaray/bin/YAFARA~1.EXE -f png -dp -pp c:/temp/yafaray/bin/plugins "Chess Table.xml" c:/Temp/Chess Table

I copied the command line generated by your code - that resulted in that error - and then I edited it after pasting in the DOS prompt by surround the image output name with double-quotes:
C:\Users\Micheus>YAFARA~1.EXE -f png -dp -pp c:/temp/yafaray/bin/plugins "c:/temp/Chess Table.xml" "c:/Temp/Chess Table"
and it worked. I got the rendered image.


I still need to check if this can work on Linux.
I download the pre-compiled install but it seems to be necessary to use Blender to use the render.
At this moment I building the yafaray from sources on my VM in order to get a command line version of it. (news soon)

That is very interesting. Should be an easy fix...

Thanks,
oort

Because of this thread...

oort, as your plugin has the ability to save defaults (by using that Save button), I think you could include an item (field) in the dialog enabling the user set the destination directory.
In case this field be empty you just ignore it, otherwise you can concatenate it with the output name parameter you pass to the command line render.
As always, you can count with me if needed.

Micheus,
If the space issue is fixed, do you still think there is a real need for defining a default directory for rendering files? When someone is working on a project, wouldn't they keep the renders in the same folder as the .wings file???

Just wondering, not saying I am against adding such an option...

I thought it would be easy but I am having trouble adding the quotes to the YafaRay command line.

I think the place to add them is at line 3323 of the file you sent me.

Quote: wings_job:render(ExportTS, Renderer,AlphaChannel++"-f "++format(RenderFormat)++" "++ArgStr++" "++filename:rootname(Filename)++" ", PortOpts, Handler)

If you are interested and have the time, I would not be offended in any way if you were to take over the polishing work on the plug-in. You would just need to make sure to add your name to the top of the file to give yourself credits...

At 6157 lines of code, I can understand why you wouldn't want to take this on...

Thanks,
oort