My PPro2010 has started behaving strangely, in a random and non-repeatable-on-demand kinda way.

Without any obvious reason, it will start refusing to render a new scene. That is, I can be adding figures, posing them, making changes to materials, adding props, etc, etc, and doing test renders. But then, when the strangeness strikes out of nowhere, it will render the exact same scene each time I try rendering, ignoring any changes I've made as if some previous scene had somehow become 'stuck' in memory.

The only way I get it to render anything different is to save the scene, exit Poser, restart, render. However, if I do this, it then gets 'stuck' on that new scene and no further changes will make any difference. Ultimately, restarting the computer is the only solution and I'm back to normal behaviour until the error kicks in again.

Anyone experience this and, even better, know how to fix it?

Further info...

• When it's rendering with IDL, it will start the IDL pass but this is just the 'stuck' scene being displayed bucket by bucket. The red IC dots don't appear on this pass as they should do. Then, it goes back and does the second pass and this is, once again, the 'stuck' scene displayed all over again.

• If I render without IDL on, it renders the whole scene black, but takes its time with each bucket as if calculating the materials and geometry that ought to be there.

• Changing to a different camera makes no difference... whichever camera I render from, the 'stuck' scene is the result.

• This happens for both normal rendering and background rendering.

• This is PPro2010 with SR1 installed running on Win7 64bit.

When this happens to me, I have found rendering using the top "Render" command, as opposed to the "Render in Background" will break it out of the cycle.

In which folder is PP2010 located?  Have you had Poser for a while, and is now starting to act strangely?  Or has the problem been sporatic since the beginning?  I'm going to suspect UAC interference on some level, but that is just speculation at the moment.

Basicwiz: I'll give that a try next time it happens, thanks!

Hborre: No UAC. I turned it off the first day I got Win7! And this error has been happening on and off for the past few weeks.

You also might try emptying the render cache when this happens. On my machine it is located at:

C:Documents and SettingsAdministratorApplication DataPoser Pro2.0RenderCache

Depending on where you installed things, this will vary.

Just highlight everything in that directory and delete. This is a brute force way of clearing things, but failing all else it will work.

If none of the above helps, try turning off "Use external binary morph targets" in your General Preferences". Then resave the pz3 using a different name. Now try rendering it again. If that fixes the problem, leave "Use external binary morph targets" permanently off. It is evil!   :mad:

I had this problem when I first started using PPro2010.  The best solution that I found was to go to the Render tab before going to the render flyout and selecting Render in background.  And just to be clear, when I say Render Tab I mean the window with your last render (this confused the hell out of me when someone pointed this workaround to me)

Do you have latest patch installed?  I don't know if this was fixed as I've gotten so used to going to the Render tab before rendering.

Well, I got the error happening again this morning so I put some of the suggestions here to the test.

First, basicwiz's suggestion to use the "Render" menu item instead of using the buttons or "Render in background" did work. Partially! It rendered a new scene, overwriting the previously frozen-in-place scene, but it didn't stop the error happening on subsequent background renders. It just froze on the new scene I'd rendered using menu-item "Render".

Second, Vestmann's suggestion to switch to the Render tab before submitting a background render worked, too. The frozen-in-place render disappeared and the new scene began to be rendered as hoped for. Again, though, it didn't unlock this interesting feature but it does mean that I now know of two ways to work around it.

Third, lesbentley's "External binary morphs" suggestion isn't the problem. I learned in my P6 days to switch this evil off (just how many scenes did I lose back then until I'd discovered to do that?).

Thanks to everyone who replied.

Render in Background is a great idea, and long overdue, but it needed more quality control before releasing as a feature and a selling point.

Render in Background has been around since Poser 7 (Poser Pro)...

Then it should have been fixed by PP2010.

I think this problem surfaced in PP2010.  I don't remember having this problem in the old Poser Pro so it should have been fixed in the service releases...

I never had it in previous PPro, either, so it certainly seems to be something that appeared in PPro2010. And SR1 didn't fix it, either. Perhaps no one's actually reported it?

Quote - I had this problem when I first started using PPro2010.  The best solution that I found was to go to the Render tab before going to the render flyout and selecting Render in background.  And just to be clear, when I say Render Tab I mean the window with your last render (this confused the hell out of me when someone pointed this workaround to me)

Do you have latest patch installed?  I don't know if this was fixed as I've gotten so used to going to the Render tab before rendering.

I am on a Mac and I can verify that this solved the problem for me in PP2010. It was reported as part of the Bug-Beta process. Also there is an issue of older props and the way they are named that causes them not to render no matter what you do excluding quit-restart. Also reported as a bug. Change there name like they are saved in P7 up and they work as expected