jcaffee Posted January 14, 2016 Share Posted January 14, 2016 Really? This is not only annoying, but totally worthless as a tool to resolve issues. How about a temp folder in the User Lib with links to the problem symbols. In my case, I'm looking at manually searching through thousands of symbols to get rid of this nag pop-up. jon Link to comment Share on other sites More sharing options...
Joe_Carrick Posted January 14, 2016 Share Posted January 14, 2016 Jon, Have you tried displaying a 3D Framing Overview to see which items are creating the problem? It could be that simple. Link to comment Share on other sites More sharing options...
jcaffee Posted January 14, 2016 Author Share Posted January 14, 2016 For the entire 9000+ symbols in my User Library "Furniture" subfolder? Fat chance. I'll do a manual export/install for the entire User Lib from X7, see if that works. jon Link to comment Share on other sites More sharing options...
Joe_Carrick Posted January 14, 2016 Share Posted January 14, 2016 Sorry Jon, I misunderstood the problem. You're saying that you get this message when you open the Library? I thought such a message was only on a per plan basis. You should contact CA SSA and report this problem directly. I haven't seen it on any of my systems but it's probably due to a Texture/Material Folder location. It could be fairly easy to resolve just by correcting the path. Link to comment Share on other sites More sharing options...
DavidJPotter Posted January 14, 2016 Share Posted January 14, 2016 I have observed that certain User Libraries, especially those brought forward from earlier versions like V9, V10, X1 etc often loose their association with their texture files. Repairing such library files just takes too long and I have ended up just deleting them form the Library Browser (a material library that contains no texture files is completely useless and too time consuming to reassociate texture files, one at a time). It is a weak point in terms of moving forward, version to version. DJP Link to comment Share on other sites More sharing options...
jcaffee Posted January 14, 2016 Author Share Posted January 14, 2016 Sorry Jon, ...It could be fairly easy to resolve just by correcting the path. Agreed, but the issue is finding the offending symbol(s). Needle-in-a-haystack situation. The warning message is utterly valueless towards a timely resolution. jon Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now