On 29/03/2017 at 03:41, xxxxxxxx wrote:
Cinema 4D Version: R18
Platform: Windows ; Mac ; Mac OSX ;
Language(s) : C++ ;
got a little question... did the definition of InitFbm() change some time after R13? I see in my old code from that time that I used to pass a Real value as max_octaves to InitFbm(), but nowadays the function wants only an Int32. It seems that the definition of InitFbm() has changed some time after R13. Maybe R14, as I can't find any mention about changes in this function in the API changes since R15. Of course, there is a chance that I simply used the wrong data type back in the R13 days.
Funny: If you call InitFbm() with a max_octaves value of "1", the Ridged Multifractal Noise comes out inverted on Windows (mountains are valleys and valleys are mountains). On Mac that does not happen. I could reproduce this behavior even on an old R16 on Windows. I don't think it's desired to have different behavior on both platforms?
Also funny: The actual max_octaves value in InitFbm() does not seem to have any effect on the resulting Ridged Multifractal Noise. I have tried values from 1 up to 18, (always using 4.0 octaves in the RidgedMultifractal() function), and there was absolutely no difference in the resulting patterns (well, except for the inversion on Windows). Is that on purpose?