topic Re: Importing and rotating/translating in Fusion Design, Validate & Document Forum

Importing and rotating/translating

JetForMe — Thu, 04 Feb 2016 21:46:13 GMT

I got a .STEP file from Orange Vise for one of their vises. I imported it into a new design. The thumbnail shows it in a reasonable orientation, but when I open the design, it is rotated 90°. So I tried using the Modify->Move command, set for Move Components, and marquee-selecting the whole thing (it's several components).

When I rotate that, all the separate components go off in different directions.

Here's my file: http://a360.co/1QfWyrW

This is the second thing I've imported that showed up correclty in the thumbanil but ends up rotated in the design file. Also, it's translated away from the origin when I rotate it back to the right orientation; is there a quick and easy way to translate something down so one of its surfaces is at the origin?

Thanks.

Re: Importing and rotating/translating

TrippyLighting — Thu, 04 Feb 2016 22:07:47 GMT

Don't select objects in the viewport if you want to move them. In default setting that will move the body in the component and most likely is not what you want to do.

Select the Vise Component in the browser tree and then use the move command.

Be aware of the difference between a component and a body.

To create new stuff, first create a component and activate it if isn't. Always activate components before adding to them.

Re: Importing and rotating/translating

JetForMe — Thu, 04 Feb 2016 23:49:05 GMT

Selecting bodies via the tree allowed me to rotate them together. How is that different from marquee-selecting?

Thanks!

Re: Importing and rotating/translating

TrippyLighting — Thu, 04 Feb 2016 23:52:32 GMT

I told you that already 😉

When you marquee select in the viewport you are selecting the bodies in the component(s).

When you select from the browser you select a component.

Please follow the link I posted to understand what makes a component different from a body.

Re: Importing and rotating/translating

JetForMe — Fri, 05 Feb 2016 00:02:02 GMT

I misunderstood my design. I thought they were bodies, not components. Also, I still don't see why rotating bodies or components would be different in a situation like this. It seems like it's applying the rotation to the component, then again to the body relative to the component. I consider that a bug, as I can't imagine any use case where you'd actually want that.

In any case, that worked, even if it is more cumbersome than just being able to slect the components in the view.

Re: Importing and rotating/translating

TrippyLighting — Fri, 05 Feb 2016 00:07:02 GMT

I agree with that being somewhat cumbersome, as I would also prefer to work more in the viewport. But rhen, once you get used to it.....

I'ts definitely not a bug! You may not yet understand the need for moving a body independent from a component, but you certainly will as you gain confidence with Fusion .

Re: Importing and rotating/translating

JetForMe — Fri, 05 Feb 2016 00:11:30 GMT

I completely understand the need for moving a body independently of a component. I'm saying that if I select a bunch of bodies and components together and move them, I consider it a bug that they move in different directions.

Of course, if I select a body by itself, it should move independently of the other bodies and components.

Re: Importing and rotating/translating

TrippyLighting — Fri, 05 Feb 2016 00:13:32 GMT

Yes, but you did not select bodies and components together. When you marquee select, you only select the bodies, not the components.

Re: Importing and rotating/translating

TrippyLighting — Fri, 05 Feb 2016 00:20:55 GMT

Hmmm....I just tried something. Could you share the model of that Vice and also create a screencast of that behavior ?

I created a quick and dirty mockup, but it did not behave the way you described it an I'd hate to ignore a real bug!

Re: Importing and rotating/translating

JetForMe — Fri, 05 Feb 2016 00:29:56 GMT

Here's the screencast: http://cl.ly/382Y1Q0p1X3M

And the file I imported: http://cl.ly/1s1G2P181L2j

Re: Importing and rotating/translating

TrippyLighting — Fri, 05 Feb 2016 02:06:43 GMT

Thanks for posting this! Before I can answer I need to wait for the answer to a question I posted in another thread with a related topic.

here are a few things to know already:

When you import an assembly say from a STEP or IGES ile all the part are not mated to each otehr. You can move them independent from each other.

teh other thing is that per default for imported geometry filesthe timeline recording is turned off, which couses the parts to behave slightly differetn in the viewport.

When timeline recording is turned off, even when the parts are not mated/joined you cannot just drage them aroung with the mouse in the viewport. That does not mesn however that they are properly joined.

With timeline recording turend on, you can simply pick an unjoined component and drag it around wothout having to use the move command.

As it appears right now in order to ge this assembly to locate at the propoer origin in the Vice assembly, all the components and subassemblies have to be joined in the correct sequence and only then teh whiole assembly can be aligned trotated to the origin and then you can ground the body of the vise to lock it in place.

Re: Importing and rotating/translating

JetForMe — Fri, 05 Feb 2016 02:14:47 GMT

Thanks, @TrippyLighting. I think I understand that. Although, I don't know how to join all the parts. Do you mean to create joint constraints between the various components? I knew I'd have to do that eventually, it's just frustrating that a selection doesn't group the objects to be acted on as a whole.

Re: Importing and rotating/translating

TrippyLighting — Fri, 05 Feb 2016 02:25:53 GMT

For most if not all of these components I'd use the Rigid Group from the Assemble menu. However, that's what I have aksed a question about. It seems there is a check box in the pop-up menu for the Rigid Group joint that sugests that when you select 2 or more subassemblies to be joined as a Rigid Group that this would also include the child components. However, it either simply does not work and there's a bug, or I am misunderstanding the purpose of the check box.

I'll create a little screencast once I have some feedback.