LDraw.org Discussion Forums

Full Version: Change the view of a Callout
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello,

I use one sub-models twice, but the second time the sub-model was rotatet by 180°. In the following picture you can see the first use of the sub-model and the callout.

[attachment=5664]

In the following picture you can see the second use of the same sub-model and the callout.

[attachment=5665]

What do I have to do to make the second callout look the same as the first callout?
In the following picture you can see a part of the "code" for the instruction.

[attachment=5666]

Regards

Manfred
I would use a rotstep 0 180 0 rel statement in the call-out....
(2020-08-31, 15:46)Philippe Hurbain Wrote: [ -> ]I would use a rotstep 0 180 0 rel statement in the call-out....






Hello Philippe,



Thank you for your reply.



I changed the code as follows:


[attachment=5673]



In this step the following error message was displayed:



[attachment=5675]



After pressing the OK field, the sheet is displayed.

But the result is wrong



[attachment=5674]



The callout (picture) is missing. I forgot to say, I am using version 2.3.6.

Regards

Manfred
(2020-09-01, 15:19)Manfred Schäfer Wrote: [ -> ]Hello Philippe,



Thank you for your reply.



I changed the code as follows:






In this step the following error message was displayed:







After pressing the OK field, the sheet is displayed.

But the result is wrong







The callout (picture) is missing. I forgot to say, I am using version 2.3.6.

Regards

Manfred
Hi

Did you change anything in the matrix?
The correct line for the second callout should be:
1 19 0 -24 0 -1 0 0 0 1 0 0 0 -1 Sub 21002-001.ldr

Philos opinion was you should insert the ROTSTEP command in front of the code in the callout.
Between the header an the first part line..
But this will probably not cause any change, except that the first callout is then also rotated.

Johann
(2020-09-01, 15:49)Johann Eisner Wrote: [ -> ]But this will probably not cause any change, except that the first callout is then also rotated.

Johann
Johann is right, if it's the same submodel, rotstep is not a solution. Or you would need to duplicate it...
(2020-09-01, 15:49)Johann Eisner Wrote: [ -> ]Hi

Did you change anything in the matrix?
The correct line for the second callout should be:
1 19 0 -24 0 -1 0 0 0 1 0 0 0 -1 Sub 21002-001.ldr

Philos opinion was you should insert the ROTSTEP command in front of the code in the callout.
Between the header an the first part line..
But this will probably not cause any change, except that the first callout is then also rotated.

Johann

Thanks Johann.
First I used the matrix to rotate the sub part, but the parts in the callout was also rotated. I can not make any changes in the sub part as this will affect the first time the sub part is used.

Regards

Manfred
(2020-09-01, 17:00)Philippe Hurbain Wrote: [ -> ]Johann is right, if it's the same submodel, rotstep is not a solution. Or you would need to duplicate it...

Hello Philippe,

I want to avoid duplicating the sub part.

Regards

Manfred
(2020-09-01, 18:44)Manfred Schäfer Wrote: [ -> ]Thanks Johann.
First I used the matrix to rotate the sub part, but the parts in the callout was also rotated. I can not make any changes in the sub part as this will affect the first time the sub part is used.

Regards

Manfred
Hi Manfred

I can't understand you.
You have only to change the last "1" in the callout line to a "-1" and he callout should be shown correct.
[attachment=5676]

I made a quick project, and it works fine.
[attachment=5677]

Code is attached.
(2020-09-01, 19:02)Johann Eisner Wrote: [ -> ]Hi Manfred

I can't understand you.
You have only to change the last "1" in the callout line to a "-1" and he callout should be shown correct.


I made a quick project, and it works fine.


Code is attached.

Hello Johann,

that is the solution. I included this solution in my project and it works wonderfully.
Many thanks. Smile

Regards

Manfred
Hello,

I have another problem. I would like to insert a part into another part upside down. In this section I want to use a callout. In the following picture you can see the first part.

[attachment=5698]

In the second picture you see the first and the scond part, but the second part with the wrong direction.

[attachment=5699]

The line which call the subpart: 1 1 0 -40 0 1 0 0 0 1 0 0 0 1 1.ldr

I hace changed the second "1" (red coloured) in the matrix to "-1". In the next picture you can see the result.

[attachment=5700]

Both parts, the part in the callout and the part in the page was rotated. But I want only rotate the part in the page.
I have attached the code.

My qustions now are:
How looks the matrix that the result is as I wish?
How is the impact of the matrix at the callout?

Regards

Manfred
(2020-09-10, 19:07)Manfred Schäfer Wrote: [ -> ]Hello,

I have another problem. I would like to insert a part into another part upside down. In this section I want to use a callout. In the following picture you can see the first part.



In the second picture you see the first and the scond part, but the second part with the wrong direction.



The line which call the subpart: 1 1 0 -40 0 1 0 0 0 1 0 0 0 1 1.ldr

I hace changed the second "1" (red coloured) in the matrix to "-1". In the next picture you can see the result.



Both parts, the part in the callout and the part in the page was rotated. But I want only rotate the part in the page.
I have attached the code.

My qustions now are:
How looks the matrix that the result is as I wish?
How is the impact of the matrix at the callout?

Regards

Manfred

Hi Manfred
The attached code works for me without any problems.
I suspect you rotated the model with a ROTSTEP command before adding the callout.
As a result, the callout also adopts this "relative" rotation.
You can remedy this, as briefly written above, by inserting the line “0 ROTSTEP 0 0 0 REL” in the sub-model of the callout after the header before the first part.

New partfile is attached.
(2020-09-12, 16:17)Johann Eisner Wrote: [ -> ]Hi Manfred
The attached code works for me without any problems.
I suspect you rotated the model with a ROTSTEP command before adding the callout.
As a result, the callout also adopts this "relative" rotation.
You can remedy this, as briefly written above, by inserting the line “0 ROTSTEP 0 0 0 REL” in the sub-model of the callout after the header before the first part.

New partfile is attached.


Hi Johann,



Thank you for your answer. Unfortunately, it didn't work for me. The code looks like this:

0 FILE part.mpd
0 Name: Part
0 !LPUB CALLOUT PLI PER_STEP GLOBAL FALSE
0 ROTATION CENTER 0 0 0 1 "Custom"
0 ROTATION CONFIG 0 0
1 0 8.787 -8 -31.213 0.707107 0 0.707107 0 -1 0 0.707107 0 -0.707107 3023.dat
1 0 15.858 0 -24.142 -0.707107 0 -0.707107 0 -1 0 -0.707107 0 0.707107 63864.dat
1 0 51.213 0 -31.213 -0.707107 0 0.707107 0 -1 0 0.707107 0 0.707107 3069b.dat
1 0 44.142 -8 -24.142 -0.707107 0 0.707107 0 -1 0 0.707107 0 0.707107 3623.dat
1 1 30 -16 -10 0.707107 0 -0.707107 0 -1 0 -0.707107 0 -0.707107 2420.dat
0 STEP
0 !LPUB CALLOUT BEGIN
1 1 0 -40 0 1 0 0 0 -1 0 0 0 1 1.ldr
0 !LPUB CALLOUT PLACEMENT RIGHT CENTER ASSEM OUTSIDE OFFSET 0.4866 -1.7853
0 !LPUB CALLOUT END
0 STEP
0 NOFILE
0 FILE 1.ldr
0 Name: 1.ldr
0 Author: Manfred Schäfer
0 ROTSTEP 0 0 0 REL
1 1 30 0 -20 1 0 0 0 1 0 0 0 1 3003.dat
0 STEP
1 1 20 -16 -10 0 0 1 0 1 0 1 0 0 6091.dat
1 1 20 -16 -30 0 0 1 0 1 0 1 0 0 6091.dat
1 1 40 -16 -10 0 0 -1 0 1 0 -1 0 0 6091.dat
1 1 40 -16 -30 0 0 -1 0 1 0 -1 0 0 6091.dat
0 STEP
1 1 30 -16 -30 1 0 0 0 1 0 0 0 -1 3794a.dat
1 1 30 -16 -10 1 0 0 0 1 0 0 0 -1 3069b.dat
0 STEP
0 NOFILE



The result (2nd page) looks like this:



[attachment=5713]



What I expected or how it should be is like this:



[attachment=5712]



I use the Version 2.3.13 (latest Version)


Regards



Manfred
(2020-09-14, 11:12)Manfred Schäfer Wrote: [ -> ]Hi Johann,
Thank you for your answer. Unfortunately, it didn't work for me. The code looks like this:

0 FILE part.mpd
0 Name: Part
0 !LPUB CALLOUT PLI PER_STEP GLOBAL FALSE
0 ROTATION CENTER 0 0 0 1 "Custom"
0 ROTATION CONFIG 0 0
1 0 8.787 -8 -31.213 0.707107 0 0.707107 0 -1 0 0.707107 0 -0.707107 3023.dat
1 0 15.858 0 -24.142 -0.707107 0 -0.707107 0 -1 0 -0.707107 0 0.707107 63864.dat
1 0 51.213 0 -31.213 -0.707107 0 0.707107 0 -1 0 0.707107 0 0.707107 3069b.dat
1 0 44.142 -8 -24.142 -0.707107 0 0.707107 0 -1 0 0.707107 0 0.707107 3623.dat
1 1 30 -16 -10 0.707107 0 -0.707107 0 -1 0 -0.707107 0 -0.707107 2420.dat
0 STEP
0 !LPUB CALLOUT BEGIN
1 1 0 -40 0 1 0 0 0 -1 0 0 0 1 1.ldr
0 !LPUB CALLOUT PLACEMENT RIGHT CENTER ASSEM OUTSIDE OFFSET 0.4866 -1.7853
0 !LPUB CALLOUT END
0 STEP
0 NOFILE
0 FILE 1.ldr
0 Name: 1.ldr
0 Author: Manfred Schäfer
0 ROTSTEP 0 0 0 REL
1 1 30 0 -20 1 0 0 0 1 0 0 0 1 3003.dat
0 STEP
1 1 20 -16 -10 0 0 1 0 1 0 1 0 0 6091.dat
1 1 20 -16 -30 0 0 1 0 1 0 1 0 0 6091.dat
1 1 40 -16 -10 0 0 -1 0 1 0 -1 0 0 6091.dat
1 1 40 -16 -30 0 0 -1 0 1 0 -1 0 0 6091.dat
0 STEP
1 1 30 -16 -30 1 0 0 0 1 0 0 0 -1 3794a.dat
1 1 30 -16 -10 1 0 0 0 1 0 0 0 -1 3069b.dat
0 STEP
0 NOFILE

The result (2nd page) looks like this:
What I expected or how it should be is like this:
I use the Version 2.3.13 (latest Version)

Regards
Manfred
Hi Manfred

I have no idea why it doesn't work for you, but the following solution:
Replace the ROTSTEP command in the callout submodel (Marked red above)with "0 ROTSTEP 0 0 180 REL" then it should work for you too.

Regards Johann
(2020-09-14, 15:58)Johann Eisner Wrote: [ -> ]Hi Manfred

I have no idea why it doesn't work for you, but the following solution:
Replace the ROTSTEP command in the callout submodel (Marked red above)with "0 ROTSTEP 0 0 180 REL" then it should work for you too.

Regards Johann

Hello Johann,

Thank you for your prompt reply. With this change, it works.
You think the reason for this failure is my system?
I had tried it on another PC before and the result was the same.
The next days I will do a new installation of the LDRAW-suite.

Can you tell me how the ROTSTEP command or the transformation matrix affects the display of the CALLOUT.
I can't explain to me why the ROTSTEP command in the sub-model was the solution to my problem.

Thank you.

Regards

Manfred