Spline Round Tool behave issue

baca

Just noticed C4D 2024 has issue with Spline Round tool relatively to previous versions of C4Ds.
At least R25 has no issues.

Issue can be replicated with both editor tool and MCOMMAND method when applied to spline with knots, means which retrieved with GetRealSpline().
And appears around first original knot or first result point.

python_splineround_issue.c4d

ferdinand

Hey @baca,

thank you for reaching out to us. Please report (what you consider to be) bugs in Cinema 4D itself via our support portal; the SDK group cannot help you here.

Please make sure to share only files that do not contain plugins (yours does), and with clear reproduction steps (I had a brief peek, and I could not reproduce your problem as I have no clue what you were doing with the multiple splines in your file).

Cheers,
Ferdinand

baca

Hi @ferdinand ,

Sorry for messed attachment,

I'll try once again:

python_splineround_issue.c4d

I'm retrieving spline from the source with GetRealSpline() (to have knots with tangents)
And applying ID_MODELING_SPLINE_ROUND_TOOL with SendModelingCommand() onto it.
R25 and 2023 versions works correct.

Is that a subject for support portal?

ferdinand

Hey @baca,

Yes, that is a bug in the app, you should always report them to customer support, because when we in SDK would handle all incoming bugs in Cinema 4D, we wouldn't do anything else.

However, I had a look in our bug tracker, and I found a similar bug from one month ago (which has been labeled as fixed). But I can reproduce your issue even in the latest beta. I asked the dev who fixed this if you should report this; will answer here when he comes back to me.

Cheers,
Ferdinand

ferdinand

Hey @baca,

so, the developer was not aware of this, and he will himself add the bug report (and fix it). There is nothing you have to do in this case (and also nothing you could do to circumvent the problem).

But in the future, please report all bugs that can be triggered without using one of our APIs, to customer support.

Thank you for your understanding,
Ferdinand

ferdinand

Hey @baca,

Just as an FYI, this bug has been fixed and it will be included in one of the upcoming releases of Cinema 4D, quite likely the next release.

Cheers,
Ferdinand