| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 214 online users. » 1 Member(s) | 208 Guest(s) Applebot, Baidu, Bing, Google, Yandex, Orion Pobursky
|
|
|
| Error found in assembly part 2772c01 |
|
Posted by: Ishai Bar - 2025-08-28, 11:38 - Forum: Parts Authoring
- Replies (1)
|
 |
I've been struggling with getting parts 2677 and 2678 to work together (and with other monorail parts) in Stud.IO for a couple of days now, and after thinking something might be wrong with them, I eventually discovered something wrong with part 2772c01 (Monorail Track Monoswitch (2772c02 / 2774)) instead. After examining this part closely in PartDesigner, I realized that the anti-studs at the bottom are actually misaligned. It turns out that part 2774 is sitting slightly too high above part 2772c02 in that assembly. This means that any monorail that includes the Monoswitch is bound to be misaligned, even if all connections along the monorail are perfect.
I can produce a corrected 2772c01, but it's probably better if someone else does it who has more experience with .dat files and can ensure that the resulting part would be perfectly aligned.
|
|
|
| parts update making MLCad behave odd |
|
Posted by: Harald Christ - 2025-08-27, 5:10 - Forum: LDraw Editors and Viewers
- Replies (2)
|
 |
Hi Team!
Just updated my MLCad v3.51 with a few of the latest parts updates (from Parts Update 2025-02 onwards)
I did it the way i normally do:
download zip file
extract to folder
copy parts, s, textures, p, 48, 8 to their relevant folders
run mklist
scan parts in MLCad
This has always served me well in the past.
However this time, there are lots of vacant spots in the part selection menu on the left.
Worse still, every file i load (ldr or mpd) fails to show some of the builds.
I know they are there, because i can make partslists from the file, but i can't view, or select them.
If i select all, then delete, then UNDO, the image shows. But saving this over the old file changes nothing.
Also, if i start a new file by dragging visible parts into the editing windows then all is good, but as soon as i drag one of the NON-visible parts, and refresh view, all the parts disappear.
Same as above, they are still "there" when making a partslist, but i can no longer view or select anything.
I've found this also seems to happen if i download a complete copy of ALL of the parts.
Is it something i'm doing wrong, or am i doomed to using old parts forever? 
Thanks in advance.
|
|
|
| Pattern Base Part |
|
Posted by: Orion Pobursky - 2025-08-24, 3:51 - Forum: Parts Tracker Discussion
- Replies (5)
|
 |
Here's a list of every patterned part that doesn't have a base part:
(List generated 8/23/2025)
parts/15336p01.dat Done
parts/15336p02.dat
parts/27039p01.dat Done
parts/39367p01.dat Done
parts/39367p02.dat
parts/47510p01.dat Done
parts/49242p01.dat Done
parts/49295p01.dat Done
parts/49295p02.dat
parts/49295p03.dat
parts/60235p01.dat Done
parts/60237p01.dat Done
parts/62575p01.dat
parts/65082p01.dat Done
parts/65497p01.dat
parts/65551p01.dat Done
parts/65552p01.dat Done
parts/65834p01.dat Done
parts/65834p02.dat
parts/67100p01-f1.dat Done
parts/67611p01.dat
parts/77127p01.dat
parts/90391p01.dat Done
parts/90391p02.dat
parts/t1094k01p01.dat
parts/t1094k02p01.dat
parts/t1094k02p02.dat
parts/t1094p01.dat
parts/t1095k01p01.dat
parts/t1095p01.dat
parts/t1096p01.dat
parts/t1097p01.dat
parts/u572p01.dat
parts/u572p02.dat
parts/u9534p01.dat
parts/u9537p01.dat
|
|
|
| Parsing LDraw |
|
Posted by: Max Murtazin - 2025-08-20, 18:04 - Forum: Help
- Replies (3)
|
 |
*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
|
|
|
|