NanetteTredoux opened this issue on Dec 04, 2009 · 6 posts
NanetteTredoux posted Fri, 04 December 2009 at 2:16 AM
This happens with Poser Pro and Poser 8.
Poser 11 Pro, Windows 10
Auxiliary Apps: Blender 2.79, Vue Complete 2016, Genetica 4 Pro, Gliftex 11 Pro, CorelDraw Suite X6, Comic Life 2, Project Dogwaffle Howler 8, Stitch Witch
hborre posted Fri, 04 December 2009 at 9:30 AM
This topic has been covered before in other posts. It usually comes down to the video card. Make sure your drivers are current for your particular brand and try changing from OpenGl to skree under General Preferences
NanetteTredoux posted Fri, 04 December 2009 at 9:51 AM
Thank you for replying Hborre.
I had just updated the driver and switched to SreeD rather than OpenGL, and discovered the problem shortly after that.
In desperation I saved out the obj file and ran it through PhilC's OBJ2CR2, so that I now have a usable version of this shirt.
Poser 11 Pro, Windows 10
Auxiliary Apps: Blender 2.79, Vue Complete 2016, Genetica 4 Pro, Gliftex 11 Pro, CorelDraw Suite X6, Comic Life 2, Project Dogwaffle Howler 8, Stitch Witch
TZORG posted Fri, 04 December 2009 at 3:43 PM
Did the shirt render like that, or just preview?
It's not the tool used, it's the tool using it
NanetteTredoux posted Fri, 04 December 2009 at 10:36 PM
Good question, Tzorg, I had not thought of rendering it.
Firstly, I have the problem on both my computers, so I don't think it is the graphics driver. As far as I can make out, only this shirt is affected. I am a bit miffed because I paid for it, and it is a Smith Micro product.
With indirect lighting, it renders in its exploded form, looking like the preview.
With normal Poser lighting, all I get is a black screen, which seems to indicate that the exploded mesh is blocking all the light.
Poser 11 Pro, Windows 10
Auxiliary Apps: Blender 2.79, Vue Complete 2016, Genetica 4 Pro, Gliftex 11 Pro, CorelDraw Suite X6, Comic Life 2, Project Dogwaffle Howler 8, Stitch Witch
TZORG posted Fri, 04 December 2009 at 11:52 PM
I'd at least report that problem then...
It's not the tool used, it's the tool using it