X2 Rotate Geometry but some gets left behind

[cired]

I've run into this problem a few times now and wanted to ask if anyone else has come across this. On certain files if you "transform rotate" your geometry, it sometimes leaves a portion of geometry behind. On the rotated part that geometry is now blank. The only way we have found to rotate the geometry properly is to painfully go back to version 9 where it works with no problem. We have two Quadro video cards and 1 gaming card with the latest drivers and they all equally seem to show the same problem. One other thing worth mentioning is our operating systems are Windows 2000, why I am not sure. It's what the boss wants.

[Matt Berube at Ferron Mold]

Hello cired and welcome to the forum. I see you've been reading for a while before making your first post.

 

Are you using Mastercam X2 or X or what?

 

What type of entities are left behind ?

 

I get the impression that there are a few challenges for Windows 2000 users that I have not seen on XP.

[cired]

Thanks Matt for the reply. We are using the latest version of Mastercam X2.

[Kyle Waters]

Not sure if this is related, but I did a part just last week that I had xform rotated for 9 set-ups, and it copied the wireframe to each xform rotate with the setting to "move" not "copy". Only the wireframe was copied, the solid was fine. I assumed it was because I don't know what I am doing.

[Matt Berube at Ferron Mold]

Slave,

 

That happens whenever you have geometry required by the solid.

 

I think Mastercam can't be sure if you still need the wireframe in the original location but it definitely needs to bring the wireframe along with the solid so you get the extra copies.

 

If you used the "nohist" c-hook before your xform you would not get the copies. Be aware however that using the nohist c-hook destroys the solid history tree. This means that you can no longer easily edit the solid.

 

I sometimes *copy* the solid onto another level and use nohist on the copy then xform it as necessary. This way I get the best of both worlds... I can xform without leaving a trail of wireframe behind but I can also go back to my original solid if necessary.

[Kyle Waters]

Matt,

I was keeping my geo so that I could maintain my associativity. I didn't actually notice all the copies of geometry until I went to change levels. It seems like the system should still pick up the relationship. Move solid, move geometry. I do use the c-hook sometimes, but not too often. I don't like the idea of going thru any more work than I have to. Now since you gave me the idea of copying the solid, I will give it a try. Thanks!

[Bruce Gibson]

slave, why not use the wcs? you do not have to move any geo, or lose any associativity.

[Kyle Waters]

Bruce, I always end up taking longer to be sure that I moved the wcs the right way. I am hoping to get it down someday though, creating a 3d model from 2d drawings eats up alot of my time. Maybe I will give it another try...