Failed to get Target Occurrence Transform after Copy New

Failed to get Target Occurrence Transform after Copy New

fsonnichsen
Collaborator Collaborator
15,386 Views
7 Replies
Message 1 of 8

Failed to get Target Occurrence Transform after Copy New

fsonnichsen
Collaborator
Collaborator

I see some reference to this but not necessarily the same problem and not necessarily resolved.

I am simply copying one component to another using the "New Component" command and I get the two yellow items in my timeline stating "Failed to get Target Occurrence Transform after Copy New".

  Any ideas what this elegant message means? f3d attached.

Thanks

Fritz

0 Likes
Accepted solutions (3)
15,387 Views
7 Replies
Replies (7)
Message 2 of 8

davebYYPCU
Consultant
Consultant
Accepted solution

I am simply copying one component to another using the "New Component" command

 

May have something to do with it,  does this help, I rearranged the file - deleted the stuff from those two warnings, 

best to make components and then activate them.  Copied the cap, as I think you need it, 

 

 

Your error for the sketch was a lost projection of the origin. 

Your copy paste got buried in an assembly that I don't know was the intention, could be wrong.

 

Might help....

0 Likes
Message 3 of 8

jeff_strater
Community Manager
Community Manager

can you show the exact steps you went through to get this error?  I'm not certain what "I am simply copying one component to another using the "New Component" command " means.  A screencast would be the ideal way to do this.

 

Thanks!


Jeff Strater
Engineering Director
0 Likes
Message 4 of 8

fsonnichsen
Collaborator
Collaborator

 

 
 
 
 
 
 
 
 
 
 
 
 
Jeff-see if this screen cast URL works--sometimes it does not. And when I select from "My ScreenCasts" I always get an error.
 
Per Dave' response-I did have a "double layered" construct in my example which did not help-but I corrected it in the screencast and I still see the problem.
 
cheers
FRitz
 
 
 
 
 
 
 
 
 
 
0 Likes
Message 5 of 8

fsonnichsen
Collaborator
Collaborator

 

 
 
 
 
 
 
 
 
 
 
 
 
Jeff-see if this screen cast URL works--sometimes it does not. And when I select from "My ScreenCasts" I always get an error.
 
Per Dave' response-I did have a "double layered" construct in my example which did not help-but I corrected it in the screencast and I still see the problem.
 
cheers
FRitz
 
 
 
 
 
 
 
 
 

 

 
 
 
 
 
 
 
 
 
 
 
 
Jeff-see if this screen cast URL works--sometimes it does not. And when I select from "My ScreenCasts" I always get an error.
 
Per Dave' response-I did have a "double layered" construct in my example which did not help-but I corrected it in the screencast and I still see the problem.
 
cheers
FRitz
 
Trying again-this time instream--the email from Screencast "claims" this URL is public,
 
 
 
 
 
 
 
 
 
0 Likes
Message 6 of 8

jhackney1972
Consultant
Consultant
Accepted solution

Take a look at the Screencast.  You got off track when you forgot to Activate the Cap before you did the Revolve and since the body appeared outside of the component, you tried to drag it to the correct position in the Browser.  Sometimes you can get away with this but not in your case.  Notice how going back in the timeline and executing the creation of the cap body, with the component active, solves you whole issue.  Model is attached.

John Hackney, Retired
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature

Message 7 of 8

jeff_strater
Community Manager
Community Manager
Accepted solution

@fsonnichsen , thanks for the screencast.  @jhackney1972 is correct about the way to avoid this.  However, this should still not cause the warnings you are seeing, so we need to investigate this a bit.  I'll create a bug for it.

 

[edit] created bug FUS-83436 for this issue


Jeff Strater
Engineering Director
0 Likes
Message 8 of 8

fsonnichsen
Collaborator
Collaborator

OK and thanks all for your inputs.  There are a few workarounds as Dave and John indicate. I don't always end up with the most efficient path to a design, largely due to lack of experience but also because I sometimes design as I think the problem thru--nothing like thinking ahead I suppose!

  I appreciate this being viewed as a bug as I know I will step into it again sometime!

 

cheers

Fritz

 

0 Likes