As for the GC issue, Poser should NOT have made GC on the default. For people who just moved from a non-GC to a GC workflow with absolutely no warning, they got hit in the face with errors that they had no idea how to fix because almost ZERO content is adjusted to take GC into account. Very few people have been listening to Bagginsbill talk about GC for the past five years. They were totally unprepared for the change. Even forum regulars still ask questions about GC, for goodness' sake. And vendors apparently got inundated with support requests for old content over the issue -- even if their new stuff was GC compliant.

If you disagree, that's reasonable. But one thing that should not be default is Poser setting normal maps to GC 2.2 when GC is on. And, at least on my version, it does. If they should always be GC 1.0, then it doesn't make sense that they default to 2.2, does it? Since we don't have Les's actual words on this, it might be this that he was referring to. Let's cut the guy a break and not get on his case over hearsay, shall we?

---

PoserPro 2014, PS CS5.5 Ext, Nikon D300. Win 8, i7-4770 @ 3.4 GHz, AMD Radeon 8570, 12 GB RAM.