I’ll do that, but that still won’t cure the problem of it showing up. If I do find one or more <specval>s like that, especially in the Arbortext distributed files I’ll pass that information along so PTC can find and FIX the problem.
I went through the FOSIs I have on my system and those in the distributed Epic files.
There is one <specval> in the distributed Epic files and nearly 900 in the various iterations of FOSI’s on my system. I searched for ‘attval=”2” | attval=”3”’. The results is there are no <specval>s with a value of 2, they are all 3. So the error of an <att> with a <specval> of 2 is really weird.