Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 5,310
» Latest member: artur
» Forum threads: 6,175
» Forum posts: 51,776
Full Statistics
|
Online Users |
There are currently 243 online users. » 2 Member(s) | 235 Guest(s) Applebot, Baidu, Bing, Google, Internet Archive, Yandex, Orion Pobursky, Will
|
Latest Threads |
A fresh list of "most com...
Forum: Part Requests
Last Post: tom alphin
1 hour ago
» Replies: 5
» Views: 267
|
Lego Town Racer 1996 - 63...
Forum: Official Models
Last Post: Chris Böhnke
7 hours ago
» Replies: 14
» Views: 1,682
|
Eyesight on Linux
Forum: Rendering Techniques
Last Post: Orion Pobursky
11 hours ago
» Replies: 12
» Views: 8,343
|
Another common varient: 1...
Forum: Part Requests
Last Post: Rene Rechthaler
2025-09-12, 14:51
» Replies: 8
» Views: 5,388
|
Fix for slightly incorrec...
Forum: Part Requests
Last Post: Gerald Lasser
2025-09-12, 14:13
» Replies: 3
» Views: 565
|
1Lx1Lx2L brick with studs...
Forum: Parts Authoring
Last Post: SNIPE
2025-09-12, 10:14
» Replies: 0
» Views: 469
|
LDraw Colors for OpenScad
Forum: LDraw Editors and Viewers
Last Post: Hageta
2025-09-12, 10:03
» Replies: 0
» Views: 428
|
Img4Dat integrated in LDP...
Forum: Parts Authoring
Last Post: Nils Schmidt
2025-09-11, 20:04
» Replies: 6
» Views: 866
|
TXT2DAT integrated in LDP...
Forum: Parts Author Tools
Last Post: Nils Schmidt
2025-09-11, 19:47
» Replies: 4
» Views: 945
|
Here is the raw version o...
Forum: Part Requests
Last Post: Peter Grass
2025-09-11, 4:39
» Replies: 2
» Views: 798
|
|
|
LPUB - Some Ideas for Improvement |
Posted by: Gerald Lasser - 2013-05-09, 22:05 - Forum: LDraw File Processing and Conversion
- No Replies
|
 |
Hello,
After working on an instruction for a few days I came across some issues that bugged me quite a lot and the workarounds with the existing tools are either tideous or I simply did not know them, in this case I gladly take some advice from you :-)
For the issues where I did not see any obvious workaround I would have some suggestions concerning mainly MLCAD, LSYNTH and LPUB. I would like to get your opinions.
Those are the concerns:
1.) "One Part Movements" e.g. sliding a bush on an axle
2.) Moving parts later during construction
3.) Re-Routing of Cables during construction
And here are the ideas:
ad 1.) "One Part Movements"
Sometimes in the instructions you want to show a part being moved or added, so you put it a bit away from the model and add an arrow.
BUFFER exchange does to job pretty well and straight forward. However, it clutters the MLCAD file quite a lot. Not so much in the code, but visually. So it gets difficult to identify parts and e.g. if you want to move them later on, you need to move the buffered parts as well.
The file looks like this:
[sub]1 4 124 0 0 1 0 0 0 1 0 0 0 1 32054.dat
0 BUFEXCHG A STORE
1 0 -4 0 0 1 0 0 0 1 0 0 0 1 4519.dat
0 MLCAD ARROW 0 72.001 0 0 -1 0 0 0 1 0 0 0 -1 15 6 18 50 1 30 1 2 1 1
0 MLCAD SKIP_BEGIN
3 1 90.001 0 0 71.001 -7.5 0 72.6677 0 0
3 1 90.001 0 0 71.001 7.5 0 72.6677 0 0
3 1 72.6677 0 0 72.001 -3 0 72.001 3 0
4 1 72.001 -3 0 22.001 -3 0 22.001 3 0 72.001 3 0
0 MLCAD SKIP_END
0 STEP
1 0 84 0 0 1 0 0 0 1 0 0 0 1 4519.dat[/sub]
And displays in MLCAD as:
![[Image: suggest_01.png]](http://www.brickshelf.com/gallery/lg008823/ThisAndThat/suggest_01.png)
To avoid this a META command either directly within MLCAD or in LPUB could be used that applies to the part following the command. e.g.:
[sub]0 OFFSET PART [Matrix where to show the part/or a delta position]
1 0 84 0 0 1 0 0 0 1 0 0 0 1 4519.dat[/sub]
MLCAD would the show only the part in its final position
-> The command could be realized in e.g. LPUB only (make it LPUB OFFSET)
-> Additionally an arrow could be added as it is currently done in MLCAD ARROW
ad 2.) Moving parts later during construction
Sometimes a part is added during construction that will be used in a later step to fasten an additional part, e.g. pushing in the long pin with bush during technic construction or movin an axle.
The only way how to realize this is putting a lot of parts into the buffer exchange. This disadvantage here is that multiple STEPS within the BUFFER exchange commands make LPUB not displaying the amount of bricks correctly. (MLCAD does show a correct inventory) .
Also a disadvatage of this method is not so much cluttering the view, but when parts are moved, you need to take care of many parts within the buffer.
A better way to handle would be to put only this one or more parts into a buffer and retreive them, respectively replace them later. Realization would require an extension to the BUFFER meta command:
e.g. define the parts that need to be moved between a START/STOP bracket and later remove them with a REMOVE command and place the same part in the final position.
[sub]0 BUFEXCHG A START
1 4 124 0 0 1 0 0 0 1 0 0 0 1 32054.dat -> Part in pulled out position
0 BUFEXCHG A END
0 BUFEXCHG A STORE
....
0 BUFEXCHG A REMOVE
1 4 124 0 0 1 0 0 0 1 0 0 0 1 32054.dat -> Part in final Position[/sub]
ad 3.) Re-Routing of Cables during construction
This concerns instructions where a cable needs to be included (as later parts would block the routing at the time the destination is inserted) and needs to be re.routed once or several times during constructions.
Theoretically this could already be addressed with the proposal of the second point. But to make instructions easier to do and better to read some improvements can be done like:
- entering a "name" for the cable (or LSynth element) to make identification for re-routing easier.
- adding a color identifier to the cable to show the destination when multiple cables are used.
Possibly two meta commands in LSynth could help here e.g. NAME and LABEL
[sub]0 SYNTH BEGIN ELECTRIC_POWER_FUNCTIONS_CABLE 16
0 SYNTH NAME CABLE-1
0 SYNTH LABEL START/STOP SQUARE/CIRCLE/DIAMOND/TRIANGLE UP/DOWN Size Color
0 SYNTH SHOW
...
0 SYNTH SYNTHESIZED BEGIN
...
0 SYNTH SYNTHESIZED END
0 SYNTH END[/sub]
The LABEL command would add a color identifier to the cable hovering above the cable before the plugs.
The NAME command could identify a cable and when preparing instructions e.g. LPUB can take care to use now the next instance of e.g. CABLE-01
So, that was quite a lot, may be too much, but I would be happy to hear your opinions.
Thansk for reading
Gerald
|
|
|
Drawing conditional lines |
Posted by: Santeri Piippo - 2013-05-08, 19:24 - Forum: Parts Authoring
- Replies (13)
|
 |
I'm using OpenGL for LDForge's renderer and I'm about stumped on to decide when to draw conditional lines. Actually rendering the part is no problem but how does a GL renderer take the control points into account?
For compiling objects glGenLists/glNewList/... is used and glCallList for drawing them. While it's not the most optimized approach, it works for something as simple as a single part.. at least for the simple ones. I've been considering using VBOs though.
|
|
|
Added Parts Different Colour than Older Ones |
Posted by: MMH - 2013-05-08, 14:34 - Forum: Rendering Techniques
- Replies (6)
|
 |
Hi there,
I'm currently trying to make a set of instructions for some Lego models I have created in MLCad. I would like to format them so that parts that were added in a previous step are differentiated from the new parts (preferably by making the older parts lighter while the newer ones are in full colour). Is there a way to do this in LPub or MLCad, or is there a better software solution to fit my needs?
Thanks for your time!
|
|
|
12887pb01 - Powdered Wig |
Posted by: Godfrey LaRocque - 2013-05-05, 19:08 - Forum: Part Requests
- Replies (1)
|
 |
Hi! I'm new here, so I hope it's not too rude of me to request a part. I need the powdered wig from CMF Series 10's Revolutionary Soldier for a set of instructions I'm working on - could anyone help? Thanks!
-G
|
|
|
Compatibility issue in MPD submodel file names between MLCad and Bricksmith |
Posted by: Philippe Hurbain - 2013-04-29, 12:04 - Forum: LDraw Editors and Viewers
- Replies (6)
|
 |
A friend who uses Bricksmith sent me a mpd, that I returned him after some changes using MLCad. After that, Bricksmith complained that "submodels are not available". A check of MPD before and after my changes, showed that there was a capitalization issue.
Here is the header of one submodel:
Code: 0 FILE righttrack.ldr
0 Right track assembly
0 Name: RightTrack.ldr
Bricksmith refers to this submodel as
Code: 1 495 -480 104 59 -1 0 0 0 1 0 0 0 -1 RightTrack.ldr
but it seems that MLCad uses only file field as reference, and silently changes this line to
Code: 1 495 -480 104 59 -1 0 0 0 1 0 0 0 -1 righttrack.ldr
...and now Bricksmith is lost!
Any solution?
|
|
|
|