Don't forget there is also a 3DSMax 4 import as well as one for Cinema 4D XL 7, both requiring P4 w/Pro Pack. :)

Blue who? Godzilla man! This ain't the Summer of Love. That band is so old, they've probably been taken by Extra Terrestrial Intelligence. Look, I'll just give one my True Confessions and say, "Don't Fear the Reaper." You're not that old. ;) (Sorry...)

Looking good! :) I don't know. When I look at it, I see someone into new-agey stuff doing some sort of yoga-kwon-transcendental type of thing. ;)

Hi wolf359! I have a simple question: Is there any way to import Poser scenes and retain the bone structure or would it have to be recreated from scratch in C4D (XL 7)? Thanks, BeatYourSoul

Alas, I can't use the new drivers because the NVidia Stereo3D drivers only work with the version coupled with them: 3.0.87.

Ahhh!!!!! Okay. I checked CL's FAQ's and it seems there is a reason and solution to this problem. If you have more than 2GB of memory (not me) OR set the initial virtual memory size above 2GB, it does this. I had set it to 4GB (to match the max size). Upon setting it to 2GB, I can now see my figures. BeatYourSoul

I can resize the document window, but the "displayed region" (in grey) remains the same size. Everything within the display is invisible. The figure is there, fully "in view", but unseeable. I only see the selected outlines. Tried resizing, turning it off and back on, tried resetting to factory states (where it is now), tried everything (!!). Plus, something somewhere else must have been changed, since it complains incorrectly on render attempts or just dies on start of render with 99% cpu usage. If this is a changed Registry setting, I have no idea where CL keeps them as a search on Poser, Curious Labs, etc, revealed nothing of interest. BeatYourSoul

:) BeatYourSoul

ScottA, that is totally possible. Could be overlapping polygons on the mesh. That could cause problems all over the place. If one set is facing one way and another the other way, but the texture is only being applied to one, there would be no "holes", but irregularities in texturing. As I said, careful, thorough inspection of the model sounds like a very good course of action. BeatYourSoul

UV coordinates can not "point in the wrong direction" (easily, anyway). Each UV point is directly correlated to a model vertex point. So, a point of a facet of a model with UV coordinates has both X,Y,Z and U,V coordinates. If the model points and UV points are in different directions with respect to each other (one clockwise, the other counterclockwise), than, to put it nicely, you're screwed. I have no idea how you could even get this to occur without physically editing the file (or using some strange settings for export). There is no easy way to fix this without first deleting the UV coordinates and recreating them from scratch, as far as I am aware. Normals are values that denote a perpendicular direction to a surface, like a facet polygon, or vertex by way of its parent facets and tell 3D apps which side of the facet is front facing. Most of the time, they are just calculated by the orientation of the facet (clockwise or not), but they can also be specifically stored (as in .obj files - vertex/vnormal/vtexture for each point of the facet). And, normals work on both the model vertices and UV coordinates by default. If you invert the normal of a facet, you invert the side of the facet onto which the texture is placed (and thereby seen). You are correct that facets with inverted normals (or not ordered properly) in Poser are displayed as holes in the model. I can't really suggest much for this except maybe re-exporting it with different settings after a thorough inspection of the model or loading it into UVMapper, saving the model without any normals or UV coordinates, reloading it and creating new UV coordinates. BeatYourSoul

No problem, noggin. Anyway, you did a much better job of describing the process to which I was only alluding. :0) Also, very good point Xurge. Lots of repetition in that model. Why have four separate, identical wall textures when you can just use one for them all? BeatYourSoul

Update: Well, when Apple released Jaguar, they decided to change the ftp daemon to some offbeat version (lukemftpd) which works, but would allow anyone ftp-ing into the server access to the entire system (not a good thing). So, so much for simple and quick; it was working very well except for that one problem, which from accounts, is unresolvable. Currently working on moving to another ftp daemon like proftpd. Will post as soon as everything is working. BeatYourSoul (wish me luck) :)

Don't need to do that! Break the model into groups (e.g. in C4D break it into separate objects and group them, export the entire group as a .obj), but you can keep them in one object file (.obj does support multiple groups in a file). You can then map each group into its own UV space in, e.g. UVMapper, and save each group's UV space out as a separate template (note that many models do this, such as Daz3Ds Mike and Vicky). Be sure to save out the modified model with UV coordinates to reflect the changes in UV coordinates. As you can tell this can be a complicated process, but beats having multiple .obj's to represent a single model. If you need more indepth info about doing this in UVMapper, don't hesistate to ask. BeatYourSoul

I was thinking the same thing, since that's what I'm using as well. Hey, whatever get's the job done. BeatYourSoul

Well, I tried. ;0) Someone's gotta play devil's advocate. Mosca: Oh, glorious god! How we love eBay, er, I mean you (nevermind). BeatYourSoul