Well I guess I get to say I told you so. I tried to alert people to this problem but only got blasted for it. This is not an isolated problem or an abberation. It doesn't matter what your computer is or isn't. Its a legitimate bug. Instead of alerting others to the problem...openly and honestly discussing the problems...trying to find solutions or workarounds...there is only defensive denial. Eon knew of these issues before they released Vue 4. They know of them now, but they continue to ship it anyway with the attitude they will issue patches whenever. If criticism is banned here then this forum loses most of its constructive value. It becomes nothing more then an ongoing infomercial. We as consumers can only voice our displeasure at this type of thing and hopefully if the company is as the moderators here keep saying they are, responsive and honest they will not do this sort of thing again. Ok that being said, I'm concerned about the posts that say Vue 4 has difficulty in importing even some simple obj's and their maps, not just the Poser scenes. I have found in Vue 3.1 that by simply leaving out the bump map it resolved most of the importation problems. I also found that the renderings were still great. Also, I noticed at least Vue 3.1 had problems in dealing with a Poser obj if more then one map was assigned. If what I'm hearing is correct it means something has radically changed between Vue 3.1 and Vue 4 making the newer one less Poser compatible not more. This is valuable and important information. But if we cannot openly share this stuff and only get a flood of defensive denials how can we as users find solutions and workarounds?