My company uses a system called ETO. It has a SW interface that works pretty well.

Looks like the location sketch now stays inside the hole wizard feature in the tree, but doesn't seem to fix that on holes already inserted in the part.

AlexLachance wrote: ↑Fri Oct 11, 2024 7:47 am Why wouldn't it be? Because that QA apparently isn't available to everyone... Not sure why they made it this way. Maybe you're right. Whatever, let them sue me, here it is: https://ufile.io/4c3o3umw For what it's worth I asked our IT guy to check on this...

So you buy the software but you can't use some of the features without being on subscription. Greedy Bastards

When this happens to me the most common cause is a file path containing to many characters. There is limit to the number of characters in the file path with Pack & Go and if that is exceeded that item won't be included in the copied file. We found that we needed to keep a simplified folder struc...

Just for giggles here is my 46" screen with 19" monitors on each side.

I believe you can place the first hole opposite the notch where desired (using a 3D sketch) and then do a circular pattern for the other two.

I do it this way as shown in the pictures. Change the state of the dimension with the menu to the right of the dimension text highlighted in blue. Top pictures is set to be unique to the configuration. Bottom is set to be the same in all configurations.
Is this what you are looking for?

Just a guess but the "In Context" relations you show might be the cause of your problem.

Josh, for things like cylinders or linear slides that need to show for example extended and retracted states we use configurations and move/copy bodies to show the working positions.

Just as an alternative, here at my shop we would save what you are calling vendor supplied sub-assemblies as a part file and and replace the assembly with the part file. This gives just one line item in the BOM and no juggling properties of an assembly. Also simplifies file structure.

This behavior was modified in, I think, SP 3 so that the axis don't show immediately. You have to hover over the object for a couple seconds before they show.

I have been having SW 2022 freeze up requiring me to use task manager to kill it and restart. Seems to happen when I am picking faces on multiple parts.

We upgrade every three years.

I have the same issue and have tried all these suggestions but have not yet found a solution.

I am looking for a macro that would run through all the parts in an assembly and activate the freeze bar on all the parts in the assembly. Does anyone have one for this that they could share?

The temporary axis popping up is better but I still would like to be able to turn it off completely, or just delete that "feature".

Our group is making the jump this week. We skipped SW2021 and are moving up from SW 2020 which for us hasn't been to bad once we got to SP5.

Can you right click on the part and use the isolate command so it is the only part shown now?

I think this is most probably the issue The virtual component might not get saved properly through the network and somehow get corrupted Did you directly work on the file on the network? Not sure the correct answer for this but I would say yes since the project is stored in a job folder on the serv...

The user here that complained about this has had it happen four times in the last few weeks. Less infrequently with a couple others. Always after a shutdown or restart. He is using a certified graphics driver for his Nvidia quadro 4000 video card. I don't have any understanding of where the data for...

We are having issues with SW2020 losing virtual components after shutting down or restarting our computers. We don't use any PDM program, we work over our local network and our project files are stored on our server. Has anyone else seen this happen or do you know what might be causing this?

My most impressive trick was once going an entire day without a crash.
Wish I could remember how I did it.