 | | | | | |
I'm trying out LPub 4 for the first time and am having some trouble. (Note that
I am a veteran of LPub 3). Every time I attempt to make a submodel into a
callout, the program simply crashes. Has anyone else used the callout function
successfully or are there any thoughts? If I could remember the syntax, I
suppose I could try putting in the meta commands for the callout manually.
LPub 4.0.0.4.
Eric Albrecht
| | | | | | | | | | | | | | |
In lugnet.cad, Eric Albrecht wrote:
> I'm trying out LPub 4 for the first time and am having some trouble. (Note that
> I am a veteran of LPub 3). Every time I attempt to make a submodel into a
> callout, the program simply crashes. Has anyone else used the callout function
> successfully or are there any thoughts? If I could remember the syntax, I
> suppose I could try putting in the meta commands for the callout manually.
>
> LPub 4.0.0.4.
>
> Eric Albrecht
Eric,
I do not experience any problems in creating callouts.
Positioning them is sometimes a bit tricky.
Adding them manually is always a good thing to try.
The syntax is this:
0 !LPUB CALLOUT BEGIN
1 x x x x x x submodel.ldr
0 !LPUB CALLOUT END
Jaco
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Jaco van der Molen wrote:
>
> I do not experience any problems in creating callouts.
> Positioning them is sometimes a bit tricky.
> Adding them manually is always a good thing to try.
> The syntax is this:
>
> 0 !LPUB CALLOUT BEGIN
> 1 x x x x x x submodel.ldr
> 0 !LPUB CALLOUT END
Thanks Jaco. Through the process of doing it manually and a lot of other trial
and error, I discovered the problem. My submodels had a dot (.) in the title.
This seemed to confuse LPub and result in the problems I saw. I converted all
the dots to dashes and now it is OK.
This leads me to a couple of other questions next:
I have some assemblies in the model which are mirrored left and right using a
tranformation matrix. LPub does not show and assembly being built mirrored.
Any way around this or do I have to actually create all the assemblies
individually?
What about LSynth assemblies? For example, I have a Technic Flexible Axle
consisting of two ends and a bunch of center parts. I know how to use PLI IGN
to get it to NOT appear in the parts list, but how I do get an actual flexible
axle to appear in the parts list?
Thanks for any help.
Eric
| | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Eric Albrecht wrote:
> Thanks Jaco. Through the process of doing it manually and a lot of other trial
> and error, I discovered the problem. My submodels had a dot (.) in the title.
> This seemed to confuse LPub and result in the problems I saw. I converted all
> the dots to dashes and now it is OK.
OK, good tip for other users too, to not use dots in filenames.
> This leads me to a couple of other questions next:
>
> I have some assemblies in the model which are mirrored left and right using a
> tranformation matrix. LPub does not show and assembly being built mirrored.
> Any way around this or do I have to actually create all the assemblies
> individually?
I believe you have to create the submodels individually indead. That is what I
always do anyway.
> What about LSynth assemblies? For example, I have a Technic Flexible Axle
> consisting of two ends and a bunch of center parts. I know how to use PLI IGN
> to get it to NOT appear in the parts list, but how I do get an actual flexible
> axle to appear in the parts list?
I'm afraid I do not have the exact answer to that, but I believe LPub it self
draws LSynth pieces in the PLI.
Jaco
| | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Jaco van der Molen wrote:
> In lugnet.cad, Eric Albrecht wrote:
> > I have some assemblies in the model which are mirrored left and right
> > using a tranformation matrix. LPub does not show and assembly being
> > built mirrored. Any way around this or do I have to actually create
> > all the assemblies individually?
>
> I believe you have to create the submodels individually indead.
> That is what I always do anyway.
There are some programs available to create mirrored subparts without
using a mirror matrix.
http://news.lugnet.com/cad/mlcad/?n=2240
I don't know how well they work with all the new parts since they were
developed, but it can't hurt to try them.
Enjoy,
Don
| | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Don Heyse wrote:
> In lugnet.cad, Jaco van der Molen wrote:
> > In lugnet.cad, Eric Albrecht wrote:
>
> > > I have some assemblies in the model which are mirrored left and right
> > > using a tranformation matrix. LPub does not show and assembly being
> > > built mirrored. Any way around this or do I have to actually create
> > > all the assemblies individually?
> >
> > I believe you have to create the submodels individually indead.
> > That is what I always do anyway.
>
> There are some programs available to create mirrored subparts without
> using a mirror matrix.
>
> http://news.lugnet.com/cad/mlcad/?n=2240
>
> I don't know how well they work with all the new parts since they were
> developed, but it can't hurt to try them.
>
> Enjoy,
>
> Don
Further research reveals that, at least in LPub 4.0.0.4, mirroring DOES work
appropriately in the instructions as long as the mirrored submodel is in a
callout. If it is not in a callout (for instance spanning multiple pages), then
it does not display as mirrored, presumably because it is then not linked to the
original model which called it.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Eric Albrecht wrote:
> In lugnet.cad, Don Heyse wrote:
> > In lugnet.cad, Jaco van der Molen wrote:
> > > In lugnet.cad, Eric Albrecht wrote:
> >
> > > > I have some assemblies in the model which are mirrored left and right
> > > > using a tranformation matrix. LPub does not show and assembly being
> > > > built mirrored. Any way around this or do I have to actually create
> > > > all the assemblies individually?
> > >
> > > I believe you have to create the submodels individually indead.
> > > That is what I always do anyway.
> >
> > There are some programs available to create mirrored subparts without
> > using a mirror matrix.
> >
> > http://news.lugnet.com/cad/mlcad/?n=2240
> >
> > I don't know how well they work with all the new parts since they were
> > developed, but it can't hurt to try them.
> >
> > Enjoy,
> >
> > Don
>
> Further research reveals that, at least in LPub 4.0.0.4, mirroring DOES work
> appropriately in the instructions as long as the mirrored submodel is in a
> callout. If it is not in a callout (for instance spanning multiple pages), then
> it does not display as mirrored, presumably because it is then not linked to the
> original model which called it.
I wondered about that. I'll have to look and understand why.
Man, LPub sure has gotten complicated :^) Anyone want to help?
Thanks,
Kevin
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Kevin L. Clague wrote:
> Man, LPub sure has gotten complicated :^) Anyone want to help?
Does finger pointing to bugs count?
http://news.lugnet.com/cad/?n=16523&t=i&v=a
w.
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Willy Tschager wrote:
> In lugnet.cad, Kevin L. Clague wrote:
> > Man, LPub sure has gotten complicated :^) Anyone want to help?
>
> Does finger pointing to bugs count?
>
> http://news.lugnet.com/cad/?n=16523&t=i&v=a
>
> w.
Hi Willy,
This is not the kind of help I was asking about. I was asking if anyone was
interested in helping with the software development of LPub. It is getting too
large for one person to work on alone.
If would seem you have issues with the images created by your renderer. The
black shadows are not under LPub control (I don't think). The parts in the PLI
and the assembly image are PNG images with what is called an alpha channel. The
alpha channel indicates transparency for each pixel in the picture. The PNG
image is rectangular and for most of the pixels in the image, the alpha channel
value (0 - transparent, 0xff is opaque), seem to be correct.
The black shadows that you see along the edges of the parts are where the
alpha channel values are not what you want.
Since LPub does not generate these images, it only uses what is generated, I
do not know how to help you with this problem.
Kevin
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Kevin L. Clague wrote:
> Man, LPub sure has gotten complicated :^) Anyone want to help?
Well, I'm interested in helping to maintain current builds for the Macintosh.
We're still at 4.0.0.1. If you update the SourceForge page with the current
code, I will work on that - and then my interest might be rekindled enough to
delve deeper into other issues.
Jim
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Jim DeVona wrote:
> In lugnet.cad, Kevin L. Clague wrote:
>
> > Man, LPub sure has gotten complicated :^) Anyone want to help?
>
> Well, I'm interested in helping to maintain current builds for the Macintosh.
> We're still at 4.0.0.1. If you update the SourceForge page with the current
> code, I will work on that - and then my interest might be rekindled enough to
> delve deeper into other issues.
>
> Jim
I'm on my way, thanks!
Kevin
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Kevin L. Clague wrote:
> Man, LPub sure has gotten complicated :^) Anyone want to help?
You know I could swear I pointed you towards a potential candidate
for this, like a month or so ago...
https://retracile.net/wiki/2009/10/10/16.45
Did you ever get a chance to follow up on that?
Don
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Don Heyse wrote:
> In lugnet.cad, Kevin L. Clague wrote:
> > Man, LPub sure has gotten complicated :^) Anyone want to help?
>
> You know I could swear I pointed you towards a potential candidate
> for this, like a month or so ago...
>
> https://retracile.net/wiki/2009/10/10/16.45
>
> Did you ever get a chance to follow up on that?
I guess I dropped that ball. Someone contacted me about Lunix patches for LPub,
and I ignored them. I should have encouraged him to put those patches onto
sourceforge himself and join the team. I'll work on that.
>
> Don
Kevin
| | | | | | | | | | | | | | | | | | | | | | | | |
As long as we're having such a good dialog, here is another one. I have a very
large assembly which is too large to fit on one page and still see the building
details. I can zoom in and the assembly simply hangs off the edges of the page.
The portions outside of the margins are cut off. However, what if I don't want
to look at the middle of the assembly? For example, if I drag the whole
assembly off to the right, LPub does NOT redraw the assembly to cut off at the
new margins. Instead the original picture (with the left and right edges cut
off) moves as a whole and nothing is redrawn into the current margins. Hitting
the "regenerate" button doesn't help any. Thoughts?
Eric
| | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Eric Albrecht wrote:
> As long as we're having such a good dialog, here is another one. I have a very
> large assembly which is too large to fit on one page and still see the building
> details. I can zoom in and the assembly simply hangs off the edges of the page.
> The portions outside of the margins are cut off. However, what if I don't want
> to look at the middle of the assembly? For example, if I drag the whole
> assembly off to the right, LPub does NOT redraw the assembly to cut off at the
> new margins. Instead the original picture (with the left and right edges cut
> off) moves as a whole and nothing is redrawn into the current margins. Hitting
> the "regenerate" button doesn't help any. Thoughts?
I think this is a good question for Kevin? ;-)
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Jaco van der Molen wrote:
> In lugnet.cad, Eric Albrecht wrote:
> > As long as we're having such a good dialog, here is another one. I have a very
> > large assembly which is too large to fit on one page and still see the building
> > details. I can zoom in and the assembly simply hangs off the edges of the page.
> > The portions outside of the margins are cut off. However, what if I don't want
> > to look at the middle of the assembly? For example, if I drag the whole
> > assembly off to the right, LPub does NOT redraw the assembly to cut off at the
> > new margins. Instead the original picture (with the left and right edges cut
> > off) moves as a whole and nothing is redrawn into the current margins. Hitting
> > the "regenerate" button doesn't help any. Thoughts?
>
> I think this is a good question for Kevin? ;-)
There is no support in LPub for the case where the assembly image is larger than
the page. Sorry.
Kevin
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Kevin L. Clague wrote:
> In lugnet.cad, Jaco van der Molen wrote:
> > In lugnet.cad, Eric Albrecht wrote:
> > > As long as we're having such a good dialog, here is another one. I have a very
> > > large assembly which is too large to fit on one page and still see the building
> > > details. I can zoom in and the assembly simply hangs off the edges of the page.
> > > The portions outside of the margins are cut off. However, what if I don't want
> > > to look at the middle of the assembly? For example, if I drag the whole
> > > assembly off to the right, LPub does NOT redraw the assembly to cut off at the
> > > new margins. Instead the original picture (with the left and right edges cut
> > > off) moves as a whole and nothing is redrawn into the current margins. Hitting
> > > the "regenerate" button doesn't help any. Thoughts?
> >
> > I think this is a good question for Kevin? ;-)
>
> There is no support in LPub for the case where the assembly image is larger than
> the page. Sorry.
How about a redraw when dragging the assembly?
Jaco
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Jaco van der Molen wrote:
> In lugnet.cad, Kevin L. Clague wrote:
> > In lugnet.cad, Jaco van der Molen wrote:
> > > In lugnet.cad, Eric Albrecht wrote:
> > > > As long as we're having such a good dialog, here is another one. I have a very
> > > > large assembly which is too large to fit on one page and still see the building
> > > > details. I can zoom in and the assembly simply hangs off the edges of the page.
> > > > The portions outside of the margins are cut off. However, what if I don't want
> > > > to look at the middle of the assembly? For example, if I drag the whole
> > > > assembly off to the right, LPub does NOT redraw the assembly to cut off at the
> > > > new margins. Instead the original picture (with the left and right edges cut
> > > > off) moves as a whole and nothing is redrawn into the current margins. Hitting
> > > > the "regenerate" button doesn't help any. Thoughts?
> > >
> > > I think this is a good question for Kevin? ;-)
> >
> > There is no support in LPub for the case where the assembly image is larger than
> > the page. Sorry.
>
> How about a redraw when dragging the assembly?
Sorry, I don't understand what you mean.
Kevin
>
> Jaco
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Kevin L. Clague wrote:
> In lugnet.cad, Jaco van der Molen wrote:
> > In lugnet.cad, Kevin L. Clague wrote:
> > > In lugnet.cad, Jaco van der Molen wrote:
> > > > In lugnet.cad, Eric Albrecht wrote:
> > > > > As long as we're having such a good dialog, here is another one. I have a very
> > > > > large assembly which is too large to fit on one page and still see the building
> > > > > details. I can zoom in and the assembly simply hangs off the edges of the page.
> > > > > The portions outside of the margins are cut off. However, what if I don't want
> > > > > to look at the middle of the assembly? For example, if I drag the whole
> > > > > assembly off to the right, LPub does NOT redraw the assembly to cut off at the
> > > > > new margins. Instead the original picture (with the left and right edges cut
> > > > > off) moves as a whole and nothing is redrawn into the current margins. Hitting
> > > > > the "regenerate" button doesn't help any. Thoughts?
> > > >
> > > > I think this is a good question for Kevin? ;-)
> > >
> > > There is no support in LPub for the case where the assembly image is larger than
> > > the page. Sorry.
> >
> > How about a redraw when dragging the assembly?
>
> Sorry, I don't understand what you mean.
OK, here goes.
When an assembly is too large to fit on the page, LPub crops the image.
When one drags the assembly image to another position LPub does not redraw the
image.
See:
http://www.binarybricks.nl/test/redraw.html
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Jaco van der Molen wrote:
| |
OK, here goes.
When an assembly is too large to fit on the page, LPub crops the image.
When one drags the assembly image to another position LPub does not redraw the
image.
See:
http://www.binarybricks.nl/test/redraw.html
|
Thanks, that’s exactly what I meant. I do instructions for multi thousand part
models, so it is quite common for the assembly not to fit on the page. The
workaround I have used so far is to make my own custom assembly images from
LView and them manually put them in the final PDF file. That’s what I did
here.
Eric
| | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Eric Albrecht wrote:
| |
In lugnet.cad, Jaco van der Molen wrote:
| |
OK, here goes.
When an assembly is too large to fit on the page, LPub crops the image.
When one drags the assembly image to another position LPub does not redraw
the image.
See:
http://www.binarybricks.nl/test/redraw.html
|
Thanks, that’s exactly what I meant. I do instructions for multi thousand
part models, so it is quite common for the assembly not to fit on the page.
The workaround I have used so far is to make my own custom assembly images
from LView and them manually put them in the final PDF file. That’s what I
did here.
Eric
|
In the case of L3P and POV-Ray, there was the ability for look at coordinates so
that you could control what is the center of the viewed image.
If such a mechanism were to exist in LDView and LDGLite, LPub could support
that. This combined with the renderers cropping the image to a known size,
would meet your needs.
I certainly understand the need. Imagine trying to do building instructions for
25 foot buildings. Adam Tucker asked me about this issue years ago at the event
that became Brickworld.
Kevin
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
On 2009-12-05, Kevin L. Clague <kevin_clague@yahoo.com> wrote:
>
> In the case of L3P and POV-Ray, there was the ability for look at coordinates so
> that you could control what is the center of the viewed image.
>
> If such a mechanism were to exist in LDView and LDGLite, LPub could support
> that. This combined with the renderers cropping the image to a known size,
> would meet your needs.
>
> I certainly understand the need. Imagine trying to do building instructions for
> 25 foot buildings. Adam Tucker asked me about this issue years ago at the event
> that became Brickworld.
Hm... wouldn't it be relatively easy to implement (yet effective) just to
have the possibility to define the crop window for a certain assembly step?
That would then work independently on the renderer. And if the coordinates
were given in % instead of pixels or so, it would be even possible to change
resolution without getting different results.
Cheers,
Matija
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Kevin L. Clague wrote:
> In lugnet.cad, Eric Albrecht wrote:
> > In lugnet.cad, Jaco van der Molen wrote:
> > > OK, here goes.
> > > When an assembly is too large to fit on the page, LPub crops the image.
> > > When one drags the assembly image to another position LPub does not redraw
> > > the image.
> > > See:
> > > http://www.binarybricks.nl/test/redraw.html
> >
> > Thanks, that's exactly what I meant. I do instructions for multi thousand
> > part models, so it is quite common for the assembly not to fit on the page.
> > The workaround I have used so far is to make my own custom assembly images
> > from LView and them manually put them in the final PDF file. That's what I
> > did <http://www.brickshelf.com/cgi-bin/gallery.cgi?f=381742 here>.
>
> In the case of L3P and POV-Ray, there was the ability for look at coordinates
> so that you could control what is the center of the viewed image.
I'm not sure what you mean by this. Both LDView and ldglite have ways
to share the coordinates used for a particular viewpoint. Something like
this:
http://ldglite.sourceforge.net/ldglitepov.html
Or do you just want a way to set the "look at" point on the command line.
I believe that's also available in both programs.
> If such a mechanism were to exist in LDView and LDGLite, LPub could support
> that. This combined with the renderers cropping the image to a known size,
> would meet your needs.
>
> I certainly understand the need. Imagine trying to do building instructions
> for 25 foot buildings. Adam Tucker asked me about this issue years ago at
> the event that became Brickworld.
>
> Kevin
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Don Heyse wrote:
> In lugnet.cad, Kevin L. Clague wrote:
> > In lugnet.cad, Eric Albrecht wrote:
> > > In lugnet.cad, Jaco van der Molen wrote:
> > > > OK, here goes.
> > > > When an assembly is too large to fit on the page, LPub crops the image.
> > > > When one drags the assembly image to another position LPub does not redraw
> > > > the image.
> > > > See:
> > > > http://www.binarybricks.nl/test/redraw.html
> > >
> > > Thanks, that's exactly what I meant. I do instructions for multi thousand
> > > part models, so it is quite common for the assembly not to fit on the page.
> > > The workaround I have used so far is to make my own custom assembly images
> > > from LView and them manually put them in the final PDF file. That's what I
> > > did <http://www.brickshelf.com/cgi-bin/gallery.cgi?f=381742 here>.
> >
> > In the case of L3P and POV-Ray, there was the ability for look at coordinates
> > so that you could control what is the center of the viewed image.
>
> I'm not sure what you mean by this. Both LDView and ldglite have ways
> to share the coordinates used for a particular viewpoint. Something like
> this:
>
> http://ldglite.sourceforge.net/ldglitepov.html
>
> Or do you just want a way to set the "look at" point on the command line.
> I believe that's also available in both programs.
>
> > If such a mechanism were to exist in LDView and LDGLite, LPub could support
> > that. This combined with the renderers cropping the image to a known size,
> > would meet your needs.
> >
> > I certainly understand the need. Imagine trying to do building instructions
> > for 25 foot buildings. Adam Tucker asked me about this issue years ago at
> > the event that became Brickworld.
> >
> > Kevin
LPub knows what parts are added at each step. LPub could find the min/max
locations of all parts added and have the look at coordinate be (min_x+max_x)/2,
(min_y+max_y)/2, (min_z+max_z)/2. This would give a general idea of where to
look.
One question is, though can I do this all the time, or should I do it as a
special case? LPub always find the min/max (for all dimensions) for the parts
in the model, and then centers the model on (min_x+max_x)/2, (min_y+max_y)/2,
(min_z+max_z)/2. Maybe now I center it on the "center" of the added parts.
I'll have to play with it and see what I can come up with. I've been away from
LPub for a while and it is hard to ramp back up, but that portion of the code is
pretty straightforward.
Kevin
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Kevin L. Clague wrote:
<snip>
> > > > > When an assembly is too large to fit on the page, LPub crops the image.
> > > > > When one drags the assembly image to another position LPub does not redraw
> > > > > the image.
> > > > > See:
> > > > > http://www.binarybricks.nl/test/redraw.html
> > > >
> > > > Thanks, that's exactly what I meant. I do instructions for multi thousand
> > > > part models, so it is quite common for the assembly not to fit on the page.
> > > > The workaround I have used so far is to make my own custom assembly images
> > > > from LView and them manually put them in the final PDF file. That's what I
> > > > did <http://www.brickshelf.com/cgi-bin/gallery.cgi?f=381742 here>.
> LPub knows what parts are added at each step. LPub could find the min/max
> locations of all parts added and have the look at coordinate be (min_x+max_x)/2,
> (min_y+max_y)/2, (min_z+max_z)/2. This would give a general idea of where to
> look.
>
> One question is, though can I do this all the time, or should I do it as a
> special case? LPub always find the min/max (for all dimensions) for the parts
> in the model, and then centers the model on (min_x+max_x)/2, (min_y+max_y)/2,
> (min_z+max_z)/2. Maybe now I center it on the "center" of the added parts.
>
> I'll have to play with it and see what I can come up with. I've been away from
> LPub for a while and it is hard to ramp back up, but that portion of the code is
> pretty straightforward.
>
> Kevin
Pardon me replying to my own post.....
The above may help with LPub showing the right portion of a large mode, but it
doesn't help with cropping the image size to contain what has changed, which I
think would have a significant impact on building instruction size. LEGO does
occasionally show cropped portions of whole model images, but they don't do that
as a general rule. But then again, they don't generally sell 25 foot tall Sears
towers.
LPub already has a mechanism for identifying where callouts are added to a model
so it can place the arrows from the callout to the center of the callout usage.
I suppose it could do a similar thing for "parts added in this step" and crop
the image to contain those. I'm pretty sure that would not be the default
behavior though. Egads, more features.
I gotta get through the backlog of bugs first.
Kevin
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Kevin L. Clague wrote:
>
> The above may help with LPub showing the right portion of a large mode, but it
> doesn't help with cropping the image size to contain what has changed, which I
> think would have a significant impact on building instruction size. LEGO does
> occasionally show cropped portions of whole model images, but they don't do that
> as a general rule. But then again, they don't generally sell 25 foot tall Sears
> towers.
>
> LPub already has a mechanism for identifying where callouts are added to a model
> so it can place the arrows from the callout to the center of the callout usage.
> I suppose it could do a similar thing for "parts added in this step" and crop
> the image to contain those. I'm pretty sure that would not be the default
> behavior though. Egads, more features.
>
> I gotta get through the backlog of bugs first.
No rush Kevin. There are probably not too many of us making instructions for
models of this size, and we at least have (painful) workarounds in the interim.
If you never get to it, I'm still very thankful for LPub, and if you do get to
it, you are just that much more awesome.
I've always thought that you should test out large LPub models by making
instructions for your pneumatic hexapod and then giving them to me. ;-)
Eric
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Eric Albrecht wrote:
> No rush Kevin. There are probably not too many of us making instructions for
> models of this size, and we at least have (painful) workarounds in the interim.
> If you never get to it, I'm still very thankful for LPub, and if you do get to
> it, you are just that much more awesome.
As a matter of fact I am creating buildinginstructions for a model that
eventually goes of the page, but for now I just scale down the assembly size as
the model grows.
But I totally agree with Eric: no rush and thanks for LPub!
Jaco
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Jaco van der Molen wrote:
> In lugnet.cad, Eric Albrecht wrote:
> > No rush Kevin. There are probably not too many of us making instructions for
> > models of this size, and we at least have (painful) workarounds in the interim.
> > If you never get to it, I'm still very thankful for LPub, and if you do get to
> > it, you are just that much more awesome.
>
> As a matter of fact I am creating buildinginstructions for a model that
> eventually goes of the page, but for now I just scale down the assembly size as
> the model grows.
Bringing this feature request back to life ... I'm working on a project now
that's 45 bricks tall.
I'd love the ability to reposition the image inside the crop window, or specify
if I'd like the top, bottom, or both (current behavior) to be cropped when the
model is too big for a page.
- Robert
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Eric Albrecht wrote:
> In lugnet.cad, Kevin L. Clague wrote:
> >
> > The above may help with LPub showing the right portion of a large mode, but it
> > doesn't help with cropping the image size to contain what has changed, which I
> > think would have a significant impact on building instruction size. LEGO does
> > occasionally show cropped portions of whole model images, but they don't do that
> > as a general rule. But then again, they don't generally sell 25 foot tall Sears
> > towers.
> >
> > LPub already has a mechanism for identifying where callouts are added to a model
> > so it can place the arrows from the callout to the center of the callout usage.
> > I suppose it could do a similar thing for "parts added in this step" and crop
> > the image to contain those. I'm pretty sure that would not be the default
> > behavior though. Egads, more features.
> >
> > I gotta get through the backlog of bugs first.
>
>
> No rush Kevin. There are probably not too many of us making instructions for
> models of this size, and we at least have (painful) workarounds in the interim.
> If you never get to it, I'm still very thankful for LPub, and if you do get to
> it, you are just that much more awesome.
Thanks Eric.
>
> I've always thought that you should test out large LPub models by making
> instructions for your pneumatic hexapod and then giving them to me. ;-)
Well, let me tell you, that the hardest part about the pneumatic walkers is
getting all hoses on correctly. It is even harder within LDraw and LSynth! I
hear there is a new LSynth out there that produces much smaller files than it
used to though! LSynth is being better maintained than LPub, thanks to Don and
Willy.
>
> Eric
Kevin
| | | | | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Jaco van der Molen wrote:
> In lugnet.cad, Eric Albrecht wrote:
> > Thanks Jaco. Through the process of doing it manually and a lot of other trial
> > and error, I discovered the problem. My submodels had a dot (.) in the title.
> > This seemed to confuse LPub and result in the problems I saw. I converted all
> > the dots to dashes and now it is OK.
>
> OK, good tip for other users too, to not use dots in filenames.
While creating instructions I have discovered that you can use extra dots in
filenames as long as the name of the model before the first dot is unique per
step in a callout.
For example if you a filename like submodel.1.ldr and submodel.2.ldr and call
them both out in the same step on the same page it won't work. The contents the
callout for submodel.2 will be the same as submodel.1.
If you use only one, it's OK. If you call them submodelA.1.ldr and
submodelB.1.ldr it's OK.
Jaco
| | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Eric Albrecht wrote:
> What about LSynth assemblies? For example, I have a Technic Flexible Axle
> consisting of two ends and a bunch of center parts. I know how to use PLI IGN
> to get it to NOT appear in the parts list, but how I do get an actual flexible
> axle to appear in the parts list?
LSynth 3.0 comes with PLI_TECHNIC_AXLE_FLEXIBLE_x meta commands. If your
Synthesis is not supported use this workaround:
http://news.lugnet.com/cad/?n=16523
w.
| | | | | | | | | | | | | | | | | | | | |
In lugnet.cad, Willy Tschager wrote:
>
> LSynth 3.0 comes with PLI_TECHNIC_AXLE_FLEXIBLE_x meta commands. If your
> Synthesis is not supported use this workaround:
Thanks! I did not know about this. Presuming that I have already synthesized
the axles, can I just change the Synth command to what you have above, or do I
need to re-synthesize? Does LSynth take the length into account when
synthesizing and adjust the routing accordingly?
I had seen the "PLI**" options on the LSynth list and didn't really know what
they meant.
Eric
| | | | | | | | | | | | | | | | | | | |
| |
|
In lugnet.cad, Eric Albrecht wrote:
> In lugnet.cad, Jaco van der Molen wrote:
> >
> > I do not experience any problems in creating callouts.
> > Positioning them is sometimes a bit tricky.
> > Adding them manually is always a good thing to try.
> > The syntax is this:
> >
> > 0 !LPUB CALLOUT BEGIN
> > 1 x x x x x x submodel.ldr
> > 0 !LPUB CALLOUT END
>
> Thanks Jaco. Through the process of doing it manually and a lot of other trial
> and error, I discovered the problem. My submodels had a dot (.) in the title.
> This seemed to confuse LPub and result in the problems I saw. I converted all
> the dots to dashes and now it is OK.
>
> This leads me to a couple of other questions next:
>
> I have some assemblies in the model which are mirrored left and right using a
> tranformation matrix. LPub does not show and assembly being built mirrored.
> Any way around this or do I have to actually create all the assemblies
> individually?
So many features, so few memories. The latest version of LPub (at least the
Windows one), has support for mirrored sub-models. It knows about mirrored
matricies (thanks to minds here that are mathematically superior to mine :^)
One test model I use has lots of mirrored sub-assemblies and they work fine.
>
> What about LSynth assemblies? For example, I have a Technic Flexible Axle
> consisting of two ends and a bunch of center parts. I know how to use PLI IGN
> to get it to NOT appear in the parts list, but how I do get an actual flexible
> axle to appear in the parts list?
>
> Thanks for any help.
> Eric
Kevin
| | | | | | |
