Yes, and now that 'Groups' can be managed and accessed from the Part Navigator they are much more useful in and of themselves, irrespective of whether it's just to help control what's visible and what's not. RE: usage of NX layers jerry1423 (Mechanical) 29 Jun 12 15:35 If my model starts becoming complicated, most often happens when creating freeform models, such that i have many surfaces built and trimmed from many curves each, it's kind of nice to be able to place the construction objects on individual layers such that i can make a specific set visible / isolate an area. Then when that feature is completed and i start the next i can "permanently hide" by moving the surfaces/curves/datums to a invisible layer and allow the next feature use the Hide/show option. If the decision stands between using "Hide/show" or "Hide/show and layers", i would say then use 2 layers, 1 Work and 2 invisibleīecause "placing" an object on a different layer will keep it invisible ( If that is the purpose) and then the Hide/ Show can be used as a working tool to quickly hide/show things whilst working.įor example, i am designing something that needs a few surfaces, curves and a few datums to complete, whilst working it's nice to hide the datums I don't need for the moment and be able to as quickly show them again. RE: usage of NX layers Toost (Mechanical) 29 Jun 12 13:07
To an Engineer, the glass is twice as big as it needs to be.
#UG NX FREE#
And if anyone else out there, who's spending their time using NX in real-world production environments and you have your own opinions and advice, please feel free to give us your 2-cents worth as well. I would look at the other more modern 'tools' first.Īnyway, I hope this helps and doesn't confuse you. However, that being said, before I automatically took a lot of time worrying about Layer Standards, naming schemes, allocations, etc. Now before anyone jumps down my throat, layers are still fully supported and will continue to be into the foreseeable future and there are still a few things which they may allow you to do which can and does have value. that it's very possible to manage the visibility and availability of objects without having to depend on something which in my honest (and personal) opinion is as outdated as 'layers'. However, today there many more tools, such as Hide/Show, Embedded Sketches in Child Features, Components and Reference Sets, Assembly Arrangements, etc. And since the resulting deliverable was almost always a Drawing, layers were absolutely necessary to manage the types and amount of data which made-up Drawings in those days.
I've been using UG/NX for nearly 35 years and at one time layers were almost the only tool we had to 'segregate' what back then was individual pieces of data, 'models' were made of lines and arcs and an occasional surface, but there were no solids, assemblies were basically parts merged together into a single files, Drawings were a collection of modeling views, etc. If you've gotten this far without using layers, and you've got experience using a system which was developed after layers lost their 'luster' to say nothing of their unique qualities, I wouldn't lose too much sleep worring that perhaps I should become more familiar with them.
0 kommentar(er)
