(2017-08-15, 4:40)Travis Cobbs Wrote:(2017-08-14, 21:10)Roland Melkert Wrote: Are you sure LPub is calling the 64 bit version of LDView. The 32 bit version might run out of memory on the larger brick count steps.
A few other things to check. LPub3D recently added support for sending renders to LDView in batches, so LDView can render multiple steps in a row without running a separate instance of LDView for each step. This can greatly improve performance, but might be a contributor to it using more memory and thus crashing. If it's possible to disable that functionality in LPub3D's UI, you might try doing so. Also, LDView has three separate settings for "Memory Usage": low, medium, and high. Setting that to low for the renders might help.
OK, I'll tweak and try some settings.
What does the Process timeout do in the Render preference? It was set to -1.
Jaco van der Molen
lpub.binarybricks.nl
lpub.binarybricks.nl