| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,756
» Latest member: alphonse
» Forum threads: 6,452
» Forum posts: 53,442
Full Statistics
|
| Online Users |
There are currently 186 online users.
» 1 Member(s) | 179 Guest(s)
Applebot, Bing, Facebook, Google, Twitter, Yandex, Jeff Jones
|
|
|
| James Jessiman Memorial Award for 2025 awarded to Rolf Osterthun |
|
Posted by: Orion Pobursky - 2026-03-18, 21:46 - Forum: LDraw.org Announcements
- Replies (7)
|
 |
The LDraw.org Steering Committee is pleased to announce that the 2025 James Jessiman Memorial Award (JJMA) recipient is Rolf Osterthun.
Rolf says about himself:
"The first LEGO set I can recall owning was the yellow garbage truck (6693). My collection grew continuously from there, with no 'Dark Ages' in between. Starting with City (LEGOLAND), Space, and Technic, moving on via Star Wars and Marvel, my physical collection now primarily focuses on Modular Buildings (City again).
My first contact with digital bricks was through LeoCAD. Shortly after, MLCad introduced me to the LDraw format and I even created a few animations using LD4DStudio (which I really enjoyed). I believe it was in 2009 that I made my first post on Lugnet, announcing a converter that could transform LDD models into LDraw models. Since then, I've been proud to be a part of this remarkable community.
Almost every time I have programmed privately, I tried to convert something into the LDraw format – I even managed to get a few parts through the Parts Tracker."
More information on the JJMA can be found at: https://www.ldraw.org/article/222.html
On behalf of the LDraw Steering Committee, we thank Rolf for his contributions and look forward to working with him in the future.
Orion Pobursky
|
|
|
| 2026 LDraw.org Steering Committee Election Results |
|
Posted by: Orion Pobursky - 2026-03-18, 21:43 - Forum: LDraw.org Announcements
- Replies (8)
|
|
Voting is now closed,
Join me in congratulating and welcoming the 2026 Steering Committee:
Philippe Hurbain
Gerald Lasser
Orion Pobursky
N. W. Perry
Lisa Winter
Thank you for all who voted and all the candidates who ran.
The full election vote totals:
Chris Böhnke - 7
Philippe Hurbain - 15
Gerald Lasser - 14
N. W. Perry - 9
Orion Pobursky - 13
Rene Rechthaler - 6
Lisa Winter - 10
|
|
|
|
| Question about aring usage in library |
|
Posted by: Travis Cobbs - 2026-03-18, 5:39 - Forum: Parts Authoring
- Replies (8)
|
 |
I am (finally) working on supporting the aring primitive in LDView's primitive substitution, and I have run into what I feel is a problem. The problem is that I believe that the aring can be used in two different ways:
- To fill in the gap between a standard-resolution curved primitive and a 48-resolution curved primitive
- To fill in the gap between 16-sided geometric curve and a 48-resolution curved primitive
I know that it is being used in situations that match option 1 above. I don't know if it is being used for option 2 or not. One (relatively minor) problem is that option 1 is incompatible with how LDView does primitive substitution when the curve quality is set to certain settings. I should be able to fix this. But there is no way for me to generate the primitive in a way that is compatible with both option 1 and option 2.
For option 1, the resolution of the inner part needs to track my primitive substitution curve quality, and the outer part needs to track the 48-resolution version of the same thing. When the quality is set to the default value, this would be 16 and 48. For the next notch on LDView's quality slider, the 16 becomes 24. Right now, the 48-resolution version remains 48 at that setting. (That would probably change. The next notch uses 32, and since 32 doesn't evenly divide into 48, that would have to change. Same for the next notch, which is 40. An easy solution is to use 64 and 80 for the 48-resolution version of those two notches.)
But if this primitive is used next to hard-coded 16-sided geometry, then the inner resolution would need to remain 16, no matter what the curve quality is set to. The current description for the aring primitive does specify that it interfaces between high-resolution primitives and normal-resolution primitives. So does this mean that interfacing with 16-segment geometry is not allowed? If so, I can make it work (although it will cause my primitive substitution to render more geometry for 48 curves when the curve quality is set to use 32 or 40 segment curves).
If it is used next to 16-segment geometry, then I feel that that needs to be forbidden, and a new primitive needs to be introduced to fill that (different) role.
Side note: for POV export, the first version of this primitive is no geometry at all. The second version is a chord.
|
|
|
|
| Victims of no autosave |
|
Posted by: Jeff Jones - 2026-03-16, 20:12 - Forum: Parts Authoring
- Replies (2)
|
 |
as you know one of the biggest flaws of ldparteditor is its lack of an autosave, i lost the age of ultron hulk i was working on thanks to it
this would be where you share the parts you lost thanks to it
for me
that chima 2014 armour, smart play x play cockpit, and the aforementioned hulk
pls add it nils
|
|
|
|
|
