Showing posts with label Render. Show all posts
Showing posts with label Render. Show all posts

Wednesday, May 28, 2014

Rendering tests in Apophysis 7X

I recently started using Apophysis 7X. Probably as many others before me, setting the parameters for rendering quality can be a challenge.

I'll keep this simple. Each test I made had only one variable changing. Each test shows what was changed, you will be the judge of what works best for you. Sometimes the difference is quite small, sometimes quite big. Check it out below.


Test one, Filter Radius:
Tests included Filter Radius: 0.1, 0.2, 0.5, 0.9

Images were rendered at:
Size: 1024x768   Quality: 1000   Oversample: 2

Comparison between different filter radius settings.


Findings: 

  • The higher the filter radius value, the softer the edges of the lines will be. (0.9 being best)
  • Difference in time is minimal at the size tested (5 second difference between highest and lowest value)
  • Difference in -+0.1 is minimal. Make larger increases/decreases to notice a difference.

FILTER TESTS STATS

--- Rendering "Fae2-1-1000.jpg"" ---
  Size: 1024x768
  Quality: 1000
  Oversample: 2, Filter: 0.1
  Total time: 8 minute(s) 7.27 second(s)

--- Rendering "Fae2-2-1000.jpg"" ---
  Size: 1024x768
  Quality: 1000
  Oversample: 2, Filter: 0.2
  Total time: 8 minute(s) 10.52 second(s)

--- Rendering "Fae2-5-1000.jpg"" ---
  Size: 1024x768
  Quality: 1000
  Oversample: 2, Filter: 0.5
  Total time: 8 minute(s) 8.99 second(s)

--- Rendering "Fae2-9-1000.jpg"" ---
  Size: 1024x768
  Quality: 1000
  Oversample: 2, Filter: 0.9
  Total time: 8 minute(s) 12.63 second(s)

-------------------------------------------------------------------------------------------


Test two, Oversample:
Tests included Oversample: 1, 2, 3, 4

Images were rendered at:
Size: 1024x768   Quality: 1000   Filter: 0.5

Comparison of oversample settings


Findings: 

  • The more oversample you have, the faster it renders (16 second faster between oversample 4 and 1)
  • *I* couldn't find much difference in image quality (at least under these test settings)
  • Needs to be tested in conjunction with another variable
OVERSAMPLE TESTS STATS

--- Rendering "Fae1-5-1000.jpg"" ---
  Size: 1024x768
  Quality: 1000
  Oversample: 1, Filter: 0.5
  Total time: 8 minute(s) 21.58 second(s)

--- Rendering "Fae2-5-1000.jpg"" ---
  Size: 1024x768
  Quality: 1000
  Oversample: 2, Filter: 0.5
  Total time: 8 minute(s) 8.99 second(s)

--- Rendering "Fae3-5-1000.jpg"" ---
  Size: 1024x768
  Quality: 1000
  Oversample: 3, Filter: 0.5
  Total time: 8 minute(s) 8.92 second(s)

--- Rendering "Fae4-5-1000.jpg"" ---
  Size: 1024x768
  Quality: 1000
  Oversample: 4, Filter: 0.5
  Total time: 8 minute(s) 5.18 second(s)

-------------------------------------------------------------------------------------------


Test three, Quality Density:
Tests included Quality Density: 200, 500, 1000, 2000, 4000

Images were rendered at:
Size: 1024x768   Oversample: 2   Filter: 0.5

Comparisons between quality density values


Findings: 

  • Difference in quality density drastically affects time
  • It is most noticeable in dark areas with light flame strokes 
  • Difference between 2000 and 4000 (under these settings) is not that much, might be worth going 2000 to save time.

QUALITY  DENSITY TESTS STATS

--- Rendering "Fae2-5-200.jpg"" ---
  Size: 1024x768
  Quality: 200
  Oversample: 2, Filter: 0.5
  Total time: 1 minute(s) 39.83 second(s)

--- Rendering "Fae2-5-500.jpg"" ---
  Size: 1024x768
  Quality: 500
  Oversample: 2, Filter: 0.5
  Total time: 4 minute(s) 4.83 second(s)

--- Rendering "Fae2-5-1000.jpg"" ---
  Size: 1024x768
  Quality: 1000
  Oversample: 2, Filter: 0.5
  Total time: 8 minute(s) 8.99 second(s)

--- Rendering "Fae2-5-2000.jpg"" ---
  Size: 1024x768
  Quality: 2000
  Oversample: 2, Filter: 0.5
  Total time: 16 minute(s) 17.46 second(s)

--- Rendering "Fae2-5-4000.jpg"" ---
  Size: 1024x768
  Quality: 4000
  Oversample: 2, Filter: 0.5
  Total time: 32 minute(s) 30.84 second(s)

Tuesday, February 14, 2012

Fixing HAMPTON hair in Vue imported from DAZ

There are a few fixes for hair and other materials that need to be made in order to have Vue render them correctly. In another post I made, I spoke of how to fix the skin texture, but in this case we'll just focus on the hair.

First we have to fix the materials for both the skin and the hair.
For the skin, check my post Fixing Skin in Vue imported from DAZ

**Remember that some of DAZ's hairs are different from others, The hair used here was the Hampton. You might need to change the Highlight and bump settings depending on your scene or the Hair Object that you use.

Fixing the Materials for the Hair
  • Lower the bump to 0.01
  • In [Highlights] tab: Put [Highlight global intensity] and [Highlight global size] to 100%
  • Make sure you have [Variable Highlight] checked.
  • Right click on  [Highlight production] and go to Edit Function. Link Highlight to your Texture map and set it to gray-scale.
Once the material is fixed, there are still some issues that need to be checked on render quality, for example rendering with the presets sometimes brings unexpected results (like transparencies showing weird shadows)

Fixing the Render Settings

How I set up my Render settings in [User Settings] is:
  • Advanced effects quality: 50%
In the [Anti-Aliasing] have both Object and texture checked and then click on the Edit button
  • I find that [object anti-aliasing] for the hair works best in [Systematic]
  • [Subrays per Pixel] Min 6, Max 16
  • [Quality Threshold] Contrast 50% and Geometry 0%
Render testings

How the quality of the image changes with the use of materials changes and render settings.
  1. The first Image is how it rendered [Final] just after import.
  2. Second is after all materials have fixed the bump.
  3. Third image is after fixing the render settings in [User Settings].
  4. Fourth is after adding the correct highlights to my hair.
This should already give you pretty good results, but there is still one more thing. 

For realism its best to use [Global Radiosity] in your [Atmosphere Editor] [Light ] Of course its not necesary and it depends on what your scene needs, but here are some before and afters:

Your Atmosphere will change drastically how your model looks.

Friday, November 11, 2011

Render Batch in Vue

So, I wanted to test my theory that maybe by using Batch Render I could continue renders that I had previously started rendering and had a resume render save file.

It didnt work for me. I made a test scene where I rendered the image on normal screen render and took X time. I then started the render and halfway I stopped it, for the resume render to be tested on the Batch rendering. It came out with a Fail message and the picture just didnt render. With the Batch render screen open, I then clicked on add current where it seemed to render the picture in full from the begining. And it took the same time. So no resume render.

I know this is not properly tested but I wanted to post my findings somewhere for the mean time. if i figure something else, ill update this.

So  Things to remember:

  • Dont add to the batch a resume render as it will crash
  • Prepare scenes in advance and prepare them to save to disk
  • It continues rendering on the BG so you can still work on vue
  • Add an auto-save timer that suits your purpose
Thats that for now. To be updated once I gather more info.