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.
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.
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.
We now get our defined block being our green fence post at every 20m along our chosen object.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. AutoCAD then asks if we want to Align block with object? We’ll stick with the default for now of no….We’ll use this in our next example….We can now as we did before enter our segment length of 20m. This time invoking the Measure command, we again select our object (the Polyline) but this time instead of our 20m segment length we now type block and then enter our block name, in our example being post. Here we’ve created a block called post to represent each fence post position. When defining our block for our post we need to remember where the block insertion point will be, so in our example the fence post centre will be our block insertion point. Now we want to add our fence posts at each 20m segment we could if we wanted simply just copy a circle to represent the post to each node point using a node snap, which is fine but along a really long fence? This is where instead of adding a node point at each 20m segment we can insert a defined block for each fence post position.