Jump to content

Custom LDD bricks and fixes

Equilibrium
 Share

Recommended Posts

Stephan

Stephan

Posted
Posted
  On 5/23/2020 at 10:06 PM, PicnicBasketSam said:

The Dropbox link for 200522v2 goes to a 404 Page Not Found error.

Expand  

Fixed.
 

 

  On 5/23/2020 at 10:06 PM, PicnicBasketSam said:

Download was successful from GitHub but part 30571

Expand  

Fixed.
 

 

  On 5/23/2020 at 10:06 PM, PicnicBasketSam said:

Additionally, parts 48165 Wedge 3x3 Sloped Right and 42862 Wedge 3x3 Sloped Left have a boundary problem

Expand  

Jester will look into that.

jester

jester

Posted
Posted (edited)
  On 5/24/2020 at 5:11 AM, Stephan said:

Jester will look into that.

Expand  

Fixed and re-upload only xml files

Also corrected and re-uploaded 30010 (xml) - there were connection problem - fixed

Edited by jester
M2m

M2m

Posted
Posted (edited)

35660 - LEGO Hair with Cap has a bug in the .g file. Typically .g files have the following mesh type: Standard mesh (Hex: 0x3A Dec: 58),  and then the additional g1, g2, g3, files may have a textured mesh type (Hex: 0x3B Dec: 59). Anyway in this case 35660.g has (wrongly) a mesh type of 0x3B and also texture coordinates. While LDD will not complain about this, this is not according to Legos 'internal' standards.

Edited by M2m
jester

jester

Posted
Posted (edited)
  On 5/25/2020 at 5:23 AM, M2m said:

Fixed 20460 and 20461

https://raw.githubusercontent.com/sttng/LDD-New-Parts/master/Primitives/20460.xml

https://raw.githubusercontent.com/sttng/LDD-New-Parts/master/Primitives/20461.xml

They missed correct values for faces and subMaterialRedirectLookupTable

Expand  

How it can have 5 decorations faces, if i put only 2 - bottom and top

Or you corrected the original parts?

  On 5/25/2020 at 2:59 PM, M2m said:

35660 - LEGO Hair with Cap has a bug in the .g file. Typically .g files have the following mesh type: Standard mesh (Hex: 0x3A Dec: 58),  and then the additional g1, g2, g3, files may have a textured mesh type (Hex: 0x3B Dec: 59). Anyway in this case 35660.g has (wrongly) a mesh type of 0x3B and also texture coordinates. While LDD will not complain about this, this is not according to Legos 'internal' standards.

Expand  

Are you able to open G files? How?

Edited by jester
JGuy

JGuy

Posted
Posted

@jester are you able to explain how to convert .g to a .obj file? I am trying but can't figure out how to convert from .lxfml to .3dxml. Is 3DVIA Printscreen required for that?

jester

jester

Posted
Posted
  On 5/25/2020 at 5:14 PM, JGuy said:

@jester are you able to explain how to convert .g to a .obj file? I am trying but can't figure out how to convert from .lxfml to .3dxml. Is 3DVIA Printscreen required for that?

Expand  

Check the previous page
I gave the tutorial and video too

M2m

M2m

Posted
Posted (edited)
  On 5/25/2020 at 4:16 PM, jester said:

How it can have 5 decorations faces, if i put only 2 - bottom and top

Or you corrected the original parts?

Expand  

Good point ! I may be wrong here. Your 20460 comes with 2 parts (g, g1). The original 20460 comes with 5 parts (g, g1, g2, g3, g4). If I want to use yours should I delete all original g, g1, .., g4 files ?

In that case your original xml files was correct. Sorry my bad. I just overwrote the g and g1 file with yours, keeping Legos g2, g3 and g4.

  On 5/25/2020 at 4:16 PM, jester said:

Are you able to open G files? How?

Expand  

I am using a hex editor to look at the raw data (0xED is the name of the editor). The .g file format is fairly well documented here: https://github.com/Polymaker/ldd-modder/blob/develop/Documentation/G (mesh) file structure.md

You can check lego's own .g and g1, g2, g2, gX files for comparison. The non-flex .g files always have a standard mesh (Hex: 0x3A Dec: 58) indicator according to my experience. The g1, g2, g3, ... files may have a Textured mesh (Hex: 0x3B Dec: 59) indicator (if they are able to be textured) and then also UV mapping info.

Edited by M2m
Jason C. Hand

Jason C. Hand

Posted
Posted
  On 5/26/2020 at 4:54 PM, Stephan said:

Your Dobby headpiece features a stud connection on the top.

Expand  

Thanks for the heads-up, just saw it for myself. That is a result of copying both the collision and connectivity figures of the normal minifig head headpiece. When I get a minute, I will go in and update it.

jester

jester

Posted
Posted
  On 5/26/2020 at 6:17 PM, Jason C. Hand said:

Thanks for the heads-up, just saw it for myself. That is a result of copying both the collision and connectivity figures of the normal minifig head headpiece. When I get a minute, I will go in and update it.

Expand  

I usually use the most similar details)

Stephan

Stephan

Posted
Posted
  On 5/26/2020 at 6:17 PM, Jason C. Hand said:

Thanks for the heads-up, just saw it for myself. That is a result of copying both the collision and connectivity figures of the normal minifig head headpiece. When I get a minute, I will go in and update it.

Expand  

Perfect! I will include it then in the next update :)

Holly-Wood

Holly-Wood

Posted
Posted

Hi,

you're doing a great job here and I love that also LDD users benefit from our collaborative effort over at LDraw.org.

However I wonder why the authorship and the history have been stripped from the converted parts and why this Derivative work is shipped with no License and Attribution as determined by the:

LDraw.org Parts Library Agreement

Kind regards,

Willy Tschager
LDraw Content Manager

zweifuss

zweifuss

Posted
Posted
  On 5/28/2020 at 2:33 PM, Holly-Wood said:

Hi,

you're doing a great job here and I love that also LDD users benefit from our collaborative effort over at LDraw.org.

However I wonder why the authorship and the history have been stripped from the converted parts and why this Derivative work is shipped with no License and Attribution as determined by the:

LDraw.org Parts Library Agreement

Kind regards,

Willy Tschager
LDraw Content Manager

Expand  

I agree with this... if this is to move forward, all the added parts need to have authorship/history embedded in them. Are there places in the header that this info can be inserted in? On that topic, have the LDD developers ever credited LDRAW library for any of their parts? Where is that information found?

M2m

M2m

Posted
Posted
  On 5/28/2020 at 5:57 PM, zweifuss said:

I agree with this... if this is to move forward, all the added parts need to have authorship/history embedded in them. Are there places in the header that this info can be inserted in? On that topic, have the LDD developers ever credited LDRAW library for any of their parts? Where is that information found?

Expand  

Don’t think the g parts support that. I guess adding a txt file (per part ?) can be done. On the other hand „The LDraw Steering Committee (SteerCo) also holds an attribution to 'The LDraw Parts Library' in such Derivative Works to be sufficient in lieu of a full list of authors.“. 
So it seems that crediting the LDraw Parts Lib in general is ok too. 
How does stud.io do that ?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...