-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CGAL error found in bevel_gear #64
Comments
In case anyone with gear maths is looking, apex_to_apex appears to be wrong. Affecting the last cylinder in the difference (and probably more). |
Nope, more complex than that... |
<edit duplicate> |
Make that line ~180 |
..and it involves pressure_angle, 36 is OK, 38 crosses the tip. |
@hamiltont if you want a hack that gets past the CGAL error, in
It just forces the points to be on the correct side of the axis. There is also a bug with the sprocket like protrusions inside the hole, but you can fix that with a difference. |
@MichaelAtOz Wow! Thanks for the effort here. I'm crunched with my day job, but as soon as I resume this side project I'll try to follow along with your work. Maybe I can contribute something |
@hamiltont Actually the above hack does affect the involute profile: This (also a hack) is closer, but also loses the flat top:
I don't know the basis for the shape of the tooth that loop is trying to calculate. |
When using
bevel_gear
with these other values, anypressure_angle > 38
seems to cause a CGAL error. I have reduced the error example down to this one line, but it may be possible to further reduce it and identify the specific parameter combination which causes this error. The problem appears to be the gear teeth, as the model will finish rendering but will not have any gear teeth.ERROR: CGAL error in CGALUtils::applyBinaryOperator union: CGAL ERROR: assertion violation! Expr: G.mark(v1,0)==G.mark(v2,0)&& G.mark(v1,1)==G.mark(v2,1) File: /Users/kintel/code/OpenSCAD/libraries/install/include/CGAL/Nef_S2/SM_overlayer.h Line: 304
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: