I don’t personally use very many model space attributed blocks these days. These are no where near 100% polished, I just sat down with an old idea and brought it back to life to get the idea out there. You can click here to download the HOBConvert & HOBReset command code. You can click the image to get a clearer visual of what’s going on. If anyone is having an issue after deciding to use this, let me know and I’ll see if I can help. So, there shouldn’t be any risk of data loss with this method. Well those are the bad things, but the pro’s are reading the name of that generic fume hood right inside Navisworks and that the values you populate are never edited or ever truly gone just invisible.
In (native) attribute mode, you can edit the values of the attributes as you normally would.
#AAUTOCAD ATEXT DISPLAY NOT UPDATE#
So, sub-point 1 may not matter if that was your goal you can’t entirely update instantiated attributes anyway… Note that attributes are always instantiated and the only editing you could possibly do would be on non-attribute geometry.
This can be a problem if you have expected needs to block edit them later.It will disassociate your inserted blocks with their original block definitions.However, I do have a work around that I’ll share in this post and have used quite successfully in the past, but there are some things to consider before using my method: To be clear though, you cannot natively display the values of an attribute in Navisworks!! It is a 3D model viewer and sadly does not play as well as expected with various 2D objects and data. It made me recall a trick that I conjured on a past project and thought it would make an excellent post. I was reading a post about the limitations of Attributed text values within Navisworks today.
0 kommentar(er)
