Solidworks Drawing Plane 3 3dsketch1

by gupta9665 » Fri Oct 22, 2021 12:16 pm

I am working in an assembly with a team of others. Sometimes we forget to plough off the planes and sketches before checking parts in. Is there an piece of cake style to select all of the sketches, or planes, or surfaces and hide them? I don't want to apply "hide all types" because in that location are planes and sketches that I will show to work. I tried selection filters just they didn't do anything.

Thu October 21, 2021 9:40 am

Then you want to hibernate some planes, sketches, etc, simply not all? In that case, as far equally I know your all-time option would be to ready display states, with the desired stuff either subconscious or shown, every bit needed. And so it's pretty simple to switch dorsum and along betwixt the unlike display states.

Unread post past **SPerman** » Thu Oct 21, 2021 ten:08 am

I think he is asking for a way to select sketches across multiple parts so they can be subconscious, without selecting each 1 individually.

Unread post past **Tom Thou** » Thu Oct 21, 2021 10:28 am

Glenn Schroeder wrote: ↑Thu October 21, 2021 9:forty am So y'all desire to hibernate some planes, sketches, etc, but non all? In that case, as far as I know your all-time selection would be to prepare brandish states, with the desired stuff either hidden or shown, equally needed. Then it's pretty unproblematic to switch back and forth between the different brandish states.

I've gotten to understand brandish states better lately. While I have some clean, as-intended for a drawing/assembly/3DPDF-export purpose, display states, I have begun to also create a Working display state where anything goes because I'm friggin' doing something here and I don't need all that other stuff in my way. While I currently piece of work in a 1-user setup, once we get some other, I'd put my own initials into the name of the Working display state, and crave other user to do the aforementioned: You lot practise what you practise and I'll do what I practise, but do information technology in your own display land and exit the clean one for common use by all.

Just an idea. I'one thousand open to learning unexpected consequences.

Unread post by **HDS** » Thu October 21, 2021 10:36 am

Kawuser

That works to hide them all. Still, I want to hide them all then then evidence the three or 4 planes and sketches I demand. Thank you for the macro simply it seems to do the same thing every bit the "hibernate all types" menu.

Glen

I merely tested display states just if I used it correctly information technology does non hide or show planes.

If there is a trick to select all the planes in the model then hide them that would piece of work for me. Filtering the tree for aeroplane at least lets me see all of them and then turn them off hide them one at a time. This is very tedious though.

Thu October 21, 2021 10:44 am

HDS wrote: ↑Thu Oct 21, 2021 10:36 am
Glen

I just tested display states but if I used it correctly it does not hide or testify planes .

If at that place is a trick to select all the planes in the model so hibernate them that would piece of work for me. Filtering the tree for plane at least lets me see all of them and so turn them off hide them one at a time. This is very ho-hum though.

Information technology works fine for me. Encounter the screenshots beneath. I created a new brandish state and set up the Plane to bear witness. When I switched back to the original display country the aeroplane doesn't testify. Maybe I wasn't clear though. You lot need to take manually hide or evidence the planes, sketches, etc in each display land. That won't happen automatically.

Thu Oct 21, 2021 ten:52 am

Here'southward what I thought:
Aren't all my Sketches named (Purpose) SketchXX? Employ Tree Filter to prove these.

Hither'south what I got:
I put Sketch into the Tree Filter, and it only showed the folders, components, features, and expanded sketches *of TOOLBOX Parts*. Every other component nowadays sure has Sketches named Sketch there also. Unfortunately this idea is a expressionless end.

EXCEPT!!
I tried information technology again. A majority of my piping components, by standard, contain a 3D Sketch named Weldment 3DSketch. Besides, my virtual weldment components ever take a 3D Sketch. So I entered "3DSketch" into the Tree Filter and indeed I got all of these displayed with less other in betwixt. Information technology doesn't ane-click and yous're done, nor even choice-filter window-select and hide, but it does condense the tree to prove all my 3D Sketches, regardless of if it was named "3DSketch1" or "Weldment 3DSketch" or "NPT Weldment 3DSketch" or "Nozzle 6in offset 3DSketch1".

So, tree filter helps reach this Only for 3D Sketches. Proficient luck.

Unread post by **Tom G** » Thu Oct 21, 2021 ten:55 am

Glenn Schroeder wrote: ↑Thu Oct 21, 2021 10:44 am You need to have manually hide or prove the planes, sketches, etc in each display state. That won't happen automatically.

I concur with Glenn. Display States are a method for preventing your issue by either returning to the past and doing previous work differently, or irresolute patterns of behavior across future time to achieve improve results. Neither of these options straight accomplish what you ask for: to click a button and get something washed nicely now.

Unread post by **JSculley** » Thu Oct 21, 2021 10:55 am

Glenn Schroeder wrote: ↑Thu Oct 21, 2021 10:44 am It works fine for me. See the screenshots beneath. I created a new display state and set the Plane to show. When I switched back to the original display land the plane doesn't prove. Perhaps I wasn't articulate though. You need to have manually hide or show the planes, sketches, etc in each display state. That won't happen automatically.

image.png

image.png

I think the issue @HDS is having is in the assembly. You tin can't command the visibility of planes in a part using display states in an assembly.

Thu October 21, 2021 10:59 am

Glenn Schroeder wrote: ↑Thu October 21, 2021 10:44 am That won't happen automatically.

Yeah information technology won't be automatic, because y'all don't hide all, the software can't figure out which to hibernate.

But if the names of the elements that demand to be subconscious kickoff with "hide" (hide-plane1 , hide-sketch1) I think a macro tin be written, like hide if the element name contains the word "hibernate". If you practise this often, yous should use the give-and-take "hibernate" for the assemblies you lot will create from at present on.

Add: can y'all collect the elements you want to hide in a binder and suppress them?

Unread post by **Tom K** » Thu Oct 21, 2021 11:fifteen am

JSculley wrote: ↑Thu Oct 21, 2021 10:55 am I call back the upshot @HDS is having is in the associates. You tin't command the visibility of planes in a role using display states in an assembly.

Nosotros digress, and obfuscate by not including context within each suggestion and answer. Isn't at that place a lovely FAQ about display states? IDK.

I am able to command the agile brandish state of a component (such as hide THIS sketch here), relieve that component, and when I return to the assembly that sketch is hidden while others are shown. It is a layered structure. Control the parts and yous volition have them testify nicely when in associates. Command the varied displays y'all want in the assembly to have them show nicely in drawings or exports. They can be useful in directly context, but are more than useful to reference in downstream applications.

OTOH, your assembly display states can control those entities only only with the same tedium as transmission fussing.

That'south why I recall that it's something you lot tin adopt into parts so that yous have planned ahead for its use in the assembly. This does not in any mode aid y'all now that you are already in the assembly unless you want to add actress work to become back and modify your components themselves.

To be more specific, y'all tin select and control the Referenced Display State of a component inside its Component Properties. This does not become back and create component display states for yous here, but it does allow you to leverage the decisions yous take already made in the by.
My component in assembly shows up as: FILENAME<#> (CONFIGURATION<DISPLAYSTATE>)
You tin cull what you've already made to utilise where you are. It doesn't reference what you haven't already differentiated.

Thu October 21, 2021 11:37 am

Tom Thousand wrote: ↑Thu October 21, 2021 11:fifteen am We digress, and obfuscate by not including context within each proposition and respond. Isn't there a lovely FAQ nearly display states? IDK.

I am able to command the active display state of a component (such as hide THIS sketch here), salve that component, and when I return to the assembly that sketch is hidden while others are shown. It is a layered structure. Control the parts and you volition accept them show nicely when in assembly. Control the varied displays you lot want in the assembly to accept them prove nicely in drawings or exports. They can exist useful in direct context, merely are more than useful to reference in downstream applications.

OTOH, your assembly display states can command those entities merely just with the same tedium equally manual fussing.

That'due south why I remember that it's something y'all can adopt into parts so that you lot have planned alee for its use in the associates. This does non in any way help you now that yous are already in the assembly unless you desire to add extra work to go back and change your components themselves.

To be more specific, you tin can select and control the Referenced Display State of a component inside its Component Properties. This does not go back and create component brandish states for you here, just it does allow you to leverage the decisions you accept already made in the past.
My component in assembly shows up equally: FILENAME<#> (CONFIGURATION<DISPLAYSTATE>)
You can choose what you've already made to use where y'all are. Information technology doesn't reference what you haven't already differentiated.

There was one, once upon a time.

Unread post past **HDS** » Thu Oct 21, 2021 12:10 pm

A simpler change to practice would be for u.s.a. to plow off all planes and sketches before checking in. That is something that display states could help with.

I was hoping for a simple way for me to exercise this for myself. Until someone shares a better idea I volition have to filter the tree and wait for the stuff that is shown. This is tedious simply easier than irresolute the mode anybody works.

I wish that surface was an option in "hide all types".

Unread post by **Lucas** » Thu Oct 21, 2021 vii:58 pm

HDS wrote: ↑Thu Oct 21, 2021 12:10 pm I was hoping for a simple fashion for me to exercise this for myself. Until someone shares a better thought I will have to filter the tree and look for the stuff that is shown. This is tedious merely easier than irresolute the way everyone works.

Are you using the Hide/Show Display Plane (F8 key)?
Still is manual, only pretty easy to spot what is on/off and plough it with ane click

Fri October 22, 2021 8:15 am

Lucas

Aye, that is how I am doing information technology. It isn't hard only takes a while to go through all the planes and sketches in a small-scale assembly.

Friday Oct 22, 2021 8:28 am

A macro would be perfect for this. I would dig through this site first (https://www.codestack.cyberspace/) or maybe @gupta9665 has something on hand. I'm pretty sure I saw him or Artem mail something like this on the one-time forum....

Unread post past **HDS** » Wed Oct 27, 2021 1:56 pm

Gupta9665 thank you for this macro! I had some problem getting it to work until I downloaded it again. This is what I needed and it will make me more than productive.

Wednesday Oct 27, 2021 5:54 pm

HDS wrote: ↑Wed Oct 27, 2021 1:56 pm Gupta9665 thank you for this macro! I had some problem getting it to work until I downloaded it again. This is what I needed and it will make me more productive.

Yep, @gupta9665 makes a lot of people's lives easier with SW. We're lucky to have him helping u.s.a..

Unread post by **KevinC** » Thu Oct 28, 2021 vii:54 am

Along the lines of Mr. Schroeder's suggestion on using display states.
If yous employ configurations in conjunction with display states, then the visibility of planes tin can be controlled.
You must create a configuration in each child file that you need to maintain planes.
Correct-click a display country proper noun and select properties. At that place, bank check link display states to configuration.
For the new configuration, hibernate (or show) the planes in question.
Repeat this for each child file.
I suggest using the same configuration name as these must exist selected in the assembly.

In the parent assembly, create a configuration (same proper noun as for the children) and right-click display state and set link DS to configs.
In the parent associates, select each affected child and modify its config to the config for the planes display desired.
One time this is done, aeroplane display in the parent assembly is a affair of changing configurations.

Solidworks Drawing Plane 3 3dsketch1

hibernate planes & sketch in assembly

hide planes & sketch in assembly

Re: hibernate planes & sketch in assembly

Re: hide planes & sketch in assembly

Re: hide planes & sketch in assembly

Re: hide planes & sketch in assembly

Re: hide planes & sketch in assembly

Re: hide planes & sketch in associates

Re: hide planes & sketch in assembly

Re: hide planes & sketch in associates

Re: hide planes & sketch in associates

Re: hide planes & sketch in assembly

Re: hide planes & sketch in assembly

Re: hibernate planes & sketch in assembly

Re: hide planes & sketch in assembly

Re: hide planes & sketch in assembly

Re: hide planes & sketch in assembly

Re: hibernate planes & sketch in assembly

Re: hide planes & sketch in assembly

Re: hide planes & sketch in assembly

0 Response to "Solidworks Drawing Plane 3 3dsketch1"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel