I ran into this problem a few times before, and luckily was able to close the program and fall back on backup project files as a work-around, but it's finally caught up to me now and I have no where to run...
Overall, it seems to me that the "Hand Valves" class is very flaky and unstable. I originally created nested valve classes within the Hand Valves class, and they have worked fine (save for a few times when they didn't work, and I reverted to overwriting the project files with a backup that I had made).
But as of right now, when I place a valve from a custom valve class, say the check valve, from below...
...at first graphically everything looks fine when prompted to place the valve in the drawing, but once I place it, it defaults to a gate valve (or generic valve body) as shown here:
Because the valves are divided up into sub-classes, this check valve should only be able to be substituted for another valve in the "Check Valves" class (and this worked fine for weeks), but once I placed the valve today, the generic valve body appeared and only allowed me to substitute it out for other 'out of the box' valves. But even if I selected any of them, they each still came through as a generic body valve as shown above...
I tried deleting the SubstitutionPalettes.xml file, but that did not resolve anything. Now I am desperate, as I have to get people started working in this program tomorrow - great timing for it to break of course...
Solved! Go to Solution.
Solved! by quentin.contreras. See the answer in context.
I am glad I was able to get a fix for you!
This same exact thing is happening to us. It started happening yesterday afternoon, and it also started happening with check valves. The same exact thing, looks good when we get it from the tool palette, but changes when placed. When we try and right click to substitute a different body, the only change in the symbol is that it doubles in size.
I wish that I had a fix or a work around, but we are at a loss as well. We've tried just about everything we can think of, short of starting the project over.
Autodesk, if you're listening, please help.
Glad to hear we're not the only ones out there. Another firm that we're working with is having the same problems as well. Last night it really tanked out on us and has brought our production to a halt. We are desperate to have it fixed soon, because none of the valves come in correctly, they all come in as gate valves.
As far as the larger valve you're getting, by default, Autodesk made their valve blocks scaled up by 4x, but set the scale factor in the symbol settings to 1/4...seems odd to me, but if you don't set them up the same way, it creates problems with the end connections and other features as well.
Update from my company:
I tried to move some of the valves out to the main hand valve class level to see if I just had my valves nested too deep, but it doesn't seem to make a difference. They still come in as "generic" body valves.
Thanks for the info on scaling up and scaling down...seems redundent to us, but appears to work. Odd thing is that some valves we made had this problem while some didn't, and all were created identically.
I received the "fix" from an Autodesk customer support rep (Quentin Contreras):
"First thing to look at is the Property Name "Normally" setting under Project Setup --> P&ID DWG Settings --> P&ID Class Definitions --> Engineering Items --> Inline Assets --> Hand Valves. The default is "NO". I have notice that this will revert the valves to gate valves if this is changed to blank. Check this first and see if this is the problem.
Also, when you edited the hand valves, I am curious if you deleted any of the fields under properties. For example, ValveCode, Failure, Number...? If so, I have seen to where valves would revert back to a gate valves as well. Check this as well if anything has been removed."
This first one solved my problem, but I can't speak to the second part. This seemed arbitrary at first, but makes sense if you don't have other graphical alternatives in place to account for the "blank" "Normally" property. And since this is a hard-coded system property, I can see how the problem would manifest itself.
Hope this helps everyone! Thanks Autodesk & Quentin!
I am glad I was able to get a fix for you!
Access a broad range of knowledge to help get the most out of your products and services.
Start with some of our most frequented solutions to get help installing your software.
The AutoCAD P&ID forum has moved into it's very own category page, and can no longer be found within the Additional Product Forums.
Upgrading to a 2015 product? Make sure to check these out 1st!