TheBounty Renderer (rewrite for wxWidgets) - Printable Version +- Wings 3D Development Forum (https://www.wings3d.com/forum) +-- Forum: Wings 3D (https://www.wings3d.com/forum/forumdisplay.php?fid=1) +--- Forum: Design & Development (https://www.wings3d.com/forum/forumdisplay.php?fid=6) +--- Thread: TheBounty Renderer (rewrite for wxWidgets) (/showthread.php?tid=440) |
RE: TheBounty Renderer; my fork of YafaRay project - povmaniac - 10-27-2013 (10-27-2013, 12:30 PM)micheus Wrote: The validator value in the dump is set by range_1(sss_depth) -> {1.0,50.0}; and there was a integer constant being assigned to the field. But sss_depth need a integer value.. not float. Code: println(F, Is it possible to eliminate all the DEF and to define these values when we define the interface? Same for the ranges.. Code: {vframe, [ Btw.. I make test for DOF, based on Kerkythea code. RE: TheBounty Renderer; my fork of YafaRay project - micheus - 10-27-2013 (10-27-2013, 12:59 PM)povmaniac Wrote: But sss_depth need a integer value.. not float.Then, the line with command range_1(sss_depth) -> {1.0,50.0}; needs to be changed to: {1,50}. povmaniac Wrote:Is it possible to eliminate all the DEF and to define these values when we define the interface?Sorry, I didn't understand this quetion. RE: TheBounty Renderer; my fork of YafaRay project - povmaniac - 10-27-2013 Code: Search "DEF_SSS_DEPTH" (2 hits in 2 files) All correct to integer mode..But obtain an error: Code: Dump written 2013-10-27_14-17 ?? RE: TheBounty Renderer; my fork of YafaRay project - micheus - 10-27-2013 The problem now is the value previously saved to the preferences file. Open it and look for sss_depth, then change 15.0 to 15. Everyone here testing the code will need do that. RE: TheBounty Renderer; my fork of YafaRay project - oort - 10-27-2013 It was an error in my original code... Quote:println(F, "<sssDepth ival=\"~w\"/>",[SSS_Depth]), I used ~w when I should have used ~.10f in the above line. I guess I never tested the reset button... oort RE: TheBounty Renderer; my fork of YafaRay project - micheus - 10-27-2013 povmaniac, I forgot to add the option to remember the last output format selected. Tomorrow I'm going to fix it. sorry. RE: TheBounty Renderer; my fork of YafaRay project - povmaniac - 10-27-2013 You can repeat the pull request, please. Is not work in my PC. I create an branch named micheus_exp. Use it, please RE: TheBounty Renderer; my fork of YafaRay project - Neon22 - 10-27-2013 (10-27-2013, 12:30 PM)micheus Wrote: EDIT: I just saw that the exporter code (export_camera/3) is already using the distance to Aim too. So, maybe would we just remove this field from the dialog? I'm not sure if you're suggesting we don't see the distance in the Render UI. I'd like to see the distance because at small f-stops the depth of field is very narrow. So I'd like to be able to adjust it a little. I agree it would be very useful to have it set to current aim point but I want to be able to adjust it. RE: TheBounty Renderer; my fork of YafaRay project - micheus - 10-27-2013 (10-27-2013, 06:18 PM)povmaniac Wrote: I create an branch named micheus_exp. Use it, pleaseI can do that only tomorrow. Neon22, I'll suggest a code for that too. RE: TheBounty Renderer; my fork of YafaRay project - povmaniac - 10-28-2013 Micheus.. Your change not work.. Thebounty need the image format, not only in the command line, also is need 'inside' exporter code, for choose 'image_handler()' fuction in the exported xml file. Btw is work for render, but obtain an error fir exporter to xml: Code: ERROR: Failed to export: My idea is to choose the file format in the render panel, be already to export to xml, or for render. If is posible, jump this step.. Also, for sync with other exporters.. Thanks for you work!! |