M2m

I'm using macOS Mojave 10.14.6 and have no problems in using the new parts. I do as follows: 1) Go to Folder "/Users/myusername/Library/Application\ Support/LEGO\ Company/LEGO\ Digital\ Designer/" and extract the db.lif file in that folder using JrMasterModelBuilders LIFExtractor.py python script. This will extract db.lif to a new folder called db in the above mentioned folder - "/Users/myusername/Library/Application\ Support/LEGO\ Company/LEGO\ Digital\ Designer/db/" After that rename the file db.lif to somethinglike db_backup.lif 2) Get the new parts from this topic: 3) Extract the parts packs (i.e. Primitives.rar) 4) Add and replace the files (not the folders) in the db folder and its subfolders with the files from the parts packs. For example in the parts pack there is a "Primitives" folder, copy all files from there to the ..../db/Primitives folder. Same with the "Primitives/LOD0" folder and so on.

Nice car. But looks like a big step to go to Millenium Falcon - Enjoy :) !

It may help if you upload your model for checking, even so it is a problem with bluerender. what also may help is to delete parts of the model and then safe it as a new file to find out which particular part is the one making trouble.

Fixed flexparts. Seems I having a caching issue - or rather a copy by reference issue, so once i turned off caching of parts all flex parts work.

Yeah I agree. I am not entirely happy with the colors. Could be a HDRI issue, could be a color linearization issue, maybe both. Anyway thanks for the kind feedback. And I am looking to improve it.

I made quite some updates since my last post: transparent material improvements. changed handling of material = 0 in a part. Now for 0 the 1st material (the base material of a part) will be chosen and not the previous material of the subpart before. Added reading of correct focus distance from lxf file camera, allowing for correct depth-of-field rendering. DB folder support for custom bricks in addition to db.lif support Get it here: https://github.com/sttng/LegoToR/releases/tag/v0.5.1.1

That looks ... AWESOME !!

Where is is Apu ? Just kidding these are great ! On another note. Can maybe someone fix the flex in the original LDD Part 63037 - Outer Cable 88mm. It seems this comes as 'botched' in the original LDD.

Ok I'm indeed parsing building instraction steps now - if the lxfml file has those of course. https://sttng.github.io/LDD-Webviewer/ldd.html?scene=https://raw.githubusercontent.com/sttng/LDD-Webviewer/master/Redbeard.lxfml&step=0 EDIT: OK I found out my recursion for generating the steps is crap , so basically quite some steps are omitted and/or place wrongly. Apologies.

OK I'm now parsing the building instructions (BI) element, too and I think I have it working correctly meaning I get the relevant Camera and Bricks for each step. That means: Step 1, Brick 1, Cam1 Step2, Brick1, Brick2, Cam1 Step2, Brick1, Brick2, Brick3,.... and so on. Now I 'just' have to create a function which creates a 'new' lfxml file with the relevant Step data.... let's see

Indeed. My fault: 11262 is the head. 24319 is the torso..... How comes I missed that

The result would be that these 2 (unrelated) parts can connect to each other. Not too bad. But yeah, some alignment wouldn't hurt.

I would be so happy if we could get the chicken minifigure in LDD https://www.bricklink.com/v2/catalog/catalogitem.page?M=col135#T=S&O={"iconly":0}

I appreciate your great efforts for this ! Keep it up ??

Thanks everyone. My current priority list is as follows: Fix flex parts support lxf files. After everything is processed correctly I certainly want to work on performance. Many thanks to @Lasse D for your link to ldraw and the ‘story’ of your webgl renderer. It’s a good read with very nice ideas. I will certainly have a look at your code I started with this project 8 days ago and I haven’t done much in JavaScript before and of course never used Three.js either. It has been quite an adventure. So far I process everything sequentially (which is deprecated in JS - you might see the warnings in the browser console) which of course degrades performance quite a lot. But I’m still quite struggling with the ‘new’ concept of everything running asynchronous.

Yeah most of the time cross Plattform you end up in command prompt / terminal versions of software which aren’t so end-user friendly.

I guess 2 reasons: 1) Its easier for Stephan 2) In case of a botched part update you are sure to have the old and still working version. Still I agree its a little tedious. But then its also not too bad and too much effort. I started to make a copy of all 'releases' into one git - it doesn't include the latest one yet. I mostly do it for myself: https://github.com/sttng/LDD-New-Parts

As title, I used my free-time and threw a LDD (lxfml) webvier (WebGL, Three.js based) together. This is a proof-of-concept and this means I wouldn't even consider this beta-software as it has a log of bugs and room for improvement (meaning it takes ages to load a file). What works: Loading of .lxfml files from LDD (stored somewhere on the internet, no local file loading yet) Textures and decals The 1st flex part (and only the 1st one) Supports some new parts What is bad: Doesn't load .lxf files yet, these are zipped and I can't process zip files properly It is painfully slow, even for small builds (don't even think about loading the UCS Millennium Falcon, unless you don't care to wait for hours around 15min and see your browser crash) More then one flex part No transparent material Code here: https://github.com/sttng/LDD-Webviewer Tryout: https://sttng.github.io/LDD-Webviewer/ldd.html https://sttng.github.io/LDD-Webviewer/ldd.html?scene=https://raw.githubusercontent.com/sttng/LDD-Webviewer/master/Redbeard.lxfml https://sttng.github.io/LDD-Webviewer/ldd.html?scene=https://raw.githubusercontent.com/sttng/LDD-Webviewer/master/new_parts.lxfml not for the faint hearted - UCS Falcon: https://sttng.github.io/LDD-Webviewer/ldd.html?scene=https://raw.githubusercontent.com/sttng/LDD-Webviewer/master/75192.lxfml

I’m using a Mac and have no problem with using the new bricks. Just extract the db.lif file. This will create a folder called db. Rename the db.lif file to something like #db.lif (so LDD won’t load it) and place the relevant files from the custom bricks into the respective sub folders of the db directory.

Great explanation on edge detection. Would you know any reason for these outlines to be there other then being ‘pretty’. Is there any practical use ?

Seems to be better then my LIFCreator.py (which is quick, dirty, slow and RAM intensive - on windows)

I guess Excel / csv table / Google docs tracking information like collision, culling, outlines, etc might be good. This could / should then also be part of the release pack data.

The LDD file of the scene: https://github.com/sttng/LDD/blob/master/assets/phil_in_meditation03.lxf

I used the wall for my recent build and I’m quite happy with the result.

Yeah sure. Also might add some grey/green colors at the bottom for 'moss' or stuff.