Allard van Efferen

This BuildMod feature is great, however I feel it is pretty sensible to cashed data or something like it. I am not really a software developer. When I run LPuB3D latest version this message shows up on different occasions where I use the BuildMod statements and all are formulated the same against the directions given. In the attachment an example. I probably overlook something, all the help is appreciated.

What I normally do is moving the unofficial parts I need to the official parts folder. I also have trouble to get the unoffical parts shown correctly from the other folders.

New attachment with snippet of model code of end of the model.

Hello, I have big building instruction on A2 size and 267 pages. I reduced it already by moving out subassemblies because LPub3D shows inconsistent behavior with bigger instructions for me. Problem now is that when the model is initially loaded LPub3D indicates 264 pages. When I jump to page 264 it changes to the actual size of 267 pages. I can't found out what causes this two pronged behavior. Problem is that even when you start the pdf-generation from page 267 the pdf will only contain the first...

Hello Trevor, I more or less gave up and changed from Native back to LDview and now al works as expected again.

Hello Trevor, After some tinkering I decided to clearout my PC and reinstall both ldraw package and LPub3D 2.3.7. with this install file: LPub3D-2.3.7.0.1195_20190327.exe. When I change the CDF I get this error with a fresh new file created in MLcad? "Could not write to Native CSI image 'C:/Users/jan/Legostuff/Lego/buildinginstructions/testclear/LPub3D/Assem/untitled_1_0_0_0_1_0_0_0_1_1_1_1240_150_DPCM_300_30_23_45.png': Image is empty. 'What can cause this error message?

Hello Trevor, Thanks for your reply. Any suggestion where I need to look to fix this in my situation? I use a Microsoft surface 3. Regards Allard van Efferen M: +31 629 535 916 On 28 Mar 2019, at 00:08, Trevor Sandy trevorsandy@users.sourceforge.net wrote: I'm not able to reproduce the behaviour you are experiencing. See the following shots. Do not mind the displayed application version - it's v2.3.7 but I'm using my development environment. Cheers, Version 2.3.6 changing Camera Distance Factor causes...