*sigh*

Okay, I've probably been it at it many times and probably even asked some questions on this topic before, but, alas, I'm at it again - trying to build an LDraw file format parser in C#. Why C#? Tl;dr: I need it for other stuff, and that stuff uses C#.

Well, the question itself: How does one even go around effectively parsing LDraw? This topic is a bit confusing to me due to the recursiveness (I guess that's what the word would be) of the format. My current approach is like this:
1. Read through all of the file, store all the faces in an array, store all the submodels in a separate array
2. Go through the submodel array, go to step 1 for each of them
3. Once the process is out of this recursive mess, "resolve" each submodel by applying the transform to it's triangles and adding them to the submodel's parent
4. Done, I guess?

It is very simple and doesn't account for, like, any meta or other stuff that could be important, but it should be enough for the start. I'm just not sure if this approach is good, or how it possibly could be improved

Also, I know I can read stuff like LDView source code, but I'm really bad at reading code made by other people, so it would probably take way more time than just asking it here

This release improves the colour search and adds the colours from the 2025-07 parts update:
https://github.com/Nexusnui/Convert-To-L...tag/v1.5.2

Release Notes:

Important Notice:
This version uses a new windows installer(Inno Setup) and the default installation path has changed. This means that versions prior to this release are not overridden and have to be uninstalled manually.

Changelog:

Improvements:

• #40 improve colour search
  • button to show simular colours to the current one
    
  • do not clear searchbar when changing search category
    
  •  fixed search by colour name
    
• updated LDraw Colours to include the new additions from the 2025-07 parts update
  

• #43 use backslash for s path in LDraw files
  
• Updated some dependicies including pillow that fixed a potential security vulnability
  

I'm looking for meshes to parts in the Duplo 3in1 Magic Castle, Set 10998.
Star-wand 16499, 
flower 84195, 
cake 65157, 
book 100954pb03, 
window 26249,
balcony 98236,
door 98239, and
bush 84194.
Can they be found in BI?

https://www.bricklink.com/v2/catalog/cat...conly%22:0}

It seems that the duplo drawer 4891 is 2.6 LDU too high compared to physical part. It doesn't fit the 52 LDU slots in cupboards.
https://library.ldraw.org/parts/9776

Furthermore, the origin seems to be 3 LDU above the part. Can we live with that?

Hi all,

Why is the angle of the arrow tip on Minifig Harpoon 57467 not straight?
It seems at an 11 degree angle?

   

All the documentation I found used backslashes(\) for filepaths e.g "s\subpart.dat". But I could not find if forward slashes(/) are also allowed. LDView can use either without any errors, while LDPe does show an error. If either both or only backslashes are allowed it should be mentioned in the Documentation either under filename or a new section. I do ask this because in ConvertToLDraw I currently use forward slashes and I got this Bug report. I will change the filepaths if they are out of spec.

Is there any way to search for unofficial subparts that have at least one official parent, but do not have any unofficial parents?

Hi there! I am looking for the pieces mentioned above. I've tried designing them myself, but I am simply too inexperienced with getting the printings onto the pieces and such. Help would be greatly appreciated, and if not, i still appreciate your consideration

https://www.bricklink.com/v2/catalog/cat...=tricera01 - Triceratops
https://www.bricklink.com/v2/catalog/cat...e?P=trex08 - Tyrannosaurus Rex
https://www.bricklink.com/v2/catalog/cat...P=raptor15 - Velociraptor
https://www.bricklink.com/v2/catalog/cat...baryonyx01 - Baryonyx

Thanks

I'm working on a custom part that is basically a face with a 1x2 plate stuck on to the back of it. The face is a complex mesh with about 45k triangles (no quads). 
To be sure my studs will have the correct shading in building instructions developed in Studio, I am adding stud.dat in LDPE. However, that step seems to "corrupt" geometry in some way. After adding the stud.dat lines, the resulting part looks ok in Part Designer, but not in Studio. Many faces have disappeared and the remaining ones look distorted.  
I have confirmed that the files are identical except for the `0 Name:` line and the two lines that reference stud.dat like so: