Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X
How can you control whether an annotation dimension disappears when cross-sectioning?
I have a model where the cross-section was created on a plane called SKETCH (offset of 0), and I added 3D annotations to the same plane. Half of them disappear when I cross-section and half of them stay. If I reverse the direction of the cross-section then the other half of the 3d Dims disappear. The annotation plane was also defined to be on the SKETCH plane.
How can I control this behavior so I control whether these dims are shown in the x-section view?
Solved! Go to Solution.
If you are working in Creo 4 or later set this config option:
show_clipped_annotations yes
Additional info on the topic.
https://www.ptc.com/en/support/article/cs66269
If you are working in Creo 4 or later set this config option:
show_clipped_annotations yes
Additional info on the topic.
https://www.ptc.com/en/support/article/cs66269
This did exactly what I had hoped! Thank you!
This begs the question, do you happen to have/recommend any other config options that can improve working with MBD? They seem to be a huge pain in comparison to drawing dims.
I don't have a list of options. You search for the word "combined" or "state" in the list of config options for the Creo release of interest and that should find most of them. They may be adding config options in releases newer than 4.0 which what I am still working in for now.
This site maintains a list of config options by date code.
Complete lists of Config.pro Options – CreoSite
I reviewed those and made some changes to test. Thanks again!
Some others you might want to look into:
excl_annotations_of_suppressed
excl_annotations_of_deleted
intf_out_pvs_recipe_file
The first 2 are for Creo 7, not sure what version you are on. The last one sets the location of your Creo View recipe file. The default recipe doesn't export MBD annoations. Be careful with this one though. There is a bug that I found that is getting fixed in 7.0.5: