You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears in R15, most likely due to changes to the modelling tools (most of all the new bevel tool), Chamfer Maker when applied kills all existing geometry instead of producing the proper in-between edges etc.
Have to get me the R15 demo and take a look at the underlying SDK changes if they included the new SDK version with the demo.
No milestone set (read: don't expect a fix to happen right away).
The text was updated successfully, but these errors were encountered:
Ok, I found the bug. Chamfer Maker uses SendModellingCommand internally which instruments the C4D internal bevel tool by setting its options and executing it. However, as stated previously, the bevel tool was replaced with a new version.
Trouble is, the R15 SDK in its current form still includes the interface for the old incarnation of the bevel tool. So SendModellingCommand accepts the settings as if it were the old bevelling tool but then just fails as it tries to execute the new tool. The effect is that no modified geometry is returned effectively killing all edges.
I posted a topic in MAXON's dev forums asking for how to properly access the new bevel tool with SendModellingCommand.
Btw, that's also why AMa_ParallelMode still works. This only helps if Chamfer Maker is put under a HyperNURBS though.
Bug was fixed with the R15 version. A new repository was created because there were too many changes to keep the code base for both APIs (pre-R15 and R15).
It appears in R15, most likely due to changes to the modelling tools (most of all the new bevel tool), Chamfer Maker when applied kills all existing geometry instead of producing the proper in-between edges etc.
Have to get me the R15 demo and take a look at the underlying SDK changes if they included the new SDK version with the demo.
No milestone set (read: don't expect a fix to happen right away).
The text was updated successfully, but these errors were encountered: