POV-Ray [plugin] (updated: 2016/Aug/08)

[micheus]

I used the method of removing /EXIT from the argument lines. Maybe it would be good to add that as an option that can be turned off or on in the Plugin Preferences dialog???

Yeah, I could do that too. But, to honest I would like to have an option to avoid the POV-Ray's editor be shown, but that is only present in Linux version.

Interesting that you are able to adjust the Gamma on your monitor.

[tkbd]

Micheus,Thank you for update of Camera

I did test some of camera types.
But,It couldn't be set angle value(the range 1-179) when type of Perspective and Orthographic camera.
The slider is grayed out.
I think that should enable an Angle of the slider (and input field) for Type Camera of Perspective and Orthographic .

See a following reference page,(The example an angle to set 33 for isometric view by Orthographic)
http://www.f-lohmueller.de/pov_tut/camer...era_e1.htm
(This site has very useful informations for PovRay.)

Regard,


And...another report.
The report is part of a log at the time of rendering the Candle model on My MacOSX.
The thread seems to have worked well.
But Gamma setting is 1.0 on dialog, but it seems that actualy use Gamma 2.5.
It was same result as oort's.

> /Applications/povcui/povcui ExampleCandle-POVRay__export.pov +W400 +H300 +FN +oExampleCandle-POVRay_.png +A0.3 +R3 +L/Applications/povcui/include/
Persistence of Vision™ Ray Tracer Version 3.7.0.unofficial4.2.1 Compatible
----------------------------------------------------------------------------
Parser Options
Input file: ExampleCandle-POVRay__export.pov
Remove bounds........On
Split unions.........Off
Library paths:
/Applications/povcui/include/
Clock value: 0.000 (Animation off)
Image Output Options
Image resolution.....400 by 300 (rows 1 to 300, columns 1 to 400).
Output file..........ExampleCandle-POVRay_.png, 24 bpp PNG
Dithering............Off
Graphic display......Off
Mosaic preview.......Off
Continued trace......Off
Information Output Options
All Streams to console..........On
Debug Stream to console.........On
Fatal Stream to console.........On
Render Stream to console........On
Statistics Stream to console....On
Warning Stream to console.......On
----------------------------------------------------------------------------
Parser Time
Parse Time: 0 hours 0 minutes 0 seconds (0.098 seconds)
using 1 thread(s) with 0.098 CPU-seconds total
Bounding Time: 0 hours 0 minutes 0 seconds (0.000 seconds)
using 1 thread(s) with 0.000 CPU-seconds total
----------------------------------------------------------------------------
Render Options
Quality: 9
Bounding boxes.......On Bounding threshold: 3
Antialiasing.........On (Method 1, Threshold 0.300, Depth 3, Jitter 1.00,
Gamma 2.50)
----------------------------------------------------------------------------
Render Time:
Photon Time: No photons
Radiosity Time: 0 hours 0 minutes 1 seconds (1.764 seconds)
using 4 thread(s) with 7.045 CPU-seconds total
Trace Time: 0 hours 1 minutes 15 seconds (75.136 seconds)
using 4 thread(s) with 297.833 CPU-seconds total

tkbd

[micheus]

tkbd, thanks for your the feedback.

But,It couldn't be set angle value(the range 1-179) when type of Perspective and Orthographic camera.
The slider is grayed out.
I think that should enable an Angle of the slider (and input field) for Type Camera of Perspective and Orthographic.

That was on purpose.
I think the Perspective must (continue) to reflect the current Wings3d camera view, as well as the Orthographic one that make it consistent with the current view as we can see in this note found in official doc about the Types of Projection:

Code:

If, in a perspective camera, you replace the perspective keyword by orthographic and leave all other parameters the same, you will get an orthographic view with the same image area, i.e. the size of the image is the same. The same can be achieved by adding the angle keyword to an orthographic camera. A value for the angle is optional.

See a following reference page,(The example an angle to set 33 for isometric view by Orthographic) http://www.f-lohmueller.de/pov_tut/camer...era_e1.htm
(This site has very useful informations for PovRay.)

I know this site. I learned much of POV-Ray using it as reference.

But Gamma setting is 1.0 on dialog, but it seems that actualy use Gamma 2.5. It was same result as oort's.

I considered the discussion about this item finished.
Note, that gamma is related to AA (you read that in the log). I also illustrated its use in the previous post I did for oort as well as I added references to the way the gamma is managed by POV-Ray - and there are some options, but the only important one is that we are already using and that to be specific assumed_gamma.
What I thought related to that was to add an option to enable POV-Ray to save the image using the sRGB gamma option.
Please see the links in my answer to oort in the post #106

[oort]

tkbd,
The Gamma you see listed as 2.5 in the Pov-Ray window is a different Gamma from the one that we set in the Wings3D dialog. Do a render with a setting of 1.0 and then one with a setting of 2.5. You will see that this setting is working as it should be...

Micheus,
Would it be possible to add a separate Isometric Camera mode? I think that is what tkbd was asking for???

oort

[micheus]

oort, I think you means tkbd and not Dimitri.

Would it be possible to add a separate Isometric Camera mode?

Isn't that the same view we get with the Wigns3D camera reset?
Or better, the angle either for Perspective or Orthographic will just work like a zoom In/Out, so use the Wings3D camera give us more precision.

[oort]

I guess am not awake enough yet. Sorry tkbd I have corrected my previous post.

I think Isometric is a skewed view of the image. Just as Fish Eye changes the way the rendered image appears... But I am not sure...

oort

[tkbd]

Micheus,Thank you for reply.
I validated to the angle by changing the value.
Certainly as you said,it was been used Wings3D's camera settings.

So I noticed two things.

The first one.
In currently My Wing3D's Camera settings is...
Field of view is 45.00022

PovRay Camera Angle = Field of view

But,In other hand,exported .Pov file by PovRay Plugin is here
The camera angle is 57.822402 degree

----------------------------------------
camera{
perspective
location camera_location
right (400 / 300) * x
up y
angle 57.822402
sky <0.557745, 0.744778, 0.366370>
look_at <-0.223504, 0.117677, -0.181860>
}
----------------------------------------

I tried with other values.
Wings3DFov :140.699903
PovRay camera angle:149.737392
The difference in the two numbers will appear.


The Second one.
If the value set by purposely,I suggest that it is an appropriately information should be feedback to User through the user-interface.
Only grayed-outed slider cause a risk of being misunderstood to the User.
Because currently, the gray-out input box display still remain different value(180) than actual exported result.

For example of the information feedback.(ex. case of Fov:57.8 degree)
In the case of Perspective and Orthographic type , It should layout to a message string instead of the grayed-out-slider's place .
"In this Camera, Using an angle as FOV:57.8 degree from Wings3D camera setting"
How about you?


About Gamma.
Thanks for advice,a pointer for a comment and links.
Recent PC and Mac takes the same Gamma value, isn't it?
I learned for the first time.
I'm going to try to read it well.

Thanks,
tkbd

[micheus]

The first one.
In currently My Wing3D's Camera settings is...
Field of view is 45.00022

PovRay Camera Angle = Field of view

But,In other hand,exported .Pov file by PovRay Plugin is here
The camera angle is 57.822402 degree

You can see the origin of this difference in the way it is computed by the plugin (I didn't changed that): here
It makes the adjust based in the width x height you define. So, maybe if you use the new camera preset - Viewport - you probably will get a closer value.

You can get more information about camera parameters used by POV-Ray in this link.

The Second one.
If the value set by purposely,I suggest that it is an appropriately information should be feedback to User through the user-interface.
Only grayed-outed slider cause a risk of being misunderstood to the User.
Because currently, the gray-out input box display still remain different value(180) than actual exported result.

I had thought about to hide it for these options and now I'm sure that it's the best option.

About Gamma.
Thanks for advice,a pointer for a comment and links.
Recent PC and Mac takes the same Gamma value, isn't it?

I cannot answer that.

[tkbd]

You can see the origin of this difference in the way it is computed by the plugin (I didn't changed that): here
It makes the adjust based in the width x height you define. So, maybe if you use the new camera preset - Viewport - you probably will get a closer value.

Thanks to,I was able to control to the value of the Angle in convincingly.
(It was to pay attention to the PovRay's export image size and the ratio of Negative from Wings Camera.)


--------
tkbd

[micheus]

I'm working in a menu addition to use the latest render plugin and its options, including the used file name.


... and it can be extended to any other Render plugin since there is no need to update the Wings3d core.