Logo by Dinkydau - 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: Visit the official fractalforums.com Youtube Channel
 
*
Welcome, Guest. Please login or register. October 23, 2019, 05:30:29 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: Mandelbulber: Defaults not written to Settings file anymore  (Read 1185 times)
0 Members and 1 Guest are viewing this topic.
mcc
Guest
« on: July 10, 2011, 11:03:16 AM »

Hi,

the default settings are no longer written to the settings file.
This implies one drawback:
Suppose you render a few settings, which you download from
the net. The very first settings are loaded when starting the
program.
Now: Set "A" from the net has changed beside other things the
shader colors. You load this one and render. Now the colors are
like those given with set "A".
Now you load settings "B". This one has no changes made in the
shaders and left the defaults untouched. But when rendering the set
the colors no longer are the default ones: The current colors are
those which were set when setting "A" was loaded. When settings
"C" is loaded and rendered again a mix from settings from "C", "B"
and "A" are taken into account.
This problem applies to all parameters in a set, which are left unchanged
(implicitely "the defaults"). This way the more settings you are
trying the more the last parameter set become a mix of a whole
generation of setting before.

Suggested solution to this problem is to silently load the default parameter
set before every time a parameter set is loaded or pasted or otherwise
altered to ensure that all parameters which are left unchanged are really
the default ones.

Best regards and have a nice sunday!
mcc
Logged
Buddhi
Fractal Iambus
***
Posts: 895



WWW
« Reply #1 on: July 12, 2011, 07:11:43 PM »

Hi,

the default settings are no longer written to the settings file.
This implies one drawback:
Suppose you render a few settings, which you download from
the net. The very first settings are loaded when starting the
program.
...
Suggested solution to this problem is to silently load the default parameter
set before every time a parameter set is loaded or pasted or otherwise
altered to ensure that all parameters which are left unchanged are really
the default ones.

I tried to reproduce this problem but it not happens on Windows and also on Linux. Please give me some detailed example, information about Mandelbulber version and operating system which you are using.
When in settings file there is some parameter missing it is loaded from ".defaults." file. So all parameters, which are not mentioned in loaded settings file, are filled with default values.
Logged

Pages: [1]   Go Down
  Print  
 
Jump to:  

Related Topics
Subject Started by Replies Views Last post
Mandelbulber Settings Gallery Mandelbulber Buddhi 6 4146 Last post September 09, 2011, 06:06:27 AM
by Xazo-Tak
Benchmark-file for Mandelbulb3D, Mandelbulber, etc. Let's collaborate on something! VanlindtMarc 3 1047 Last post August 04, 2013, 12:26:52 PM
by taurus
Settings of www.mandelbulber.com/gallery_page1.php Mandelbulber noscio 7 2772 Last post February 18, 2015, 08:22:43 PM
by taurus
Mandelbulber 2.06 Newbie questions about settings files Help & Support Phil J 9 461 Last post March 07, 2016, 12:49:42 AM
by cKleinhuis
Mandelbulber 2.06 - exr not written Bug Reporting verstaerker 6 853 Last post March 17, 2016, 09:04:34 PM
by verstaerker

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.14 seconds with 28 queries. (Pretty URLs adds 0.009s, 2q)