And so we've NEVER actually let you save that kind of measurement. And completely wrong in any other instances of that component. In particular, from within the context of any given assembly component, a measurement from the block in the component to the sphere in the assembly will only be valid in the context of that one specific instance. That one's easy.īut from within the context of any given assembly component, we cannot ensure that the measurement value will be meaningful in more than that transient moment. We are happy to make these associative, because the resulting values are stable, because the assembly determines the location of each of its components uniquely. Measurements made in the context of the assembly - looking "down" into assembly components - make total sense. And there are obviously three instances of that component in this assembly. Each block is a solid within an instance of a "model_1" component. In the example below, the sphere is a solid within the assembly file. Measuring from the context of a component up into a parent assembly is not a good idea. This one is really all about design in context. You have likely already read the feedback there, but for the benefit of the larger crowd here: I see that our development team addressed both of your PRs within a day or two. We made a ton of changes from our original design, and looked very closely at some of the good things our competitors were doing here.
We had many rounds of very early usability testing - long before beta - with fresh eyes each time, to try and dial in the experience. In fact, I think we've done more usability testing on these changes than any project I've been a part of in my 15 years in NX product management. (Though frankly, I spend a lot more time over on the Siemens NX Design Forum these days.) (Phoenix, Arizona) RE: NX12.0.1.7 MP1 Measure command drastically changed.
#Ug nx command list software
Siemens Product Lifecycle Management Software Inc. NX Product Manager, Knowledge Reuse and NX Design There are a TON of new things lurking in here that I think you're going to love.Īnd yes, we have a great team working on performance, too.
#Ug nx command list series
Over the next few weeks I'll be putting up a series of videos on the SPLM Community Blog going through these use cases and a bunch of others. Like anything new, this will take a bit of getting used to.
In the middle of a distance measurement and decide you want it to be projected? No more re-selection or starting over. Want to save all those measured values and refer to them later? Send Results to the Console and you'll keep a running record during your session. Want to copy that value and use it non-associatively? Go ahead and copy it right out of the scene dialog. Want it to be an associative feature? Click the save button in the scene dialog.
(And if you'll watch the hint area, we actually guide you into this one.) Projected Measurement? Pick the things, then pick a vector or datum axis.
#Ug nx command list update
As the Product Manager who has spent the last couple of year working with the development team to update and consolidate our measurement commands (and as a 20+ year user of Unigraphics and NX who cares a lot about usability), I'm happy to help where I can.
0 kommentar(er)
