 | | Re: Lpub Dual Callout
|
|
(...) I believe that your solution of multiple identical parts within the same begin/end is the correct solution. I'll make the PLI and BOM processes handle this case correctly. This way each instance gets its own placement and orientation. Kevin (19 years ago, 1-Jun-05, to lugnet.cad)
|
| |
| | Re: Lpub Dual Callout
|
|
(...) Thinking better (had a sleepless night ;o), this is not a solution. Multiple arrows generating multiple parts in bom/pli is not either: how the multiple submodels would get placed in the model (only one set of coordinates)? Philo (19 years ago, 1-Jun-05, to lugnet.cad)
|
| |
| | Re: 1-8tang.dat?
|
|
(...) but the current 1-8tang on the PT has 3 hold votes. This part (...) changed since december last year. Is someone willing to correct (...) It would be rather handy to give us a direct link to this primitive. And then, nice (URL) retro (...) (19 years ago, 31-May-05, to lugnet.cad.dat.parts.primitives, FTX)
|
| |
| | 1-8tang.dat?
|
|
I am working on a part and I actually need something like a 1-8tang primitive, but the current 1-8tang on the PT has 3 hold votes. This part hasn't been changed since december last year. Is someone willing to correct this primitive? Niels (19 years ago, 31-May-05, to lugnet.cad.dat.parts.primitives)
|
| |
| | Re: Callout in LPub
|
|
(...) Right. That did it! Tnx. Jaco (19 years ago, 31-May-05, to lugnet.cad)
|
| |
| | Re: Lpub Dual Callout
|
|
(...) This one: (URL) ? Thanks... nothing better than an axample! (...) I do too (the multi pointer could have other uses) There might be a third solution, something like the "inverse" of LPUB PLI BEGIN IGN that would allow to add parts to the PLI (...) (19 years ago, 31-May-05, to lugnet.cad)
|
| |
| | Re: Lpub Dual Callout
|
|
(...) Hi Philo, I've uploaded a DAT file to brickshelf that uses multiple pointers with a single callout, and a bunch of other tests. I made this file at the recommendation of Mike Walsh. I use it to test LPub. I'm updating the documentation to (...) (19 years ago, 31-May-05, to lugnet.cad)
|
| |
| | Lpub Dual Callout [DAT]
|
|
I want to use the same callout twice in the same step. I tried to use the following code (and variations...), but when generating layouts Lpub complains that a file (MPDname_0_04_co_1.png) is missing. And after that one of the bars is missing in the (...) (19 years ago, 31-May-05, to lugnet.cad)
|
| |
| | Re: Questions about LPub
|
|
(...) I rewrote all the layout parsing so that it checks syntax and reports errors yesterday. I've wanted to eliminate the silent parse errors. I've got to debug this before I can release. Kevin (19 years ago, 31-May-05, to lugnet.cad)
|
| |
| | Re: Callout in LPub
|
|
Hello Jaco, (...) Yes, getting better and better ! (...) Yes, CALLOUT POINTER takes 4 parameters, the side (RIGHT), the position on that side (missing here, 0.9 would be a good start) and the x-y position of the tip (0.8 0.3) Philo (19 years ago, 31-May-05, to lugnet.cad)
|
| |
| | Re: Callout in LPub [DAT]
|
|
(...) OK! Nearly there: (URL) to eleminate the arrows in the assem (due to ghosting) and get rid of step 2 in the call out. Also the pointer is missing (something wrong with the code?) Here is the DAT code of the entire model: 0 FILE 1088.ldr 0 Set (...) (19 years ago, 31-May-05, to lugnet.cad)
|
| |
| | Re: Orientation in PLI and BOM
|
|
(...) Right. I did so, but the frustrating thing was that it didn't work. No matter what I did the part kept displaying the same way. Until ofcourse I deleted the image from the parts folder and did a new render... :-) Thanks again, Kevin! Jaco (19 years ago, 31-May-05, to lugnet.cad)
|
| |
| | Re: Orientation in PLI and BOM
|
|
(...) This is a tough situation Jacko. If you look at LEGO PLI's you'll notice the orientation of a technic brick. The left end of the brick is rendered lower than the right end of the brick. Now look at the orientation of the same brick in the (...) (19 years ago, 30-May-05, to lugnet.cad)
|
| |
| | Orientation in PLI and BOM [DAT]
|
|
Though I added part 3829 Car Steering Wheel to the ORIENTATION.LDR file in the extra's folder of LPub, the part shows up wrong in the PLI and BOM: (URL) this a bug? Or did I do something wrong? I added it like this: 1 0 0 0 0 0 0 1 0 1 0 -1 0 0 (...) (19 years ago, 30-May-05, to lugnet.cad)
|
| |
| | Re: Callout in LPub
|
|
(...) 0 // Idefinty part calledoutmodel.ldr 0 LPUB CALLOUT BEGIN 0 // Place the callout centered above the assembly 0 LPUB CALLOUT PLACEMENT TOP CENTER ASSEM 0 // Draw a pointer from right edge of callout to upper right of ASSEM 0 LPUB CALLOUT (...) (19 years ago, 30-May-05, to lugnet.cad)
|
| |
| | Re: Questions about LPub
|
|
(...) OK... Note that unfortunately I still don't have that updated documentation (installer problem, see (URL) In LPub traditional form (which is annoying), the "mistake" of using ASSEM, is (...) Yes, that deafening silence is annoying. After (...) (19 years ago, 30-May-05, to lugnet.cad)
|
| |
| | Parts substitution [DAT]
|
|
Some parts that consist of more subparts must be drawn as one part in the PLI. LPub has a command for this I used: 0 LPUB PLI BEGIN SUB hinge.ldr 1 0 0 -40 80 1 0 0 0 1 0 0 0 1 hinge.ldr 0 LPUB PLI END SUB I created the file inside the MPD file: 0 (...) (19 years ago, 30-May-05, to lugnet.cad)
|
| |
| | Callout in LPub
|
|
Hi all, Though I am getting more and more good results from making building instructions using LPub I still have some questions. I know I posted a lot of questions already, but there are some new. Since I lost track of replies and answers, I decided (...) (19 years ago, 30-May-05, to lugnet.cad)
|
| |
| | Re: Questions about LPub [DAT]
|
|
(...) I think I did this, but the picture I get is this: (URL) parts at all for the hinge? With the code like this: 0 STEP 1 1 -30 -16 70 0 0 1 0 1 0 -1 0 0 4085C.DAT 1 1 30 -16 70 0 0 -1 0 1 0 1 0 0 4085C.DAT 1 1 0 -16 -110 1 0 0 0 1 0 0 0 1 (...) (19 years ago, 29-May-05, to lugnet.cad)
|
| |
| | Re: Questions about LPub
|
|
(...) Philo, In my code and the documentation I posted yesterday, STEP_NUMBER can only be placed relative to PLI or PAGE. It currently cannot be placed relative to the ASSEM image. Therefore you cannot do what you want. In LPub traditional form (...) (19 years ago, 29-May-05, to lugnet.cad)
|
