Mandelbulber: Defaults not written to Settings file anymore

[mcc]

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

[Buddhi]

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.