tho the thing that has me confused is...

trueSpace didn't used to do this.
I could export a mesh out of tS using the standard LUUV.tsx and bring it into poser and not see this error.
but, in the last coupla months..bam it's there. (it's why I'm trying to help with the thread and to understand whats going on)

the only things that have changed on the PC is drivers and installing poser pro base. so I'm a little puzzled why trueSpace 4.3 (10 year old stable unchanged code) and LUUV (not been changed for a coupla years now) would suddenly start doing this.