All Activity

Create sections (green) at several points along the object. Explode the sections then set a UCS to the plane of a section and create offset curves (red) with a distance equal to the desired fillet radius. I used 0.2. Add a circle of the fillet radus at the intersection of the offset curves and then trim the circle. Create a polyline (yelllow) to form a closed shape that includes the "fillet" arc (cyan). With pedit create closed polylines for the fillet sections then use loft to create the fillet solid. Union the two solids together.

I got to thinking about this and with some other LISPs it would be handy for my use to check if anyone has been altering a drawing on the network without permission. I normally look at the last saved time and date, but something like this might be useful to see what if anything was physically altered.

The two tubes run at different angles.

I gave the drawing a look. I am not 100% sure what you are trying to accomplish here, in order to fillet the two cylinders they need to share a common edge(s), the rectangular extrusion you have between them needs to be unioned as far as I know, if that's what you are trying to use, by the way it looks to be two of those. You might have better luck extruding a fillet shape between them and then union that to them.

I use a couple of LISPs.

Db.Transparency in ARX (and Python) is overloaded to take an alpha 0-255 or alphaPercent 0.0 – 1.0, so you can use either. 0.5 is the same as 127 in this case. In this case traceBoundary was called with detect islands = False. Of course one might like to have a different transparency between the boundary and hatch, this just illustrates one

The key is to make the Hatch entity itself see-through not the boundary lines that get drawn. The hatch must also be checked after each boundary loop is added. The main fix is the transparency value. For 50% see‑through use an alpha value 127 instead of 0.5 because Db.Transparency uses a 0–255 scale. Set it directly on the hatch for example: hat.setTransparency(Db.Transparency(127)). Also if traceBoundary returns loops find the outer loop and any inner islands separately before you call appendLoop. If you do not do this the hatch might fill spots that should stay open.

import traceback from pyrx import Ap, Db, Ed, Ge _index = 1 def makeBoundary(db: Db.Database, pnt: Ge.Point3d, tr: Db.Transparency): ids = [] plines = Ed.Editor.traceBoundary(pnt, False) for pline in plines: pline.setColorIndex(_index) # Uses the global integer pline.setTransparency(tr) ids.append(db.addToModelspace(pline)) return ids @Ap.Command() def doit(): global _index try: db = Db.curDb() tr = Db.Transparency(0.5) #50% ps, pnt = Ed.Editor.getPoint("\nSelect internal point: ") if ps != Ed.PromptStatus.eOk: return # 1. Generate the boundary polylines ids = makeBoundary(db, pnt, tr) if not ids: print("\nNo boundary found.") return # 2. Create and configure the Hatch object hat = Db.Hatch() hat.setPattern(Db.HatchPatternType.kPreDefined, "SOLID") hat.setColorIndex(_index) hat.setTransparency(tr) # 3. Add hatch to model space BEFORE appending loops (AutoCAD requirement) db.addToModelspace(hat) # 4. Establish associativity and evaluate hat.setAssociative(True) hat.appendLoop(Db.HatchLoopType.kDefault, ids) hat.evaluateHatch(True) print(f"\nCreated boundary and hatch with Color Index: {_index}") # 5. Increment color index (Cycle back to 1 if it exceeds standard ACI 255) _index += 1 if _index > 255: _index = 1 except Exception as e: print("Error encountered:") traceback.print_exc()

Hi, Drawing attached. Dale CB&Q water tower hoop lugs v2.dwg

Going back a few steps looking at your image if you were to draw the two outside circles in 2D, you can add a fillet arc using Circle TTR you need to trim the new circle and trim the existing two circles add the outer edges and so on add the inner tube circles then extrude the outside object as a pline. There may be some way to add the correct fillet to a solid beyond my pay grade some one else will jump in.

Welcome to CADTutor! Can you post the .dwg?

Hi all, I have been struggling or having a senior moment with getting a fillet between these two cylinders. Like rubbing a bead of caulk with your finger between them. Any suggestions? Thanks, Dale

For commercial AutoLISP applications I would not trust FAS VLX compilation alone. It makes looking at the source code but it should not be seen as full protection from people trying to figure out how it works. A better way is to put parts about licenses and checks into a compiled.NET component. Use a server to check licenses and connect activations to a mix of computer details. I also suggest using signed license answers storing information in a way on the computer checking online now and then and allowing a short time without internet. Do not depend on hardware IDs because changes in hardware can cause real problems with activation. One key thing to remember: no protection on the computer side is completely safe. The aim is to make it hard for people to copy and change the software while making sure real users can activate and renew easily. It would be interesting to find out if people here have done this with their licensing server or, with a company that offers licensing services.

When working with drawings received from other companies, you may encounter blocks containing attributes such as part numbers, descriptions, or reference labels. If you need to convert those blocks into ordinary drawing entities while preserving the displayed attribute values, the BURST command can be useful. Unlike EXPLODE, it converts attribute values into text rather than simply losing them. However, converting blocks can affect the original structure and editability of the drawing. When preparing external drawings for modification or data extraction, do you prefer BURST, EXPLODE, or keeping the original attributed blocks intact? What determines your choice?

In a complex 2D drawing, two or more lines may occupy exactly the same position. The drawing can look perfectly correct, but duplicate geometry can cause problems during area calculations, hatching, CNC preparation, and file conversion. One useful command is OVERKILL. It detects and removes duplicate or overlapping geometry, with options to control how objects are compared. However, running it with default settings may not always produce the desired result, especially in drawings with different layers, linetypes, or partially overlapping segments. Do you routinely run OVERKILL before issuing a drawing, or do you prefer to identify and correct overlapping geometry manually? Have you ever found a problem caused by duplicate entities?

In the draw window it's for multi story buildings so size can be different for every window. There is not a problem matching properties with a dcl. You can make better descriptions, in the code is default values you set or it can remember previous values. Just have the tools to make the dcl. If you look at the window DCL in movie on right side is edge controls these do just that a corner or a multi panel join and so on. So in your comments you talk a bit about this. Yes it's drawn via objects Plines etc. You can have shapes like the V notch. The dimensioning is just part of a program. I believe it will be easier than trying to make a dynamic block work. Given how much post time has occurred in this forum, a program would be done by now. But it is for your company only so a cost may be relevant. But you can add more shapes quickly. Will see if can find time to do some form of example. Step 1

These are ones I use: To record the current zoom: (setq currentzoom (list (getvar 'viewctr) (getvar 'viewsize))) .. zoom as you want And this returns you to where you were. (vla-ZoomCenter (vlax-get-acad-object) (vlax-3d-point (car currentzoom)) (cadr currentzoom)) Never tried with viewports but some ssget types need the entities to be selected to be in view, maybe viewports are the same

Here's another without command calls: (defun c:zal (/ a d c tabs) ;; RJP » 2020-07-08 (setq c (getvar 'ctab)) (vlax-for x (vla-get-layouts (setq d (vla-get-activedocument (setq a (vlax-get-acad-object))))) (setq tabs (cons (list (vla-get-name x) (vla-get-taborder x)) tabs)) ) ;; The sort makes sure that the tabs step left to right (foreach x (cdr (vl-sort tabs '(lambda (r j) (< (cadr r) (cadr j))))) (setvar 'ctab (car x)) (vlax-put d 'mspace 0) (vla-zoomextents a) ) (setvar 'ctab c) (princ) )

I am still working on this, works pretty good on everything but blocks now. I can place my crosshairs on blocks no problem, they work off the dimension, Centermark command needs an object, I think I have that sorted, just need time to get it working in my LISP. For my use, I have it placing the CENTERMARK in modelspace when a paperspace dimension references an object in modelspace. To maintain a correct dimension measurement on a scaled viewport the marks need to be associated with the modelspace object. My question would be, does anyone want the Centermarks in paperspace? I also have my crosshairs and plan on the Centermark to be outside of the blocks since I am just working on objects that are dimensioned and wouldn't want to update all of the blocks if more than one. Is there a case where anyone would want them inside the blocks?

Yeah fig so just left 410 in there to be safe.

I have a Zoom Extents in Modelspace and Zooms Extents, then .9x in all layouts, it helps with the offset AutoCAD puts on some drawings when opening them, plus works for finding odd paperspace items, zooms just a little more to show the edges. Still trying to determine what is wrong with Lee Mac VPOUTLINE LISP? Are you looking for a count of true viewports? I have a LISP that gives this report of true viewports in all layouts, as well as places a border in modelspace and creates/checks for my viewport layer. ====================================== AutoVPBrdr REPORT ====================================== True layout viewports: 5 Viewport layer assignments: 5 Layer assignment failures: 0 Modelspace borders created: 5 Viewports skipped: 0 -------------------------------------- Layer: Viewport Color: 45 Plot: OFF ====================================== It only places a border for a viewport referencing Top/Plan view.

BricsCAD reports the correct number of view-ports without requiring looping through the layouts first.

As well as spend time making full instructions and even some videos of them in action.

Thank you

I would avoid setting each flange. Begin with the panel dimensions then add horizontal, vertical, parallel and 45‑degree constraints only where the shape needs them. Measure each flange length on its own if the lengths can change. Look at the remaining degrees of freedom before adding another restriction because a missing restriction may control rotation or skew of length. Which CAD software are you using?