Trevor,
I've identified what I believe is a bug when using POV-Ray for rendering images in LPub3D. When the directory path to the LDraw file does not contain any spaces, POV-Ray is invoked successfully and the appropriate images rendered. An example of the command line generated by LPub3D to invoke POV-Ray (from the POV-Ray log) is:
However, when the directory path contains a space, POV-Ray generates an error (from the POV-Ray log);
Note the difference between the respective +O command line argument quoting. The first (without spaces)
compared to the second )with spaces);
I believe the issues may be the double quotes around the entire +O parameter values, causing POV-Ray not to see the +O as intended.
Regards,
David
I've identified what I believe is a bug when using POV-Ray for rendering images in LPub3D. When the directory path to the LDraw file does not contain any spaces, POV-Ray is invoked successfully and the appropriate images rendered. An example of the command line generated by LPub3D to invoke POV-Ray (from the POV-Ray log) is:
Code:
Preset INI file is 'D:\USERS\VISTA\DJM\DOCUMENTS\POV-RAY\V3.7\INI\QUICKRES.INI', section is '[800x600, AA 0.3]'.
Rendering using command line '+ID:\users\djm\personal\2017\LEGO\BUILDI~1\DACHSH~1\LPub3D\tmp\PLILDR~1.POV
+OD:\users\djm\personal\2017\LEGO\building_instructions\dachshund\LPub3D\parts\4589_128_1753_150_DPCM_1_23_-45.png +W1753 +H1240 +UA +LD:\PROGRA~1\LDraw\LGEO\lg
+LD:\PROGRA~1\LDraw\LGEO\ar +A'.
Rendering with 2 threads.
Persistence of Vision(tm) Ray Tracer Version 3.7.0.msvc10
This is an official version prepared by the POV-Ray Team. See the
documentation on how to contact the authors or visit us on the
internet at http://www.povray.org/
However, when the directory path contains a space, POV-Ray generates an error (from the POV-Ray log);
Code:
Preset INI file is 'D:\USERS\VISTA\DJM\DOCUMENTS\POV-RAY\V3.7\INI\QUICKRES.INI', section is '[800x600, AA 0.3]'.
Rendering using command line '+ID:\users\djm\personal\2017\LEGO\BUILDI~1\DACHSH~1\LPub3D\tmp\CSILDR~1.POV "+OD:\users\djm\personal\2017\LEGO\building
instructions\dachshund\LPub3D\assem\main_10_whole_rotated_060-00-head_1_0_0_0_1_0_0_0_1_1_1753_150_DPCM_1.png" +W1753 +H1240 +UA +LD:\PROGRA~1\LDraw\LGEO\lg
+LD:\PROGRA~1\LDraw\LGEO\ar +A'.
Persistence of Vision(tm) Ray Tracer Version 3.7.0.msvc10
This is an official version prepared by the POV-Ray Team. See the
documentation on how to contact the authors or visit us on the
internet at http://www.povray.org/
<snip>
</snip>
Could not find file '+OD:\users\djm\personal\2017\LEGO\building
instructions\dachshund\LPub3D\assem\main_10_whole_rotated_060-00-head_1_0_0_0_1_0_0_0_1_1_1753_150_DPCM_1.png.ini'
-
Cannot open INI file '+OD:\users\djm\personal\2017\LEGO\building
instructions\dachshund\LPub3D\assem\main_10_whole_rotated_060-00-head_1_0_0_0_1_0_0_0_1_1_1753_150_DPCM_1.png'.
-
Cannot process command-line at ' +W1753 +H1240 +UA +LD:\PROGRA~1\LDraw\LGEO\lg +LD:\PROGRA~1\LDraw\LGEO\ar +A' due to a parse error.
This is not a valid command-line. Check the command-line for syntax errors, correct them, and try again.
Valid command-line switches are explained in detail in the reference part of the documentation.
Failed to start render: Failed to parse command-line option
Note the difference between the respective +O command line argument quoting. The first (without spaces)
Code:
+OD:\users\djm\personal\2017\LEGO\building_instructions\dachshund\LPub3D\parts\4589_128_1753_150_DPCM_1_23_-45.png
compared to the second )with spaces);
Code:
"+OD:\users\djm\personal\2017\LEGO\building
instructions\dachshund\LPub3D\assem\main_10_whole_rotated_060-00-head_1_0_0_0_1_0_0_0_1_1_1753_150_DPCM_1.png"
I believe the issues may be the double quotes around the entire +O parameter values, causing POV-Ray not to see the +O as intended.
Regards,
David