LPub: Repeating a submodel/callout

[peedeejay]

I have the following problem: Within my MLCad file I have a submodel which is used multiple times within my model. However the repeated usage is not during the same step. First the submodel is used at step 6 for example and then again at step 12.

When I work within LPub I receive the assembly page for the submodel with a "x2" the first time the submodel is used (e.g. step 6). Within the next step of my instruction the submodel is only placed once. When I reach the next step where the submodel is used (e.g. step 12) the submodel is placed but without any assembly page (or callout) before.

Is there any way to repeat the assembly page? I know that I can create a workaround by creating the submodel twice in MLCad even though they look exactly the same, but this would be kinda dull...

[peedeejay]

Hmm I have the same situation with a different submodel at a later step within the instruction and here LPub does repeat the assembly page. So weird..

[Classicsmiley]

Here's a quick test I did in LPub3D. Is that the effect you're trying to achieve?

Sample File

[peedeejay]

Yeah exactly. With the exception that there are different steps in between the multiple usage of the submodel. Sometimes it seems to work and sometimes it doesn't. Still trying to figure out when it works and when not.

[Alasdair Ryan]

You can simply rename the sub-model in question ,Lpub matches the instances of bricks/models/sub-models.

[Classicsmiley]

Yeah exactly. With the exception that there are different steps in between the multiple usage of the submodel. Sometimes it seems to work and sometimes it doesn't. Still trying to figure out when it works and when not.

When in doubt, use LPub to strip the LPub comments out of your file, and start over. Yes, it's a pain, especially with larger models, but sometimes it's what is necessary.

Here's an updated sample file, showing a couple of steps in between uses of the submodel. I can PM you my email address, if you'd like me to take a look at your file.

[Rane]

Hey guys! Bumping an old thread to add further info and with the hope that someone might have a solution...

The sample file above is great, but doesn't solve my problem (or the OP's, if I understood correctly). Call-outs (as demoed in the sample file) seem to work just as you would hope. That is, they repeat for every instance of a sub-model being used in a set, even if used many steps later.

However. If you don't convert your sub-model to a call-out (say it's too big) it does that "x2" (or however many) in the corner and refuses to repeat your assembly page again. Also if you "add assembled image to parent page" it only does it the first time. There doesn't seem to be a way to do it for the subsequent uses of the same sub-model.

Unless I'm mistaken, It looks like the only way to around this is to never use a sub-model twice.

P.S. I'm just learning this after finishing organizing all the sub-models, and steps for a 7500 pieces set. >:(

[legolijntje]

This might be a nice new feature in LPub3D. I'll make a request tomorrow :)

[Alasdair Ryan]

Let me just quote myself from four replies ago,this should fix your problem.

You can simply rename the sub-model in question ,Lpub matches the instances of bricks/models/sub-models.

[Rane]

This might be a nice new feature in LPub3D. I'll make a request tomorrow :)

Cool! In the mean time, I actually got lucky. I only had a handful of sub-models large enough to need dedicated pages. The rest are all call-outs, so I was able to just duplicate and replace the affected models without too much trouble.

Let me just quote myself from four replies ago,this should fix your problem.

You can simply rename the sub-model in question ,Lpub matches the instances of bricks/models/sub-models.

I read this a couple of times, but couldn't make sense of how it could help. If I have a sub-model and rename it, isn't it still the same sub-model? I can duplicate it under a different name so that there's a copy for each instance of the sub-model. Then just swap in a duplicate for each of the sub-model's repeated instances (which is what I ended up doing). Just renaming the sub-model doesn't seem to help (so far as I could tell).

[Alasdair Ryan]

I read this a couple of times, but couldn't make sense of how it could help. If I have a sub-model and rename it, isn't it still the same sub-model? I can duplicate it under a different name so that there's a copy for each

Sorry If you misunderstood, but that is exactly what I was suggesting you do (duplicate and rename one to something different).

Edited August 15, 2016 by Alasdair Ryan

[Rane]

Sorry If you misunderstood, but that is exactly what I was suggesting you do (duplicate and rename one to something different).

Ah, I see. I did end up doing just that. I was horrified at the thought of having to go back and swap all the sub-models at first, but it turned out that of the over 600 sub-models in my creation, most of the duplicates were small enough that they'd just be call-outs anyway. I ended up only having to replace about 6.

I like LPUB, but it is thoroughly unforgiving. Your only option is to adapt to how it wants you to do things. It's not a problem once you know, but it makes no effort to ease you into the leaning process. lol

[1963maniac]

Classicsmiley, in your updated sample file how do the two black 1x2 plates become a single line of code ending with ldr instead of dat in MLCAD?

Edited March 11, 2017 by 1963maniac