You can create countersinks on both sides of a Hole feature by activating "Start Chamfer" and "End Chamfer" options.
This does not work for counterbores, though. Apparently NX lacks the "End Counterbore" option for its Hole features.
On that "fully loaded" Alert I agree with cowski - it...
Those might be object tags (of the dataset attributes in question), not error numbers...
Could there be some mandatory attributes in TC that are now enforced, and are missing in your model? Present in an old revision, but not in the new one?
You mean the Start/End fields resetting to "Value" from other options like "Symmetric" or "Until Next"?
Don't think there's a trick here, other than writing and programming your own feature dialog for that.
There's a Lightweight body that's generated automatically since some NX version later than 7.5 the script was developed in.
It's on the MODEL Refset, and I guess it interferes with the object selection part of the journal code.
What do you mean by "attach" and "solid body"?
If you mean import a STEP/Parasolid/whatever dumb solid model into a work part and then unite it with existing geometry, then yes.
You can record a Journal with the activity you need to perform and just go off that.
It depends on what you want with the template.
If it's meant for local use on that machine - go ahead and select "update the pax file" (so you don't need to edit it manually).
If it's for distribution to other machines/user roles, there's probably no point in updating the pax file of your...
Given that the pax file is a directory of templates available in the File-New dialog, not updating it will result in your new template not showing up on that dialog.
When your NXOpen programs grow out of the simple Journal files, Siemens wants you to have the Authoring license to be able to sign your dlls, so that other people can use them.
For .net applications, you need to add the NXOpen Signing Resource thingy (UGOPEN\NXSigningResource.res) to your...
The red dot tells you where the problem is, most likely some sort of distance tolerance issue. You can sometimes "fix" it by twiddling the tolerance value, but a lot of the time it's some sort of geometry problem that you might want to address before this thing is created IRL.
You can create a dummy assembly with some basic blocks to show us here, and also verify that this behaviour is reproducible with any model.
Otherwise we're reduced to making guesses.
Are there any other objects in the assembly, that are overlapping with the hidden assembly components, like...
You can record NX Journals while performing simple tasks to learn how NXOpen does stuff from these.
Recorded Journals tend to get excessively verbose when you record more than a couple simple actions (running the risk of drawing you into cargo-cult programming), but this should be bearable for...
Yeah, they added the whole symbolic thread stuff into the "modern" NXOpen, while simultaneously obsoleting the old C function wrappers back in 1926 or so. This function will now only work for the old pre-1926 holes.
You'll have to re-record/rewrite the Journal using the "modern" functions...
Having used keyboard and mouse for the majority of my waking life over the last 35 years, and never having any issues, I'm going to guess it largely depends on workplace and tool ergonomics.
Holding the mouse at weird angles, having the table edge cut into your forearms, or forearms hanging...
patternFeatureBuilder1.FeatureList should have it.
Depending on the designer's "creativity," the list may have more than one feature, even more than one hole package, so you'll need to look for the one you need in there.
