I use MLcad for my MOCs and LPub3D for instructions.
Now I want to add a foldable stair to my MOC where at first the stair is placed unfolded. I a later step I want the stair shown folded.
https://flic.kr/p/2nj5bwr for first step then later I want to show the folded stair [/url][url=https://flic.kr/p/2nj6dJM]folded stair. (I seem not be able to add the images in the text itself)

This is what I have so far:
0 !LPUB BUILD_MOD_ENABLED GLOBAL TRUE
1 19 10 10 0 1 0 0 0 1 0 0 0 1 64782.dat
1 19 10 10 -60 0 0 -1 1 0 0 0 -1 0 32278.dat
1 0 -70 -10 -80 1 0 0 0 1 0 0 0 1 63869.dat
1 0 90 -10 -80 1 0 0 0 1 0 0 0 1 63869.dat
1 71 10 -10 -80 1 0 0 0 1 0 0 0 1 60485.dat
0 STEP
0 !LPUB BUILD_MOD BEGIN "zz"
1 71 10 -10 -140 1 0 0 0 1 0 0 0 1 stairs.ldr
0 MLCAD ARROW 71 65 -35 -85 0.707107 0.707107 0 -0.707107 0.707107 0 0 0 1  10 4 12 40  3 30 1 2  16 16
0 !LPUB BUILD_MOD END_MOD
0 GHOST 1 71 -60 -36 -26 0 0 -1 0.978148 0.207912 0 0.207912 -0.978148 0 stairs_folded.ldr
0 !LPUB BUILD_MOD END
0 STEP
0 !LPUB BUILD_MOD REMOVE "zz"
1 4 120 -10 -140 1 0 0 0 1 0 0 0 1 3704.dat
0 STEP
0 !LPUB INSERT PAGE
0 !LPUB INSERT BOM


This works in a sense that the stair appears in the instruction first unfolded and in the later step as folded.
The problem is both stairs appear as building steps in the instructions. However only once in the BOM which is good again.

How best to get this effect in the building instruction. I tried also Buffer Exchange but that I couldn't get to work. Maybe I did something wrong there.
Any ideas? Much Appreciated.
Regards Allard

Attached Files

Thumbnail(s)
       

T-Junctions:
These are discouraged in the file format spec:

Quote:Where possible, abutting polygons should share common verticies.

Hi, new user here.

For some background, I've been looking at using the LDraw parts catalog as a starting point for 3d printing a few missing parts from some of my original 1970s space lego sets I kept from when I was a kid - set 924 for example. I could just buy the pieces of course, but trying to print them myself seems like a lot more fun :-).

I know the caveats around measurements in the LDraw catalog being approximations of the real physical dimensions, and being optimised for on-screen rendering, etc, so please say something if I'm stirring up old discussions and maybe just point me in the direction of those so I can read them.

Having said that, while I've been experimenting I've found some general inconsistencies between similar primitives in LDraw parts catalog and was I hoping someone could help me understand if they're "by design" or just historical drift between individual files, and whether there'd be any interest (or not) in trying to iron them out if they're not expected. Some of the parts haven't been modified for over a decade so I appreciate it might just be better to let sleeping dogs lie at this point :-).

There's a bunch of different types of inconsistencies I've found - I won't go into all the details unless there's some positive value to the community, but as a single example the control points for the conditional lines on the ends of part "p/1-4cyli.dat" look like the green lines in this screenshot and they appear to work as intended when the model is rotated (Note: I've attached the screenshots as well in case the Imgur posts get deleted):



but the control points for the conditional lines at the ends of "p/2-4cyli.dat" look like this and don't really show the conditional outline on the end edges correctly when the model is rotated:



I'm kind of new here (only been lurking for a couple of weeks), so there might be a legitimate reason for these odd-looking control points, in which case I'd be interested in what that is so I can understand it better.

In any case, if this kind of feedback is useful please let me know. And if it's not, please say so as well and I'll avoid spamming the forum with lots of irrelevant glitches :-)

Cheers,

Mike

Attached Files

Thumbnail(s)
   

  1-4cyli.png (Size: 10.79 KB / Downloads: 34)

Can you add these minifigure part? (20592) I need them for an MOC.
https://rebrickable.com/parts/20592pr000...nge-print/

I've been busy finishing LDCad 1.7 Alpha 2 and one of it's checkpoints is upgrading dependencies.

For this I upgraded the Linux (vm) build system to Debian 11, this caused some major problems compiler wise.

But after hours of tweaking I got a new binary out of it.

Only to discover it doesn't work on older systems because of the libc 2.28 dependency.

So I want to  try again using an older version of Debian.

But before doing that I was wondering about distributions the current users are running.

Also does anyone still use 32bit versions of the newer Linux  releases?

Hi! :-)

I would like a camel! :-)

There is in a two photos and also here: http://www.digital-bricks.de/en/index.ph...ddp&mg=259

Can sombody do this?

Thank you very much!

Best regards.: Zoli

Attached Files

Thumbnail(s)
       

Updated: corrected misplaced and obsoleted parts, split movable sections into submodels


  6352 - Cargomaster Crane.mpd (Size: 12.04 KB / Downloads: 10)
   

OMR compliant
Missing items: flexible rope

Some help please i been trying to join the sections i have circled but now doing my head in no matter what i can not get right is there a easy way or a short cut to help me starting to do my head in thank you

Attached Files

Thumbnail(s)
   

This part seems to need some fixing. The flanges should be 1 LDU thicker and the channel 2 LDU thinner, in order to properly fit the tires it goes with.

Here's my proposed fix, but it brings up some other issues, like the visible edge lines where the side supports meet the backside disc. (I tried a fix, but it messes up prim sub.) And what about the origin??

Attached Files

  497a.dat (Size: 2.54 KB / Downloads: 2)

It's looking like the next update will happen around the weekend of the 7th. I'd like to have the axle fix finished so that gives us 2 weeks to take care of the items on this list:
https://www.ldraw.org/cgi-bin/ptreviewsu...xleholefix

and address any items on the focus list that can be done.

Thanks for all the regular part reviewer efforts.