Mon, Jan 27, 1:49 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

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



Subject: Superfly and Rendering


arrow1 ( ) posted Sat, 02 February 2019 at 2:59 PM · edited Sun, 26 January 2025 at 9:56 PM

I normally render my scenes with Superfly (still images) at 300 DPI and 3000 X 2000 pixels. A render can take 2 days or more.Am I wrong with my settings or does Superfly offer better rendering at a lower setting? If so can anyone suggest a better formula? I am after extreme quality for printing! Cheers

Custom built computer 128 gigs RAM,4 Terabyte hard drive, NVIDIA RTX 4060 TI 16 GIG Gig,12 TH Generation Intel i9, Dual LG Screens, 0/S Windows 11, networked to a Special 12th Generation intel I9, RTX 3060 12 Gig, Windows 11,64 gigs RAM, Dual Phillips Screens, 2 Terabyte SSD Hard Drive plus 1 Terabyte Hard Drive,3rd Computer intel i7,128 gigs ram, Graphics Card NVIDIA RTX 3060 Gig,1 Terabyte Hard Drive, OS Windows 11 64 Bit Dual Samsung Syncmaster 226bw Screens.Plus INFINITY Laptop 64 Bit,64 gigs RAM.Intel i9 chip.Windows 11 Pro and Ultimate. 4 x 2 Terrabyte Hard Drives and 2 x 2 Terrabyte external USB Hard drives. All Posers from 4 to Poser 2010 and 2012, 2014. Poser 11 and 12, 13, Hexagon 2.5 64 Bit, Carrara 8.5 Pro 64 bit, Adobe Photoshop CS4 Creative Production Suite. Adobe Photoshop CC 2024, Vue 10 and 10.5 Infinite Vue 11 14.5 Infinite plus Vue 15 and 16 Infinite, Vue 2023 and 2024, Plant Catologue, DAZ Studio 4.23, iClone 7 with 3DXchange and Character Creator 3, Nikon D3 Camera with several lenses.  Nikon Z 6 ii and Z5. 180-600mm lens, 24-70 mm lens with adapter.Just added 2x 2 Terrabyte portable hard drives.


bagginsbill ( ) posted Sun, 03 February 2019 at 10:25 AM · edited Sun, 03 February 2019 at 10:28 AM

I fear your question may be assembled from false assumptions. First, there is no DPI in Poser - it is PPI, pixels per inch. Second, this is not a render setting. It is a number (literally that and nothing more) stored in some image file formats, but not all. It is a number used by software that formats for print media that may or may not affect how big (in inches) the printed image will be. It is quite a mystery as to why Poser makes you choose this number BEFORE rendering. It doesn't apply until you save the render as an image, and as such should be asked of you AT THAT MOMENT, not before.

From the point of view of rendering and then viewing on screen, the PPI value doesn't affect or influence anything at all. Try it - set it to 100000 and then 2, the render time is the same and the image looks the same when viewed on your screen.

Total number of pixels is a determinant, and you're rendering 6 million of them when you render for 3000 x 2000. That's a lot of work. But if you actually want to look at a 3000 x 2000 image on screen, I suppose you have one of those new 4K monitors? I don't, so rendering 6 megapixels is a giant waste for me.

Do you print your images, or look at them on a screen?

After we get past the issue of megapixels (and PPI if you're actually printing them), we would then talk about actual settings that matter and affect time vs. quality.


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


bobbesch ( ) posted Sun, 03 February 2019 at 12:22 PM

Hello Arrow1, do you consider to upgrade to poser 11 pro? The pro Version can use the GPU of a NVIDIA graphics card which may speed your renders up.


arrow1 ( ) posted Sun, 03 February 2019 at 1:44 PM

I already have Poser Pro 11! I used to work in the print media and when we enhanced images in Adobe Photoshop for pre production image quality was important, DPI was also important. Are you saying that with 3D that this is not the case? I am open to any suggestions that might make my render times shorter and of high quality. Sometimes I print my renders out but mainly I view them on the screen and save in a folder. Cheers

Custom built computer 128 gigs RAM,4 Terabyte hard drive, NVIDIA RTX 4060 TI 16 GIG Gig,12 TH Generation Intel i9, Dual LG Screens, 0/S Windows 11, networked to a Special 12th Generation intel I9, RTX 3060 12 Gig, Windows 11,64 gigs RAM, Dual Phillips Screens, 2 Terabyte SSD Hard Drive plus 1 Terabyte Hard Drive,3rd Computer intel i7,128 gigs ram, Graphics Card NVIDIA RTX 3060 Gig,1 Terabyte Hard Drive, OS Windows 11 64 Bit Dual Samsung Syncmaster 226bw Screens.Plus INFINITY Laptop 64 Bit,64 gigs RAM.Intel i9 chip.Windows 11 Pro and Ultimate. 4 x 2 Terrabyte Hard Drives and 2 x 2 Terrabyte external USB Hard drives. All Posers from 4 to Poser 2010 and 2012, 2014. Poser 11 and 12, 13, Hexagon 2.5 64 Bit, Carrara 8.5 Pro 64 bit, Adobe Photoshop CS4 Creative Production Suite. Adobe Photoshop CC 2024, Vue 10 and 10.5 Infinite Vue 11 14.5 Infinite plus Vue 15 and 16 Infinite, Vue 2023 and 2024, Plant Catologue, DAZ Studio 4.23, iClone 7 with 3DXchange and Character Creator 3, Nikon D3 Camera with several lenses.  Nikon Z 6 ii and Z5. 180-600mm lens, 24-70 mm lens with adapter.Just added 2x 2 Terrabyte portable hard drives.


bobbesch ( ) posted Sun, 03 February 2019 at 2:30 PM

" DPI was also important." DPI is only important if you print something out or if you want to know how big a picture will appear on a specific monitor. A digital picture by itself has no physical dimensions and is defined only by its pixelsize. Are you already rendering using your Graphics card? What bucket size?


bagginsbill ( ) posted Sun, 03 February 2019 at 2:44 PM

bobbesch is correct. But I made more specific points in my first post. Read each sentence carefully and think about it.

Points I made:

  • DPI doesn't exist unless you print
  • Poser doesn't have DPI anywhere - it has PPI - your concern about PPI has nothing to do with DPI
  • PPI doesn't affect rendering speed - it affects printing image physical size - nothing do with "3d rendering" - it's an intrinsic property of digital images WHEN PRINTED
  • Your questions are about rendering speed. PPI doesn't affect rendering speed.
  • The dominant issue in rendering speed is how big an image you render - you're rending 6 mega pixels - why? You intend to print?


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


JohnDoe641 ( ) posted Sun, 03 February 2019 at 2:45 PM

bobbesch posted at 3:40PM Sun, 03 February 2019 - #4345140

Hello Arrow1, do you consider to upgrade to poser 11 pro? The pro Version can use the GPU of a NVIDIA graphics card which may speed your renders up.

He has a Quadro K2200, that card is old and way too slow to be of any use. With only 640 CUDA cores and PCI-E 2.0 it may be better to just stick with his CPU for rendering.

Also arrow1, it's NVIDIA, not "NVIDEA". :P


bagginsbill ( ) posted Sun, 03 February 2019 at 2:55 PM · edited Sun, 03 February 2019 at 2:55 PM

Here is a selfie of me in front of a printed digital image (photograph of Ronda Spain). The original digial image is 6 megapixel, about the same as you're rendering. I printed it at 30 inches by 20 inches. So the pixels per inch (PPI) is literally 3000 / 30, or just 100 PPI. The actual dots this was printed with were 2400 DPI, because the printer that produced this image had literally two thousand four hundred dots of color it could place for every inch of this picture. The DPI, 2400, had NOTHING WHATSOEVER to do with the PPI, 100, of this image.

Note also that everybody who sees this agrees its an amazing image, despite being 100 PPI.

Now - can we move on and discuss things that affect rendering speed? PPI and DPI do not.

DSC03495.JPG


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


arrow1 ( ) posted Sun, 03 February 2019 at 6:21 PM

Many thanks everyone for for replies.I am a little confused with what has been said!!! Is everyone saying that if I want a high quality render I forget about pixel size and dpi or ppi? If that is the case with my present computer setup what are the suggestions for a Superfly settings for a good quality render and how should I go about it? Also as side issue.What recommendations are there for a good NVIDiA Card? Cheers

Custom built computer 128 gigs RAM,4 Terabyte hard drive, NVIDIA RTX 4060 TI 16 GIG Gig,12 TH Generation Intel i9, Dual LG Screens, 0/S Windows 11, networked to a Special 12th Generation intel I9, RTX 3060 12 Gig, Windows 11,64 gigs RAM, Dual Phillips Screens, 2 Terabyte SSD Hard Drive plus 1 Terabyte Hard Drive,3rd Computer intel i7,128 gigs ram, Graphics Card NVIDIA RTX 3060 Gig,1 Terabyte Hard Drive, OS Windows 11 64 Bit Dual Samsung Syncmaster 226bw Screens.Plus INFINITY Laptop 64 Bit,64 gigs RAM.Intel i9 chip.Windows 11 Pro and Ultimate. 4 x 2 Terrabyte Hard Drives and 2 x 2 Terrabyte external USB Hard drives. All Posers from 4 to Poser 2010 and 2012, 2014. Poser 11 and 12, 13, Hexagon 2.5 64 Bit, Carrara 8.5 Pro 64 bit, Adobe Photoshop CS4 Creative Production Suite. Adobe Photoshop CC 2024, Vue 10 and 10.5 Infinite Vue 11 14.5 Infinite plus Vue 15 and 16 Infinite, Vue 2023 and 2024, Plant Catologue, DAZ Studio 4.23, iClone 7 with 3DXchange and Character Creator 3, Nikon D3 Camera with several lenses.  Nikon Z 6 ii and Z5. 180-600mm lens, 24-70 mm lens with adapter.Just added 2x 2 Terrabyte portable hard drives.


bagginsbill ( ) posted Mon, 04 February 2019 at 2:38 PM

I don't know how to make it any more clear other than discuss each point by itself. So let's take them one by one.

DPI doesn't exist unless you print. It is the dots of ink per inch your printer spits out. It is defined by the printer, not the image you're printing.

Is that clear or no?


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


bagginsbill ( ) posted Mon, 04 February 2019 at 2:42 PM · edited Mon, 04 February 2019 at 2:45 PM

These are printer ink dots, greatly magnified.

image.pngimage.png

The measure of how many of these there are per inch is dots per inch, DPI. This is a property of your printer. It is not a property of your image, or the rendering process that produces the image.

The DPI of a given printer is always the same regardless of the image you print on it.

Is that clear? Once you are satisfied that you understand now what a dot is, and how you cannot influence these dots with your render settings, we can move on to the next point.


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


bagginsbill ( ) posted Mon, 04 February 2019 at 2:47 PM

image.png


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


bagginsbill ( ) posted Mon, 04 February 2019 at 2:49 PM · edited Mon, 04 February 2019 at 2:50 PM

Pixels per inch is a property of YOUR MONITOR. It is not a property of your image. Images do not have inches. You can try to set the PPI for an image but this is just advice for showing the image scaled to a particular output device, whether that is made of pixels (a screen) or dots (a piece of paper with ink on it).

In no case is the PPI or DPI going to change how long it takes to render an image. How long it takes to render is affected by how many pixels you render - period. end of sentence.

Poser developers have done a great disservice by offering to let you type a number into the PPI part of the render dimension dialog. The image width and height in pixels is the only thing that matters to the renderer and the only thing that affects how long it takes to render.


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


bagginsbill ( ) posted Mon, 04 February 2019 at 2:53 PM

Now - you are rendering 3000 x 2000. Why?

When you look at your image, is it on a screen? Does that screen only have about 2 million pixels, like all mine? If so, you are wasting your time rendering 6 million pixels.

In all the things you've said, the only one that matters is that you're rendering 6 megapixels. Why are you rendering 6 megapixels?

Are you planning to look at these 6 megapixels on a 6 megapixel monitor? Are you planning to print these 6 megapixels on a piece of paper 4 feet wide? If not, then the first thing to do to speed up your renders is render fewer megapixels.

If your monitor is 1920x1080, then render to that size - anything bigger is just wasting time.


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


bagginsbill ( ) posted Mon, 04 February 2019 at 2:56 PM

Once you're rendering at a size that is not wasting resources, then you may want to do other things to improve. But first, let's find out what size you should be rendering. I believe that size should NOT be 3000 x 2000.

After we choose a sensible pixel size, then we can revisit whether that's taking too long or not. We can do things to improve speed after we've determined that you still have a problem.


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


bagginsbill ( ) posted Mon, 04 February 2019 at 3:00 PM

This render is only 900 x 900, which is 810,000 pixels. I think it conveys everything I wanted to show in it. (Which is that Poser can be a damn good renderer of a human head if you use a quality model and textures instead of the usual junk people buy)

What do you think? Did I need to spend 48 hours on this instead of 30 minutes?

DigitalEmily.jpg


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


arrow1 ( ) posted Mon, 04 February 2019 at 3:04 PM

bagginsbill, Many thanks for your patience and explanation.It is a lot clearer to me now.Lately I have been making Alpha Planes of my renders so as to add to my scenes so they do not take up a lot of resources.When following tutorials they say to make the image as large as possible to retain quality.Is this still the case? What would be your suggestion as a guide for these images as a starting point? Also any advice on a good NVIDIA Card? Cheers

Custom built computer 128 gigs RAM,4 Terabyte hard drive, NVIDIA RTX 4060 TI 16 GIG Gig,12 TH Generation Intel i9, Dual LG Screens, 0/S Windows 11, networked to a Special 12th Generation intel I9, RTX 3060 12 Gig, Windows 11,64 gigs RAM, Dual Phillips Screens, 2 Terabyte SSD Hard Drive plus 1 Terabyte Hard Drive,3rd Computer intel i7,128 gigs ram, Graphics Card NVIDIA RTX 3060 Gig,1 Terabyte Hard Drive, OS Windows 11 64 Bit Dual Samsung Syncmaster 226bw Screens.Plus INFINITY Laptop 64 Bit,64 gigs RAM.Intel i9 chip.Windows 11 Pro and Ultimate. 4 x 2 Terrabyte Hard Drives and 2 x 2 Terrabyte external USB Hard drives. All Posers from 4 to Poser 2010 and 2012, 2014. Poser 11 and 12, 13, Hexagon 2.5 64 Bit, Carrara 8.5 Pro 64 bit, Adobe Photoshop CS4 Creative Production Suite. Adobe Photoshop CC 2024, Vue 10 and 10.5 Infinite Vue 11 14.5 Infinite plus Vue 15 and 16 Infinite, Vue 2023 and 2024, Plant Catologue, DAZ Studio 4.23, iClone 7 with 3DXchange and Character Creator 3, Nikon D3 Camera with several lenses.  Nikon Z 6 ii and Z5. 180-600mm lens, 24-70 mm lens with adapter.Just added 2x 2 Terrabyte portable hard drives.


bagginsbill ( ) posted Mon, 04 February 2019 at 3:06 PM

Here is a render 700 by 700. Is this not a fun picture to look at, knowing it came from Poser?

Coke Bottle.jpg

Are your 3000 x 2000 images more impressive than this?


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


arrow1 ( ) posted Mon, 04 February 2019 at 3:07 PM

PS.Judging by your 900 square image.Would that be suitable for an Alpha Channel image? Cheers

Custom built computer 128 gigs RAM,4 Terabyte hard drive, NVIDIA RTX 4060 TI 16 GIG Gig,12 TH Generation Intel i9, Dual LG Screens, 0/S Windows 11, networked to a Special 12th Generation intel I9, RTX 3060 12 Gig, Windows 11,64 gigs RAM, Dual Phillips Screens, 2 Terabyte SSD Hard Drive plus 1 Terabyte Hard Drive,3rd Computer intel i7,128 gigs ram, Graphics Card NVIDIA RTX 3060 Gig,1 Terabyte Hard Drive, OS Windows 11 64 Bit Dual Samsung Syncmaster 226bw Screens.Plus INFINITY Laptop 64 Bit,64 gigs RAM.Intel i9 chip.Windows 11 Pro and Ultimate. 4 x 2 Terrabyte Hard Drives and 2 x 2 Terrabyte external USB Hard drives. All Posers from 4 to Poser 2010 and 2012, 2014. Poser 11 and 12, 13, Hexagon 2.5 64 Bit, Carrara 8.5 Pro 64 bit, Adobe Photoshop CS4 Creative Production Suite. Adobe Photoshop CC 2024, Vue 10 and 10.5 Infinite Vue 11 14.5 Infinite plus Vue 15 and 16 Infinite, Vue 2023 and 2024, Plant Catologue, DAZ Studio 4.23, iClone 7 with 3DXchange and Character Creator 3, Nikon D3 Camera with several lenses.  Nikon Z 6 ii and Z5. 180-600mm lens, 24-70 mm lens with adapter.Just added 2x 2 Terrabyte portable hard drives.


bagginsbill ( ) posted Mon, 04 February 2019 at 4:00 PM

Oooh - alpha planes (also sometimes called billboards) are a great way to reduce render times.

The resolution (pixel size) for these would best be based on their role in the target image they are used within. If the target image size is presenting a tree alpha plane that eventually results in filling up only 100 or so pixels of the final render, then the alpha plane only needs to have roughly that much detail - 100 to 200 pixels in size would be plenty. Do you have any examples I could see?

I know my friend dreamlandmodels used billboard trees in his products. Let me see if I have any of those handy.


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


bagginsbill ( ) posted Mon, 04 February 2019 at 4:15 PM · edited Mon, 04 February 2019 at 4:15 PM

Checked some of my dreamlandmodels props. Some of his bigger trees, meant to be seen in front of houses, by the street, are using textures 1500 to 2000 pixels. Smaller bushes and trees meant to be far away are generally 800 to 1000 pixels.


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


bagginsbill ( ) posted Mon, 04 February 2019 at 4:31 PM

The tree and bushes here are all 750 to 800 pixels on a side. X1.pngx2.png


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


arrow1 ( ) posted Mon, 04 February 2019 at 6:46 PM

This a combination of several figures including DAZ and Poser Figures.It is to be inserted into a fashion show I am putting together.They were originally rendered as PNG's with an alpha channel, but I have saved them as Jpg's to put on Renderosity to show you!. CheersAudience Front Row Small.png

Custom built computer 128 gigs RAM,4 Terabyte hard drive, NVIDIA RTX 4060 TI 16 GIG Gig,12 TH Generation Intel i9, Dual LG Screens, 0/S Windows 11, networked to a Special 12th Generation intel I9, RTX 3060 12 Gig, Windows 11,64 gigs RAM, Dual Phillips Screens, 2 Terabyte SSD Hard Drive plus 1 Terabyte Hard Drive,3rd Computer intel i7,128 gigs ram, Graphics Card NVIDIA RTX 3060 Gig,1 Terabyte Hard Drive, OS Windows 11 64 Bit Dual Samsung Syncmaster 226bw Screens.Plus INFINITY Laptop 64 Bit,64 gigs RAM.Intel i9 chip.Windows 11 Pro and Ultimate. 4 x 2 Terrabyte Hard Drives and 2 x 2 Terrabyte external USB Hard drives. All Posers from 4 to Poser 2010 and 2012, 2014. Poser 11 and 12, 13, Hexagon 2.5 64 Bit, Carrara 8.5 Pro 64 bit, Adobe Photoshop CS4 Creative Production Suite. Adobe Photoshop CC 2024, Vue 10 and 10.5 Infinite Vue 11 14.5 Infinite plus Vue 15 and 16 Infinite, Vue 2023 and 2024, Plant Catologue, DAZ Studio 4.23, iClone 7 with 3DXchange and Character Creator 3, Nikon D3 Camera with several lenses.  Nikon Z 6 ii and Z5. 180-600mm lens, 24-70 mm lens with adapter.Just added 2x 2 Terrabyte portable hard drives.


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.