I did use the "render" option. I assumed that the problem was that the flag is missing, since its passing the file name for the POV file, without the +i in front of it, I might be wrong. This was just a quick test. All I did was export one of the standard Skeletons, from Poser and obj, making no changes, other than pulling the arms down to the sides, instead of pointing straight out, then imported from there. I haven't used Poseray at all, so, I figured I would use something familiar. lol
I think I have, however, figured out two things:
1. I was trying to run this against an open, single instance, copy of POVRay (do to running the scene manually, when I got an error the first time). I need to either turn single instance off, or leave it closed, for the thing to work right.
However, I do think I found why its generating an actual error when trying to render, and those two lines where not commented out. The last lines in the scene are "lights". The missing one in the scene seems to be an ambient light. POVRay doesn't define ambient as a light source, but it appears that Wings3D is exporting an object reference to such a light, but ***is not*** exporting a definition block for the ambient source (since it can't), the result is an error, caused by the fact that the resulting light source was never defined, so the name its been given doesn't reference any object that actually exists in the scene file. Woops!
This is probably easy enough to confirm, even without the huge file I was playing with. If it finds an ambient light, it either needs to ignore it, or use the correct definition for it, which isn't a light source, and thus, shouldn't have an "object" block for it anyway, never mind having one, and not having the #define for it. That definitely *is* a bug.
Hmm. Though.. Other possibility, I was looking at it from the Z direction, and had "tab smoothing" on, so... Maybe Wings3D is generating that ghost light, as a result of trying to show the scene from where you are viewing, when there are no lights, and no camera defined?
I think I have, however, figured out two things:
1. I was trying to run this against an open, single instance, copy of POVRay (do to running the scene manually, when I got an error the first time). I need to either turn single instance off, or leave it closed, for the thing to work right.
However, I do think I found why its generating an actual error when trying to render, and those two lines where not commented out. The last lines in the scene are "lights". The missing one in the scene seems to be an ambient light. POVRay doesn't define ambient as a light source, but it appears that Wings3D is exporting an object reference to such a light, but ***is not*** exporting a definition block for the ambient source (since it can't), the result is an error, caused by the fact that the resulting light source was never defined, so the name its been given doesn't reference any object that actually exists in the scene file. Woops!
This is probably easy enough to confirm, even without the huge file I was playing with. If it finds an ambient light, it either needs to ignore it, or use the correct definition for it, which isn't a light source, and thus, shouldn't have an "object" block for it anyway, never mind having one, and not having the #define for it. That definitely *is* a bug.
Hmm. Though.. Other possibility, I was looking at it from the Z direction, and had "tab smoothing" on, so... Maybe Wings3D is generating that ghost light, as a result of trying to show the scene from where you are viewing, when there are no lights, and no camera defined?