| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,654
» Latest member: Gonçalo
» Forum threads: 6,392
» Forum posts: 53,054
Full Statistics
|
| Online Users |
There are currently 370 online users. » 1 Member(s) | 365 Guest(s) Baidu, Bing, Google, Yandex
|
| Latest Threads |
Discussion - proposal to ...
Forum: Official File Specifications/Standards
Last Post: Roland Melkert
2 hours ago
» Replies: 43
» Views: 3,488
|
2026/2027 LDraw.org Steer...
Forum: LDraw.org Announcements
Last Post: Willy Tschager
2 hours ago
» Replies: 0
» Views: 25
|
Parts 4245 + 4264 for set...
Forum: Part Requests
Last Post: Alfred Schmitz
6 hours ago
» Replies: 2
» Views: 128
|
Parts Request- Marvel 202...
Forum: Part Requests
Last Post: Gerald Lasser
Yesterday, 23:16
» Replies: 7
» Views: 1,700
|
Looking for some Ninjago ...
Forum: Part Requests
Last Post: Gerald Lasser
Yesterday, 23:13
» Replies: 6
» Views: 244
|
Metalic gold primatives v...
Forum: Parts Authoring
Last Post: Travis Cobbs
Yesterday, 0:09
» Replies: 5
» Views: 275
|
4.5L technic axle and new...
Forum: Part Requests
Last Post: SNIPE
2026-02-12, 22:45
» Replies: 2
» Views: 157
|
[LDPE] 1.8.97 Released (s...
Forum: Parts Author Tools
Last Post: Nils Schmidt
2026-02-12, 19:05
» Replies: 5
» Views: 966
|
Existing Part Edit Reques...
Forum: Parts Authoring
Last Post: Chris Böhnke
2026-02-12, 2:24
» Replies: 159
» Views: 388,602
|
Raven from Dreams [5272pb...
Forum: Part Requests
Last Post: Hageta
2026-02-11, 16:29
» Replies: 2
» Views: 237
|
|
|
| Cannot run the POV for the file from LDRAW |
|
Posted by: jass - 2020-02-21, 9:06 - Forum: Rendering Techniques
- Replies (1)
|
 |
I updated the new LDRAW ALL IN version. There is no problem in the modeling by MLCAD. But when I run the POV file exported from LDRAW, the wrong message is as below.
I checked the before POV file made by old LDRAW ALL IN version, there is no problem. I don't know if there is any option need to setup. Thanks a lot.
Parse Error: No matching } in ‘texture’, undeclared identifier 'lg_gold_chrome' found instead
#ifndef (LDXColor334) // Chrome Gold
#declare LDXColor334 = #if (version >= 3.1) material { #end
texture {
lg_gold_chrome
}
#if (version >= 3.1) } #end
#declare LDXColor334_slope = #if (version >= 3.1) material { #end
texture {
lg_gold_chrome
#if (LDXQual > 1) normal { bumps 0.3 scale 25*0.02 } #end
}
#if (version >= 3.1) } #end
#end
|
|
|
| Help me figure out a math/measurement problem |
|
Posted by: N. W. Perry - 2020-02-16, 4:57 - Forum: Help
- Replies (5)
|
 |
I found a measurement discrepancy in set 21004 between the LDraw version and the real thing. I know that sometimes things don't work out precisely between the two, but in this case there's a mismatch of exactly 4 LDU, and I'm trying to pinpoint why.
This involves the rotunda section with its stacked 6x6 dishes and 4x4 round plates, and the 6L axle that supports it. Here are the precepts:
- The 6L axle has a length of 120 LDU, nominally equal to 48mm in real life.
- As we know, plate height is 8 LDU (12 with the studs), so two stacked plates are 16 LDU high (20 with studs).
- The center of the 6x6 dish has the ordinary plate height of 8 LDU, and the cavity adds another 8 LDU, making it equal to two stacked plates in height.
- As a result, the 4x4 round plate sits entirely flush within the 6x6 dish.
- Per the instructions, and confirmed in the physical set that I own, the 4x4 round plate at the top of the assembly sits fully within the uppermost 6x6 dish, and the bottoms of both that dish and the 4x4 dish should be at equal height.
- The axle hole in the 4x4 dish is 12 LDU deep.
So, here's an image showing the problem; the axle assembly and the stacked dishes are shown offset for clarity, but at their correct vertical position:
As you can see, the 4x4 dish and plate at the top are 4 LDU too high, because the rest of the assembly is only 104 LDU high rather than the necessary 108. Where is that extra 4 LDU coming from?
I thought perhaps the axle hole in the 4x4 dish should be 16 deep instead of 12, but a rough measurement of the real part suggests that 12 is correct. All of the dishes seem to be modeled at their correct height, too, so the only thing I can think of is the axle. Indeed, measuring the real axle shows that it's just a bit over 47mm long, not 48. It may even be 47.2mm, leaving it 2 LDU short of its theoretical length, but that still leaves another 2 LDU to account for. Could the height of the embossed stud logo account for that (see the 2x2 round plates at the bottom), or just the natural physical play between parts?
|
|
|
| How to import LDCad file to Solidworks? |
|
Posted by: Cuong Nguyen Viet - 2020-02-15, 8:16 - Forum: General LDraw.org Discussion
- Replies (1)
|
 |
Dear LDraw.org member!
I am learning how to simulate lego set. I tried with LDCad with its script.
I think this is the best simulate for lego set now.
But, I saw in youtube that they can simulate lego set with Solidworks.
So could you give me some advice, how to import LDCad file to Solidworks?
Thank you!
This video using SR3DBuilder. But the Developer was pass away some years, and now I cannot install it in my PC window 10.
|
|
|
| New Parts Tracker Search Capabilities |
|
Posted by: Chris Dee - 2020-02-13, 19:11 - Forum: Website Suggestions/Requests/Discussion
- Replies (2)
|
 |
(2020-02-12, 6:29)Chris Dee Wrote: I can take a look at this.
That's done for the Parts Tracker File scan (https://www.ldraw.org/cgi-bin/ptscan.cgi). Multiple words are now supported and all need to exist in a file for it to be listed inthe search results. Double quoted phrases are supported and need to exist as entered. The two forms may be combined.
The search box in the Parts Tracker page header works slightly differently. If the entered word (xxxx) exists in the unofficial library (as xxxx.dat) the detail page for that file is returned. I guess now that the Parts Tracker allows the display of detail pages for official parts, it should also check for a precise match in the official library. At present if there is no unofficial file, the search term is passed to ptscan. It would be possible to make that script work differently in this use case, but it is not clear to me what it should do.
|
|
|
|