The 2023-02 LDraw Parts Update has been released. This update adds 279 new files to the core library, including 147 new parts and 2 new primitives.
Thanks are due to all the part authors who created or corrected parts for this release. The small, but dedicated, band of reviewers also play an important role in keeping files moving through the Parts Tracker and deserve just as much credit. This update wouldn't have been possible without their dedication and attention to detail.
You can preview the new parts in 2023-02 here, and download the zip-file update or Windows install package here. Currently LDView download is unavailable due to the new server configuration. This will be fixed in the near future
This update marks phase 2 in the rollout of the new licensing scheme. In this update, parts where all the authors have agreed to new license will now be marked as CC By 4.0 only. This file are included with only the license line updated (as opposed to the the normal process of updating the !LDRAW_ORG line and adding a !HISTORY statement)
Thank you to all the beta testers and parts authors who continue feedback for the new PT software. This project would not was it is without your help.
Orion Pobursky
LDraw.org Parts Library Admin
P.S.
I have noted some parts that should be listed either the notes file or the part preview are not listed as they should be. I'm working to figure out the cause of this and will manually update these file when I patch the issue. Update: Part preview is now fixed (notes were correct). There are a few broken images but those will be dealt with shortly.
Been stuck with a problem for a couple of days - the new unanswered forum posts from some recent time started to appear to me as unread for some reason. Unless I use "mark all threads tread" function, threads stay marked as unread until I'll answer those no matter how many times I check them
I am trying to convert bricks to .obj format. LeoCAD has this export option, however, for some parts it raises an error "Nothing to export".
E.g. when I load part 4073 from .dat file, it can be exported just fine, but not part 3023. I get the same error when I try to render it.
What are the reasons for such inconsistent behaviour and is there a way to fix it?
Requesting part 76925 (Hair piece), if possible.
I cannot find it on digital bricks, would there be any other source to get the mesh from?
Probably not from the LEGO instructions app as it has to available as 3D build?
I am getting error 500 when trying to submit new parts, in both Edge and Firefox. Already deleted cookies and tried private mode, but no effect. Was able to update some existing parts yesterday, is something wrong on my side or server side?
So, continuing with my LDraw to xml converter grind, looks like I have managed to solve pretty much everything but one thing - handling sharp edges
I have tried multiple ways, but nothing seems to work. Generally, it seems I should not interpolating normals between faces that share sharp edge, but then arises problem of faces that share only 1 vertex. How this case should be approached?
Howdy!
I hope I am on the correct forum with this post
So I am trying to program a 3d viewer for my files for my website. And I got most stuff working, but now I noticed that when loading some parts, such as 4733 (Brick, Modified 1 x 1 with Studs on 4 Sides), two of the studs are oriented the wrong way (as you can see in the picture i uploaded): they are flipped on their axes, the other studs aren't though.
And so I looked into the ldr file of the part 4733 itself where the studs themselves are being rotated (line 116-120) and I noticed that the studs that are wrongly rotated on my viewer are the 2nd and 5th entry (line 117 and 120) there. And I looked at their transformation matrices and they seem kinda wrong.
So I looked into those matrices more and it kinda looks like the axis that those matrices flip (which is what the "-" does), should be on the other axis, so the entry in line 117 should actually be "1 16 10 10 0 0 1 0 -1 0 0 0 0 1 stud2a.dat" and in line 120 it should be "1 16 0 10 10 1 0 0 0 0 -1 0 1 0 stud2a.dat".
The matrices look like the creator of the ldr part switched up the matrix multiplication, like the flipping of the two axes and the invertion of the axis, cause if you take those matrices apart and switch them around (you flip the part where the "-" is as explained above) you end up with the correct transformation matrix.
Is it normal that those matrices are just wrong? Or do I not completely understand the ldraw standard in a way that you can't just take the vertices and transform them using those matrices?
Thanks for your help!
(I also have some problems with some of the "4-4ndis.dat" transformations in this and a few other parts, though I haven't looked into that yet, you can kinda see it on the attached picture though that the scaling in the y direction is wrong, might just be an error in my code who knows, I'll look into that )
(If I haven't explained some stuff properly feel free to ask!)
(If you want to look at the code I wrote for this: link, but it's not optimised yet and I've commented some stuff out since I work directly in the deployment branch and the zip library makes my automatic deployment fail xD)
