SLW210 Posted 53 minutes ago Posted 53 minutes ago So in keeping with posting some of my LISPs, I used this just the other day, and just was reminded with the recent resurrection of the Fillet 0 issue thread where the OP was doing 40,000, not sure what LISP they used. Per the latest resurrection, setting FILLETPOLYARC setting may or may not help depending on what you are trying to fillet. The few times I have seen Fillet 0 fail with the P option was when the fillet radii completed something like a half circle when adjacent corners are filleted (something like the ends of a slot). This can be handy dandy. There are others like this around. For my use this was better than a few of the ones I tried. You may need to change the FILLETPOLYARC=0 if you have issue using this with Radius=0. In those situations when I had an issue, the LISP just doesn't do anything to those fillets, so I just go back with a small radius and change them, then you should be able to Fillet=0 those. (defun c:MF () (c:MultiPolyFillet) ) (defun c:MultiPolyFillet (/ radius ss i ent) (setq radius (getdist "\nFillet radius: ")) (if radius (progn (setvar "FILLETRAD" radius) (setq ss (ssget '((0 . "LWPOLYLINE,POLYLINE")))) (if ss (progn (setq i 0) (while (< i (sslength ss)) (setq ent (ssname ss i)) (command "_.FILLET" "_P" ent) (setq i (1+ i)) ) ) ) ) ) (princ "MultiPolyFillet complete.") (princ) ) (princ "\nMultiPolyFillet loaded. Type MultiPolyFillet or MF to run." ) (princ) 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.