I may have missed something, but how do you change the LDCad file format to one that can be used by the instruction building / publishing software?

OR - is there one that uses the LDR file direct?

Thanx
Ed

I am searching for the Parts DAT  from The Porsche GT3 RS

23800 Wheel Porsche

23799 Tyre 81,6x44

26530 5X15X2 PANEL WHEEL ARCH w. Print left


26531 5X15X2  PANEL WHEEL ARCH w. Print right


24118 5X15X2 PANEL WHEEL ARCH only Printing


24119 3x7x2   Bricks, Special Circles And Angles


23801 WHEEL BEARING BACK W/ CROSS HOLE


26287 CROSS AXLE, EXTENSION, 3M


Thanks
Thorsten

Greetings - just wanted to say Travis' guidance to render images with LDView using the -SaveSnapshots=1 switch is showing a 75% increase in performance. This configuration renders multiple files using a single call. So with this 'Single Call' configuration on LPub3D, the entire parts list/bom is rendered with a single call and step models on a multi-step page are also rendered with a single call.

I have to add that this enhancement was quite complicated. Image attributes (height and width) are critical to the lowest level of LPub3D functionality and are processed on the fly as page components are constructed so to not generate images on the fly - so they can be included in a single call - was most complicated. Especially to design something that was not more expensive than the current performance cost. It's not good to rob Peter to pay Paul. Anyhow, I believe what I came up with is a good design and the results clearly show a performance credit.

So without further adieu, here is the evidence log for the model file below. (Model file credit: Philo):

Single Flat Page - LDView Single Call
 "LDView"  PLI single render call took  4660 milliseconds. 
 "LDView"  CSI single render call took  923 milliseconds  for step  1  on page  1 
 
Single Flat Page - LDView normal Call
 "LDView"  PLI render call took  21474 milliseconds. 
 "LDView"  CSI render call took  1017 milliseconds  for step number  1  on page number  1

You can see the overall elapsed time was 22,491 milliseconds for the normal call where every bom part is rendered by an individual call. With a single call for the entire bom, the overall elapsed time is reduced to 5,583 milliseconds. 

Test model used:
   

Very big thanks to Travis for his guidance.

P.S. The next release of LPub3D is imminent - wrapping up testing.
Cheers !

Hi folks,

Are the tiny stickers with the Ferrari logo (as seen in set 10248 and other past Ferrari models) made or is someone working on them as sticker or part?
I am aiming at stickers 2, 3 and 7. 

Hi all,

Looking for the Stormtrooper Pauldron Cloth. Hopefully it's in lDraw aleady, and as usual, I can't find it?

http://alpha.bricklink.com/pages/clone/c...=4#T=C&C=4

Thanks!

Hi,

I just moved to a new flat and did a hardware / VR / system upgrade on my desktop machine as well.
The upgrade inlcuded a new powerful GPU configuration (2x NVIDIA GTX 1080, SLI).
Currently, there are no open source linux drivers for the GPU, yet.

I need about a week to play a little bit with my new workstation / VR headset and will then continue to work on LDPartEditor.
Of course, I will not raise the hardware requirements for LDPE... :)


Cheers

Nils

I'm not sure if this has been mentioned before, but the new forums don't seem to have a favicon. The old ones had the blue brick favicon. For reference, I'm in Firefox; not sure if that matters.

Hi!

23443 is a new part for 2016 and AFAIK the part number just became known a few days ago. I would love if anyone did this!

http://brickset.com/parts/6143318

I have a question / discussion point regarding 64 bit programs and the AIOI.

I noticed (far as i know) the AIOI only uses the program files (x86) folder to install programs. Is this also true for 64 bit programs or are there currently none?

I'm thinking about this as LDCad 1.6 will be available in a 64 bit windows version  (upgraded to a minGW64 that finally supports the native windows threading model) and I'm considering the setup options for this change.

The main goal here is to also support the AIOI install location so it can upgrade if needed.

Wedo/Wedo 2.0 Sets