Page 10 of 12
Re: Cinema 4D version 2018.1.3-R3 (Latest stable) - 14.09.2019
Posted: Wed Sep 18, 2019 11:00 am
by aoktar
AaronWestwood wrote:Using the updated R3, inside R21, Scatter seeds still behave incorrectly/broken. Any ideas when this will be addressed (only asking as I need it for a current job

)
To be clear these are the issues, that never existed prior.
- re positioning the source geometry re seeds
- scaling the clone re seeds
- rendering to picture viewer re seeds
- undoing a seed change re seeds
This can be replicated using a simple plane + scattering spheres. Nothing fancy.
I'm not aware of something broken/etc... on scatter. Because I haven't changed anythings on scatter. It can be due to internal changes of R21 or compiling of plugin for R21.
Re: Cinema 4D version 2018.1.3-R3 (Latest stable) - 14.09.2019
Posted: Wed Sep 18, 2019 12:10 pm
by AaronWestwood
Yeh I thinks its exclusive to R21.
I swapped from R18, and using it for years with scatter I never had this issue.
Is there anything I can try, or is there an easy fix perhaps? I have the R21 subscription so there's no going back...
Re: Cinema 4D version 2018.1.3-R3 (Latest stable) - 14.09.2019
Posted: Wed Sep 18, 2019 12:24 pm
by aoktar
AaronWestwood wrote:Yeh I thinks its exclusive to R21.
I swapped from R18, and using it for years with scatter I never had this issue.
Is there anything I can try, or is there an easy fix perhaps? I have the R21 subscription so there's no going back...
I'm investigating that, It's not my fault that I can say. Some unexpected results by new surprise of R21
Re: Cinema 4D version 2018.1.3-R3 (Latest stable) - 14.09.2019
Posted: Wed Sep 18, 2019 12:39 pm
by AaronWestwood
aoktar wrote:AaronWestwood wrote:Yeh I thinks its exclusive to R21.
I swapped from R18, and using it for years with scatter I never had this issue.
Is there anything I can try, or is there an easy fix perhaps? I have the R21 subscription so there's no going back...
I'm investigating that, It's not my fault that I can say. Some unexpected results by new surprise of R21
Totally understand I assumed the same, thanks R21. Thankyou so so much Aoktar. Looking forward to any updates

Re: Cinema 4D version 2018.1.3-R3 (Latest stable) - 14.09.2019
Posted: Thu Sep 19, 2019 10:12 am
by AaronWestwood
Also I wrote a few messages back but it may of gotten missed, but another bug (maybe also exclusively R21) is that store render buffer tonemaps really differently. The stored image in A/B comparison is much lighter and washed out.
This obviously makes comparisons really difficult. Again I think this is an error that R21 created...
Re: Cinema 4D version 2018.1.3-R3 (Latest stable) - 14.09.2019
Posted: Thu Sep 19, 2019 1:42 pm
by aoktar
AaronWestwood wrote:Also I wrote a few messages back but it may of gotten missed, but another bug (maybe also exclusively R21) is that store render buffer tonemaps really differently. The stored image in A/B comparison is much lighter and washed out.
This obviously makes comparisons really difficult. Again I think this is an error that R21 created...
I checked it, it's happening on just R21. Don't know why it acts like that, investigating.
EDIT: Found the reason and fix. It's about a change on defaults of C4D's bitmap functions. Will be fixed on next build.
Re: Cinema 4D version 2018.1.3-R3 (Latest stable) - 14.09.2019
Posted: Thu Sep 19, 2019 8:12 pm
by AaronWestwood
aoktar wrote:AaronWestwood wrote:Also I wrote a few messages back but it may of gotten missed, but another bug (maybe also exclusively R21) is that store render buffer tonemaps really differently. The stored image in A/B comparison is much lighter and washed out.
This obviously makes comparisons really difficult. Again I think this is an error that R21 created...
I checked it, it's happening on just R21. Don't know why it acts like that, investigating.
EDIT: Found the reason and fix. It's about a change on defaults of C4D's bitmap functions. Will be fixed on next build.
Amazing well done! Looking forward to that. By chance any headway on the scatter, or is that a trickier beast?
Re: Cinema 4D version 2018.1.3-R3 (Latest stable) - 14.09.2019
Posted: Thu Sep 19, 2019 8:13 pm
by AaronWestwood
aoktar wrote:AaronWestwood wrote:Also I wrote a few messages back but it may of gotten missed, but another bug (maybe also exclusively R21) is that store render buffer tonemaps really differently. The stored image in A/B comparison is much lighter and washed out.
This obviously makes comparisons really difficult. Again I think this is an error that R21 created...
I checked it, it's happening on just R21. Don't know why it acts like that, investigating.
EDIT: Found the reason and fix. It's about a change on defaults of C4D's bitmap functions. Will be fixed on next build.
Amazing well done! Looking forward to that. By chance any headway on the scatter, or is that a trickier beast?
Re: Cinema 4D version 2018.1.3-R3 (Latest stable) - 14.09.2019
Posted: Thu Sep 19, 2019 9:24 pm
by aoktar
AaronWestwood wrote:
Amazing well done! Looking forward to that. By chance any headway on the scatter, or is that a trickier beast?
It's another mysterious shit of R21, looking out why it happen.
EDIT: I've managed to avoid jumping clones. They are not doing this now. But I've detected that clone positions are not same as in previous C4D versions. Because of some R21 revisions of used distribution functions in Cinema 4D. So DON'T USE old scatter object scenes in R21.
Re: Cinema 4D version 2018.1.3-R3 (Latest stable) - 14.09.2019
Posted: Fri Sep 20, 2019 6:48 pm
by AaronWestwood
aoktar wrote:AaronWestwood wrote:
Amazing well done! Looking forward to that. By chance any headway on the scatter, or is that a trickier beast?
It's another mysterious shit of R21, looking out why it happen.
EDIT: I've managed to avoid jumping clones. They are not doing this now. But I've detected that clone positions are not same as in previous C4D versions. Because of some R21 revisions of used distribution functions in Cinema 4D. So DON'T USE old scatter object scenes in R21.
Sweeet!! Fantastic news Aoktar. Any ideas when this update will be available?