Logo by Trifox - Contribute your own Logo!

END OF AN ERA, FRACTALFORUMS.COM IS CONTINUED ON FRACTALFORUMS.ORG

it was a great time but no longer maintainable by c.Kleinhuis contact him for any data retrieval,
thanks and see you perhaps in 10 years again

this forum will stay online for reference
News: Did you know ? you can use LaTex inside Postings on fractalforums.com!
 
*
Welcome, Guest. Please login or register. April 23, 2024, 08:55:14 AM


Login with username, password and session length


The All New FractalForums is now in Public Beta Testing! Visit FractalForums.org and check it out!


Pages: [1]   Go Down
  Print  
Share this topic on DiggShare this topic on FacebookShare this topic on GoogleShare this topic on RedditShare this topic on StumbleUponShare this topic on Twitter
Author Topic: Ambient illumination changes cased by image render size - ?  (Read 2637 times)
0 Members and 1 Guest are viewing this topic.
Sfumato
Safarist
******
Posts: 94



« on: August 12, 2011, 10:20:48 PM »

Dear friends, I found myself in a strange situation not for the first time (and it seems to be only in 1.7.3, not in 1.6.9 or 1.7.2): the image was prepared for rendering on a notebook and had dimensions say 500x700. Then I usually take the parameters (m3i) to my more powerful graphic station, open, set dimensions, say 3500x4900, decrease raystep multiplier, stepwidth limiter, press 'Calculate 3D' and go to bed if Parameters OK in the below window and 'togo' isn't say 23hrs...
The image I saw in the morning lately is far from making my day: they are much lighter and I have to spend bunch of time adjusting light for > 17Mpx image once again. So I experimented a wee, rendered a 2770x3490 image and then reduced the dimensions to 693x872. As I had expected the image became darker (only global lights used, neither positional, nor lightmaps).
Please tell me what is the right way to change the light conditions (i. e. parameters) in case one changes dimensions of image rendered.
Thank You in advance,
Sfumato.
Logged
Jesse
Download Section
Fractal Schemer
*
Posts: 1013


« Reply #1 on: August 13, 2011, 02:27:34 AM »

Just changing the image size without changing the DEstop value (how near the raymarching stops infront of the object) changes the iterationcount of the objects surface, meaning there is more detail, other shapes, other colors.. and maybe more.

So there could be some effects that changes the light amount, like the color of the object getting darker or brighter, and because you changed the raystep multiplier and or the limiter, the dynamic fog is also changing (if enabled) what can lead to big light changes.

This is a general problem where no easy solution exists, you always have to adjust these parameters in the final rendering.

Or do the preview rendering with the same raystep multiplier etc and downscale the DEstop value like the imagesize, then you get a more similiar result (without guarantee).
Logged
Sfumato
Safarist
******
Posts: 94



« Reply #2 on: August 13, 2011, 08:12:24 AM »

Thank You very much, Jesse for substantial and prompt reply! Of course it's DE stop - now that You explained it it seems sobvious :-)
With kindest regards,
Have a lovely weekend,
Sfumato.
Logged
Pages: [1]   Go Down
  Print  
 
Jump to:  

Related Topics
Subject Started by Replies Views Last post
Image change with render size? Mandelbulb 3d MarkJayBee 6 5719 Last post March 15, 2012, 07:17:20 PM
by MindsEye
"Render Selection at render size" feature request PhotoComix 10 4263 Last post February 19, 2013, 02:15:21 PM
by taurus
Render size vs. Animation size? Mandelbulb 3d Weber 3 10184 Last post September 20, 2013, 12:21:11 AM
by Sockratease
Render size vrs. amount of memory Mandelbulb 3d haltenny 2 6704 Last post December 15, 2014, 11:25:41 AM
by haltenny
Maximum render size Kalles Fraktaler Dinkydau 4 1700 Last post February 16, 2017, 11:32:12 PM
by Dinkydau

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM
Page created in 0.163 seconds with 28 queries. (Pretty URLs adds 0.008s, 2q)