(2017-01-08, 21:54)Walt White Wrote: Hi,

I have the same problem Knud experienced.  Using POV for rendering in LPub3D 2.0.19 generates the same "Failed to set render options" error message he reported, when asked to render an LDR file containing a single steering pulley piece.  

POV-Ray 3.7 by itself can render its example woodbox.pov fine.  And both Stud.io and LDCad 1.6 Beta 1a can call POV and successfully render that one piece steering pulley LDR file.  Only LPub3D fails.

Looking at the earliest fail point in the LPub3D log file, it reports that it cannot find the steering pulley 3736.dat in the LDR file, and very helpfully reports exactly where it is looking.  But 3736.dat is clearly in the complete.zip file being examined.  See screenshot below.

Trevor suggested to Knud that the Preference for "Ldraw Root Directory" shouldn't be in the Program Files folder, even though the AIOI put it there.  I think the confusion is over the word "Root," and whether it really means "Part Library."  I tried setting the LPub3D preference to the LDraw folder containing the part library, and there was no change to the failure reported in the log file.

Any and all ideas are welcome for solving this problem.  I haven't figured out how to attach thumb size images, they are full size in this edit mode, and it looks like I'll have to post again to get the last two files, <sigh>

Walt

Attached are:
OneSinglePiece.ldr
csi.ldr.pov — POV temp file generated during failed LPub3D session
OneSinglePiece.pov — Successful POV generated by LDCad
NotFound.png — Log report 3736 not found
3736dat.png — 3736.dat does exist in complete.zip
Messages.png — POV-Ray failure messages
LDView.png — LDView render and POV-Ray path
LPub3D-GeneralPref.png — LPub3D General Preferences
POV-script.png — Successful POV settings using LDCad
Stud.io.png — Successful POV settings using Stud.io

(2017-01-08, 21:56)Walt White Wrote:

(2017-01-08, 21:54)Walt White Wrote: <snip>

Trevor suggested to Knud that the Preference for "Ldraw Root Directory" shouldn't be in the Program Files folder, even though the AIOI put it there.  I think the confusion is over the word "Root," and whether it really means "Part Library."  I tried setting the LPub3D preference to the LDraw folder containing the part library, and there was no change to the failure reported in the log file.

Any and all ideas are welcome for solving this problem.  I haven't figured out how to attach thumb size images, they are full size in this edit mode, and it looks like I'll have to post again to get the last two files, <sigh>

Walt

</snip>

Last two files should be attached

(2017-01-09, 23:59)David Manley Wrote:

(2017-01-08, 21:56)Walt White Wrote: Last two files should be attached

Hi Walt,

I downloaded your sample file OneSinglePiece.ldr and ran LPub3D to see if;
(a) I would experience the same behaviour and, if so,
(b) whether I could offer some suggestions for resolution.

I can firstly confirm that I did experience similar behaviour, though the behavior I experienced aligns to that of Knud's (i.e. POV-Ray displaying an error message "IO Restrictions prohibit write access ...") rather than your error message (i.e. "Could not find file ...").

Digging into this a little, the "IO Restrictions prohibit write access ..." appears to come about from a security check within POV-Ray. I verified this in two ways;
1) opening POV-Ray as a separate executable, I set the menu item "Options | Script I/O Restrictions" to "No Restrictions" and then exited the application. The next time LPub3D invoked POV-Ray for rendering, it successfully generated the desired images.
2) I opened POV-Ray as a separate executable a second time, set the menu item "Options | Script I/O Restrictions" to "Allow Read, Restrict Write" and edited the Pov-Ray engine ini file pvengine.ini (located in the directory "%USERPROFILE%\Documents\POV-Ray\v3.7\ini") to add an appropriate directory root to the [Permitted Output Paths] section (refer to http://wiki.povray.org/content/Documentation:Windows_Section_2.1#Low-Level_Configuration for more details about this). In my case, I added the directory "D:\users\djm\personal\2017\LEGO" as a permitted path since I had your LDR file within a sub-directory of this path.

Now while the above may not resolve the issue you are experiencing, are you able to post two things;
1) the value you have for "Path" within the "LDraw Root Directory" on the "General" tabbed sheet which is displayed when within LPub3D you select the menu item "Configuration | Preferences". For example, my value is set to D:\Users\Vista\Public\Documents\LDraw. 
2) the value of the environment variable LDRAWDIR. For example, my environment variable value is set to D:\users\Vista\Public\Documents\LDraw
Knowing these values may help in further diagnosis.

Regards,

David

(2017-01-11, 0:19)Walt White Wrote: Thanks for investigating this puzzle.

My Path to the LDraw Root Directory was:
C:\Program Files (x86)\LDraw

I tried changing it to:
C:\Users\Public\Documents\LDraw 
so it matches exactly my LDRAWDIR environment variable:
C:\Users\Public\Documents\LDraw
but it still failed.

I already had the "Options | Script I/O Restrictions" set to "No Restrictions" but went ahead and added the folder containing the .LDR file to the [Permitted Output Paths] in pvengine.ini as suggested, but it still fails.

I haven't considered file permissions as a problem because LPub3D successfully generates six files in the "tmp" sub-folder:
csi.ldr
csi.ldr.pov
main.ldr
pli.ldr
pli.ldr.pov

For me, the clue is that both of the .POV files contain sixty eight lines of:
// Empty model
so LPub3D never generates anything in the "parts" sub-folder, which explains why POV-Ray fails with the message that it can't find what it is looking for in that "parts" sub-folder.

And the LPub3D log file clearly states why it can't generate the required file:
@ln 1014 "Item [3736.dat] not in the LPub3D archives. C:/Users/Walt/AppData/Local/LPub3D Software/LPub3D/libraries/lpub3dldrawunf.zip C:/Users/Walt/AppData/Local/LPub3D Software/LPub3D/libraries/complete.zip"

The puzzle for me is why LPub3D can't find that 3736.dat file in complete.zip when my Windows 10 machine clearly shows that .DAT file in that .ZIP file. I've tried running LPub3D as an administrator and it still fails.

Walt

(2017-02-03, 6:18)David Manley Wrote:

(2017-01-11, 0:19)Walt White Wrote: Thanks for investigating this puzzle.

My Path to the LDraw Root Directory was:
C:\Program Files (x86)\LDraw

I tried changing it to:
C:\Users\Public\Documents\LDraw 
so it matches exactly my LDRAWDIR environment variable:
C:\Users\Public\Documents\LDraw
but it still failed.

I already had the "Options | Script I/O Restrictions" set to "No Restrictions" but went ahead and added the folder containing the .LDR file to the [Permitted Output Paths] in pvengine.ini as suggested, but it still fails.

I haven't considered file permissions as a problem because LPub3D successfully generates six files in the "tmp" sub-folder:
csi.ldr
csi.ldr.pov
main.ldr
pli.ldr
pli.ldr.pov

For me, the clue is that both of the .POV files contain sixty eight lines of:
// Empty model
so LPub3D never generates anything in the "parts" sub-folder, which explains why POV-Ray fails with the message that it can't find what it is looking for in that "parts" sub-folder.

And the LPub3D log file clearly states why it can't generate the required file:
@ln 1014 "Item [3736.dat] not in the LPub3D archives. C:/Users/Walt/AppData/Local/LPub3D Software/LPub3D/libraries/lpub3dldrawunf.zip C:/Users/Walt/AppData/Local/LPub3D Software/LPub3D/libraries/complete.zip"

The puzzle for me is why LPub3D can't find that 3736.dat file in complete.zip when my Windows 10 machine clearly shows that .DAT file in that .ZIP file. I've tried running LPub3D as an administrator and it still fails.

Walt

Walt,

I think that the error you encountered may be due to a space somewhere in your directory path. Refer to https://forums.ldraw.org/thread-22020.html for a possible explanation.

Are you able to try renaming you directory path, replacing any space in the directory name with an underscore? Please post the outcome of attempting this i.e. whether or not it resolved the issue you encountered.

Regards,

David