Decoding Mandelbulb3D parameters?

[OSAlien]

I was wondering if there was any simple way for me to decode Mandelbulb3D parameters. After messing around with parameters I've found I've managed to be able to (somewhat) control resolution before loading the file, but I would like to know how the parameter is encoded/prepared, as I have an idea for a project.

[lenord]

In a single word...Nope!

Formulas yes, Params, no way...

[Sockratease]

I was wondering if there was any simple way for me to decode Mandelbulb3D parameters. After messing around with parameters I've found I've managed to be able to (somewhat) control resolution before loading the file, but I would like to know how the parameter is encoded/prepared, as I have an idea for a project.

I think it was once stated that the text format is really machine code representing the formulas, combination type, and parameters for each variable.

So if you know machine code, it's possible.  Otherwise...  Try this:

 

[cKleinhuis]

so, to bring some light to it, it is definately no machine code, the machine code is just in the formulas, and in the mb3d config file
is saved an index or the name of the formula that is used, together with the parameters everything needed for a scene is inside
the params (@jesse please correct me if wrong )

the parameters are encoded binary and then transformed to a copy&paste able text, that is used to decipher it, for interpreting
the content you have to now the encoding system used, it might be just base64 encoding, but this information has to be retrieved
from the programmer....

[taurus]

... it is definately no machine code
...the parameters are encoded binary and then transformed to a copy&paste able text...

Thanks for clarifying. I think binary and machine-code are often mistaken.

but this information has to be retrieved from the programmer....

I doubt, that Jesse lays his cards on the table in this case...

[Jesse]

I was wondering if there was any simple way for me to decode Mandelbulb3D parameters. After messing around with parameters I've found I've managed to be able to (somewhat) control resolution before loading the file, but I would like to know how the parameter is encoded/prepared, as I have an idea for a project.

The only problem i see is that parameter structures will always change from release to release, so the project might only work for a specific release.

The m3p parameter format is just the binary saved record (windows byte order) of all parameter, and the text format is then further converted to ASCII.

So if you tell what parameter you want to change, i will try to give the infos for the offset and value type, but can take a while because i am a bit short of time...

[OSAlien]

The only problem i see is that parameter structures will always change from release to release, so the project might only work for a specific release.

The m3p parameter format is just the binary saved record (windows byte order) of all parameter, and the text format is then further converted to ASCII.

So if you tell what parameter you want to change, i will try to give the infos for the offset and value type, but can take a while because i am a bit short of time...

Ideally, I'd like all of them. I have no problem with waiting, take all the time you need.
Editing saved files through a hex editor has gotten me a little farther, as I can see the names of the base formulas used, however values used are still 'unreadable'.

[Jesse]

Sorry that i did not replied earlier, but all parameters would be not an option anyway.   

The values for each formula must somewhere after the formula name and are always 16 double values in this format:
http://en.wikipedia.org/wiki/Double-precision_floating-point_format

So you might figure out by yourself where they are.
Of course only as much values are used, as the formula parameters got.

Hth so far at least.