Did something change in the Bevel operation after R21.026?
-
In R21.026 our plugin gave following nice result (look especially at the bevels).
In R21.207 the result is not so nice anymore. Bevel shows errors?
Did something change after R21.026?
-
In the Cinema 4D R21 Service Release (21.207) change list, we found the following fixes / changes:
Could these fixes / changes be the cause of the issue?ā¢ Fixed a performance issue with the Boole object
ā¢ Fixed a stability issue with the Boole object
ā¢ Fixed a stability issue with the Shape setting of the Bevel deformer -
What does your plugin do?
How is your plugin related to Cinema's Bool or Bevel stuff?
-
Did some testing, it seems there is a bug with the intersection selection. It does not work correctly when you enable "hide new lines" previously this was working.
In the file I added you can see the incorrect intersection. If you turn off hide new lines it seems to work again. But this was previously working with this option turned on.
Hopefully Maxon can fix this issue.
-
hello,
with your scene i can confirm that in 21.200.
This is not reproducible with our last internal version of Cinema 4D.
The bug will be fixed in the next update.Cheers,
Manuel -
@m_magalhaes
Sorry, I do not quite understand what you mean.
"This is not reproducible with our last internal version of Cinema 4D." meaning you cannot reproduce the error in R21.200?"The bug will be fixed in the next update.", but there is a bug and the bug will be fixed in the next release?
-
hi,
sorry for the confusion.The last official release is 21.207. I've tested your scene with 21.200 and i do have the same bug.
I've used our internal version that is after 21.207 and the bug is gone.Of course i can't tell you when this update will be available.
For your issue, there's no real solution.
The bug is with the Bool object that doesn't select the edge. Even if you ask for a CSTO and apply the Bevel, that will not work.Cheers,
Manuel -
Great, thank you.
Let's hope 207 will be released soon! -
hi,
must be monday, sorry,
the 21.207 IS the current last public version (and after another test, the bug is definitely there). It's already out
the next update we can't tell what and when.
Cheers,
Manuel
