Group removed inside a callout still visible on the main model


Group removed inside a callout still visible on the main model
#1
Hello guys
i have a main model with a callout. Inside callout i use the command to remove a group
Code:
0 !LPUB REMOVE GROUP

and it works prefectly during callout steps, but when i return in the main model step with the submodel placed i still see parts removed before.
Is it possible to not show in the upper model the parts removed with REMOVE GROUP command?

You can find an example attached.

thanks
regards

Simon


Attached Files
.ldr   removegroup sample.ldr (Size: 1.06 KB / Downloads: 2)
Reply
RE: Group removed inside a callout still visible on the main model
#2
(2018-11-10, 15:21)Simone Wrote: Hello guys
i have a main model with a callout. Inside callout i use the command to remove a group
Code:
0 !LPUB REMOVE GROUP

and it works prefectly during callout steps, but when i return in the main model step with the submodel placed i still see parts removed before.
Is it possible to not show in the upper model the parts removed with REMOVE GROUP command?

You can find an example attached.

thanks
regards

Simon


Hi Simon

I think, this is a bug.
I have the same problem.
Have you post the problem already at github?
Or should I?

Regards Johann
If nothing goes right, go left.
Reply
RE: Group removed inside a callout still visible on the main model
#3
Hi Johann, no i didn't open any issue on github.


About github, do you mean opening a ticket on LPub3D github page?

thanks
regards

Simon
Reply
RE: Group removed inside a callout still visible on the main model
#4
(2018-11-11, 20:07)Simone Wrote: Hi Johann, no i didn't open any issue on github.


About github, do you mean opening a ticket on LPub3D github page?

thanks
regards

Simon


Yes, that I mean.
Regards Johann
If nothing goes right, go left.
Reply
RE: Group removed inside a callout still visible on the main model
#5
Hi Johann
ticket opened
https://github.com/trevorsandy/lpub3d/issues/158

For the moment i solved by using buffer exchange as workaround.

Regards

Simon
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 1 Guest(s)
Forum Jump:


Users browsing this thread: 1 Guest(s)