Sat, Jan 11, 4:19 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 11 12:18 am)



Subject: PPro2010: Missing pixels!


Michael314 ( ) posted Sun, 14 March 2010 at 7:55 AM · edited Sat, 11 January 2025 at 4:17 PM

file_449477.jpg

Hello, I made a render with the Poser Pro 2010  in queue (local queue on same computer). Unlike the preview I did inside Poser itself, the final render with better resolution has some white spots. These don't look like IDL problems, more like as if they had been forgotten at all!

Has anyone else seen these issues? I did not have that with the beta or the previous
Poser Pro.

Best regards,
   Michael

P.S.: I'm on XP64, using the 64 bit version of Poser Pro 2010.


vxg139 ( ) posted Sun, 14 March 2010 at 11:59 AM · edited Sun, 14 March 2010 at 12:03 PM

Not seen that, but have other issues with Poer Pro 2010.... like twist button not functioning, slower rendering than Poser Pro (w/ similar setting), system hanging up and the list goes on.....

Rmoved the Poser Pro 2010... and am going to wait for a couple of months until most of the known bugs are ironed out.....

Sorry couldn't be help on your question....


wimvdb ( ) posted Sun, 14 March 2010 at 12:06 PM

How many threads are you using and what bucketsize?


vxg139 ( ) posted Sun, 14 March 2010 at 12:28 PM

multiple thread tests (12, 24 and 30) w/80 Bucketsize....unfortunately, didn't see much improvement.....with Poser Pro (4 threads) I seem to be gietting significantly faster responses (both during setting the scene and rendering).....


wimvdb ( ) posted Sun, 14 March 2010 at 1:04 PM

Number of threads and bucketsize influence the speed of the render. Unfortunately this is very much dependent on the scene you are rendering. If there are large "difficult" areas (those where reflection/refraction and/or transpareny are involved) you are better off with smaller bucketsizes and higher number of threads to spread the load evenly on the processor cores. But this goes at an expense - the "not so difficult" portions will go slower overall because it is less efficient.

In my tests I found that a bucketsize of 32 and the number of threads equal to the number of cores is on average the fastest. In practice I set the number of threads one lower as the number of cores to keep the pc responsice to other  tasks. Again - in my tests - on average the speed of P8 and PP2010 is about 10-20 percent faster as PoserPro due to the better bucketmanagement.

Regarding the missing pixels - I have seen them in the early PP2010 beta and lowering the number of threads seem to resolve these.; I have not seen them in the released version. Better open a ticket to Smith Micro with the particulars to get that resolved.
 


vxg139 ( ) posted Sun, 14 March 2010 at 1:15 PM

Thanks for the heads up wimvdb.... will re-install PP 2010 and try your suggestion....

BTW, are you able to rotate a figure/prop by moving the mouse over the twist button?


wimvdb ( ) posted Sun, 14 March 2010 at 1:36 PM

No, not really - only in very small increments. I never noticed because I always use the bodydials in the parameter window. This looks like a genuine bug


Michael314 ( ) posted Wed, 17 March 2010 at 1:05 PM

file_449681.jpg

> Quote - How many threads are you using and what bucketsize?

Hello,
I use bucket size 32 or 64, and 4 threads (I have 4 cores).

This happened only once, but another time I had this problem:

(The pink area was transparent in the render, and these 3 big black spots.
The same image rendered OK another time).

As these are just 1 out of 20 renders, and PoserPro2010 is perfectly stable
otherwise, I wonder if they are due to hardware (but I had never any issue with
another program or another Poser version.)

Best regards,
  Michael


ratscloset ( ) posted Wed, 17 March 2010 at 1:24 PM

For Threads.. you want it equal to or double your number of Cores. If rendering in the Program, you want Separate Processes checked.

You indicated that it does not happen every time.. if you Save the image, does it have the artifact?

I have an issue using C4D that if I have several back to back Renders, that I get an artifact in the Render, but when I Save the image, it was not there... but obviously was in the display.

ratscloset
aka John


Michael314 ( ) posted Sun, 21 March 2010 at 4:51 AM

Hi John,
it was in the generated image, I could see it in the preview in the second case as well,
before saving the image.
 
Best regards,
  Michael


ratscloset ( ) posted Sun, 21 March 2010 at 9:55 PM

If you can get steps to duplicate, contact Support... if not, you can contact and we can try to figure out the cause so it can get reported if it is a bug... issues that are Random are hard to isolate, but if you are willing, we can try. Put Attn: John in the Subject when you contact Support and I will look for it.

ratscloset
aka John


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.