Has anyone every set up a scene, and Poser decides not to render everything in the scene?

This has happened more than once. And mostly with Poser 8.

I just spent a few hours last night setting up a scene with lots of props. I test render it, and Poser only renders about five props, and skips the rest.

I opened the same scene in Poser 7, and it renders.

It seems that with each new build of Poser, I'm having to compromise on my scenes. I once rendered a very complex scene in Poser 6 (see gallery, The Invaders), but usually have to pare down complex scenes recently.

It's a shame, since Poser 8 has such nice new lighting effects and renders better, when it chooses to render the entire scene.

I don't do nekkid Vickies with just a backdrop. I like to add detail, but Poser 8 seems to not want to render them.

Is it just me, or has anyone else run into this problem?

Windows XP, 3GB ram, in case you're curious.

-- Jeff

I don`t have poser 8 but that sounds like some kind of memory problem.

I did run into this problem when I side-graded from Poser 7 to Pro on a new computer. I tried to just transfer the Runtimes over and it seemed to work, all the figures were visible, but when I rendered it, all the Daz figures disappeared. Poser figures worked fine, as did other 3rd party figures, but all my Daz figures, clothes, etc just didn't render. had something to do with moving the runtimes via an external drive and Win 7 mapped it as a fixed hard drive.

Since Poser 7 renders the scene, I'm thinking it's either a memory problem, or just the way Poser 8 handles files (not very well, somtimes).

I hate that new features compromise scene integrity. Can't we have both?

I haven't had issues with Poser 8 like many others; no problems with the library or antialiasing, etc. In fact, I've been loving working with Poser 8.

But it seems to not want to work with larger scenes. It chokes, and sometimes instead of just crashing, it just is blind and renders a few things.

It's not just a DAZ product vs Poser people. Out of 15 or twenty props, all part of Posien's Overgrowth, it just renders 3 or 4 of them, and ignores everything else.

I ran Poser File organizer over the pz3 to check for path inconsistancies, but didn't find anything, and P7 renders it all.

I'll just try and rebuild this scene, but I'm starting to get frustrated with Poser 8. I did mention the scene size issue in the Poser 8 open letter feedback thing. I'm hoping SR 3 comes soon and addresses these issues. SR3, historically, fixes most Poser problems.

-- Jeff

Jeff - this is just a stab in the dark but do you have the 'Seperate Process' box checked in the General Preferences? The only time I got memory problems on rendering was when it wasn't.

Other than this I can only think that Poser might be passing on scene elements that it's File Search can't find for some reason, but you'd usually get a popup for that kind of thing.

Is this happening with old scenes made in  previous versions opened in P8?

This just happened to me. I set up a scene with three clothed figures, and when I rendered, the girl's jacket didn't show up. It was visible in preview. I changed the lighting a bit and when I rendered again, the jacket showed up fine. I was very puzzled by it and surprised to see your post on the very same issue.
I am using Poser 8 and rendering in a separate process.
 

Do the problem items show in the preview?  If not, then it may be that P8 is not finding the geometry for those props.  I don't think P8 handles ambiguous locations all that well when working with content in multiple runtimes, you might try installing the props into P8's main runtime, deleting them from the scene and re-adding them from the main runtime location.

edit: now, Nanette's problem is one I hadn't seen, that's pretty mysterious.

I have scenes with up to 6 figures that I rendered in Poser 5 and they will not render in Poser 7. It seems that each version needs more memory for the same scene. I have had to set up some scripts to split the scene up and render in two or three passes and then composite. It really messes up any shadows though. :( 

Seperate process is checked. Number of threads = 2.

I tried changing cameras and angle, too (thought it might be a hither/yon type thing), but this isn't the first scene. And it's newly created scenes.

External runtimes on an external drive. But the preview loads up fine. It's just when you render it, Poser 8 sometimes will not render everything. This happened sporatically in P7, but not as often.

Yeah, and sometimes it'll even be clothes conformed, too.

It doesn't happen all of the time. It's unpredictable on which scene this'll happen with. More of a gremlin that a always occuring problem.

And, yes, I had a relatively weak computer with P6 for that Invaders scene, compared to today's standards.

Well, it's good to know that it does sometimes happen to others ;)

-- Jeff

Bit of a puzzle by the sounds of it. Hopefully it's not too frequent an issue.
I never had just odd elements in a scene not render before.
Every now and then Poser will fail to calculate IDL or render black on me, but it's so rare and always solved by restarting Poser.

Even though it's not a frequent occurrence, it's happened to enough people to warrant reporting to Smith Micro, don't you think? Mind you, it hasn't happened to me. Yet. If it does, I will. Report it, I mean.

Well, I deleted that scene, and rebuilt it.

Poser 8 still only rendered out about 5 out of 25 objects. I tried switching render settings -- the same. Tried to "trick" it by using IDL -- failed.

Opened it up in Poser 7, rendered, everything came through.

I just finished contacting SM support about it, since it was reproducable.

Just when I was really becoming addicted to Poser again, this crap happens... Anyway, since reverting back to XP, I hadn't yet re-installed Cararra 6, so I did tonight. I'm off of work tomorrow, so I'll see if I can get used to it; I really dislike the GUI and shading system set-up, but it handles larger scenes better than Poser. Sure, I can use Poser 7, but I'm upset and frustrated and need to try new things.

-- Jeff

It could be your computer.  For example people have had problems with the Alex 7000 or the Hal 9000.

"I'm sorry Dave, I can't render that scene as you've created it.  There seems to be a problem with the antenna.  Perhaps you should go outside to check."

Perhaps someone can figure out the origin of the Alex 7000.

 "open the Pod Bay doors HAL...."    

Move all of the letters forward by one.....

H.A.L. = I.B.M.

I also get the selective rendering problem, mainly with the area render function. When it decides not to work right, it renders black. Sometimes a full size render will render half way and then leave the rest of the screen gray.

I've found that lowering the bucket size tends to help with this problem. On a big enough render I'll even set the bucket size 8 or 12.

I was having problems with failed area renders which just rendered the Poser gray background, prior to SR 2.1.  Since the SR, I've had periodic failed area renders in which just the scene preview is rendered.  Never seen a case where some items were rendered and not others, but I haven't created any really complex scenes so far.

I tried re-installing SR 2.1, but to no avail. It's still happening.

Here are the rendered scenes. This is the re-creation of my original, and is basically whittled down some. But the same results.

Here is the Poser 7 render -- everything renders accordingly:

http://www.flickr.com/photos/20381395@N03/4320290636/sizes/o/

The second one is the Poser 8 render.

http://www.flickr.com/photos/20381395@N03/4319557037/sizes/o/

-- Jeff

Heard back from Tech Support. They want the scene, so I shall send it to them.

-- Jeff

I really dont thing the prop makers will mind if SM test out a Poser Failure by you sending them they're files...send it, I dont want to come across this problem.

well, it's not just this one scene. It's happened before with totally different props/setup.

The asked for just one prop, but it wasn't reproducable that way.

-- Jeff

I've not had the selective rendering problem, but I do have scenes that P8 just won't render but P6 will.
In the most recent case I got an error message, but I have several where the render window appears, t starts to list the process then disappears and leaves a black screen in the render window.
I'm starting to think P8 is growing its own bugs as I use it. The latest weird one, if I launch a pz3 by name from My Recent Doc's in the Start menu it loads with a Language Bar at the top of the screen, works for a few minutes then crashes to desktop.

Not getting much help from Tech Support. They didn't want the entire scene, just 1 prop, even though I mentioned it was not specific, and this has happened with totally different setups previously. But they want to try and replicate it -- so why not just ask for the scene that I have that it does it with?  I tried to upload it to their website, but the website is slow and times out every single time.

My latest answer is that it's my computer. Oh, totally re-install P8 since it might be corrupted preference files, but most likely corrupt preference files wouldnt cause this type of problem (This is the actual answer from Tech Support),  but try it anyway.

Pissing in the wind here.

Guess I'll just do nekkid people with swords.

-- Jeff

After a reinstall, the problem presists.

It seems to be how Firefly translates the camera settings, since I was able to get a few more items to render after changing the focal length. Why it doesn't happen with every scene is still a mystery.

Historically, Poser isn't  stable until SR3. So hopefully something will stabilize when SM releases their SR3. But Tech Support doesn't seem to want to really look at the problem, at least my problem. So if you've had this happen, let them know.

-- Jeff

You could try tinkering with the hither/yon settings on the camera (?).

try collecting the scene inventory to the same folder as the poser document. When I had that happen in Poser Pro, that is what I did and it worked.

Quote - try collecting the scene inventory to the same folder as the poser document. When I had that happen in Poser Pro, that is what I did and it worked.

I had to do that for Tech Support. The scene rendered the same.

Getting a second look at it.

-- Jeff

Didn't know that about HAL and IBM.  But what about the Alex 7000?

Is BMFY anything important?

Quote - Didn't know that about HAL and IBM.  But what about the Alex 7000?

Is BMFY anything important?

http://www.google.com.au/search?hl=en&source=hp&q=BMFY&btnG=Google+Search&meta=&aq=f&oq=

I looked here,  so I don't think so.

Quote - In the most recent case I got an error message, but I have several where the render window appears, t starts to list the process then disappears and leaves a black screen in the render window.

Have that happend to me many times where it renders black. After unchecking "Seperate Processes" it renders fine.

Quote - > Quote - In the most recent case I got an error message, but I have several where the render window appears, t starts to list the process then disappears and leaves a black screen in the render window.

Have that happend to me many times where it renders black. After unchecking "Seperate Processes" it renders fine.

Thanks Zaycrow, I'll give that a try