RE: LPub3D 2.0.9 Released
2016-09-06, 8:52 (This post was last modified: 2016-09-06, 9:54 by Trevor Sandy.)
2016-09-06, 8:52 (This post was last modified: 2016-09-06, 9:54 by Trevor Sandy.)
(2016-09-06, 4:56)David Manley Wrote: 1) could LPub3D, when invoking LDView, use the ""-extrasearchdirs" to pass the directories required for the faded parts?
2) should LPub3D generate the instructions including the faded motor when using LDGLite as the renderer or is this a known shortcoming from using
Regards,
David
I just read your last post.
I have been working with Travis to extend the capabilities of LDView. Searching the extra search directories, defined through the LDView GUI, from a command call is one of the updates available to me but not yet released publicly I believe. Sorry, I completely forgot about this when I merged that enhancement to production. From your last post, it looks like you are able to invoke the extra search directories defined from the LDView GUI via LPub3D command call using LDView 4.2. For me, calls on Window 10, did not succeed to use the GUI defined extra search directories; hence the updated version of LDView (4.3) I am currently working with.
To Answer your questions:
From LPub3D 2.1, LDView will be included in the distribution as a 3rd-party renderer as is currently the case for L3P and Ldglite. All required search directories will be automatically communicated between LPub3D and the 3rd Party renderers.
Yes, LPub3D should generate the instructions including the faded motor when using LDGLite as the renderer. This is working as expected on my environment with and without ldrawini. Be sure your are using the latest version of LDGlite or that your preferences are mapped to the version distributed with LPub3D. The LPub3D version can be found at C:\Program Files [(x86)]\LPub3D\3rdParty\ldglite1.3.1_2g2x_Win\ldglite.exe
I'll take a look at your log and example.
Cheers,
Cheers,