Forum Cadtutor

I am not too worried about it, you asked and I tested. If I get time I'll run through a few more.

You already have a thread on this topic. Stop creating the same threads over and over, please. I have already had to delete some threads you already had previously posted. You look more and more like a bot or spammer. Not sure what you are up to with all of this, everything seems copy and paste over and over. Title: Why can a LOFT create a twisted 3D shape even when the profiles look correct? - AutoCAD 3D Modelling & Rendering - AutoCAD Forums

That's g r e a t!

I’ve had LOFT produce a twisted or unexpected shape even when all the profiles looked correct. One thing that helped was checking the order and orientation of the profiles before lofting. If needed, changing the loft settings or adding guide curves can give much better control over the final shape. It’s a small detail, but it can make a big difference in complex 3D models. How do you usually control the shape when LOFT starts behaving unexpectedly?

When modelling parts with repeated holes, slots, or other features, creating each one manually can take extra time and make later changes difficult. A 3D array can help maintain consistent spacing and alignment, especially when the number of features may change during design. However, for irregular layouts, placing features individually may offer more control. How do you handle repeated features in your 3D models? Do you prefer arrays or manual placement, and why?

SLW210, thanks for retesting and posting the exact messages. The two cases need to be kept separate: The triangle-limit/non-finite-coordinate message concerns the mesh data, rather than just the compressed file size. That message alone doesn't tell us which condition your 7.5 MB file hit. The temporary-capacity message concerns available processing capacity; it doesn't establish that the model itself is invalid. I can't confirm that your original files now work. If either error still occurs, could you let us know which one, your browser/version and roughly when it happened? Please don't post a confidential model here. If you want to provide reproduction details privately, the support address is support@cadprops.com. For context, CADProps reads core 3MF mesh geometry. Manufacturing extensions aren't interpreted, and mesh properties are approximate. Files are processed on the server, so please only upload models you're permitted to share with the service. Disclosure: this is a CADProps team reply, written with AI assistance. Current documentation: 3MF scope and limits

Just a reminder: the early-bird discount for PRO ends on October 31st. What capabilities will be unlocked by upgrading to PRO? (FREE is already sufficient for most users; PRO is designed for those with more advanced needs.) 1. Update the asset version of a published VCID without changing the VCID itself. 2. Configurable donation links, such as PayPal. 3. Both ARX and DLL, two advanced plugin formats, are supported, and the maximum file size has been increased from 3MB to 15 MB. 4. PRO is the minimum requirement for mounting and joining the VedaCAD-based General contracting and subcontracting network ark visa. Early bird event details: https://www.vedacad.com/journal?post=the-pioneer-challenge

an AI translation (defun c:ldoit ( / ss i ent dxf x1 x2 rot normal dirVec vAxis projDist newX2 ) ;; 1. Select only DIMENSION objects (setq ss (ssget '((0 . "DIMENSION")))) (if ss (progn ;; Iterate backwards through the selection set (repeat (setq i (sslength ss)) (setq i (1- i)) (setq ent (ssname ss i)) (setq dxf (entget ent)) ;; Ensure it is specifically a Rotated/Linear dimension (if (member '(100 . "AcDbRotatedDimension") dxf) (progn ;; 2. Corrected DXF Codes: 13 maps to xLine1Point, 14 maps to xLine2Point (setq x1 (cdr (assoc 13 dxf))) ; xLine1Point (Defpoint 1) (setq x2 (cdr (assoc 14 dxf))) ; xLine2Point (Defpoint 2) (setq rot (cdr (assoc 50 dxf))) ; Rotation angle (in radians) (setq normal (cdr (assoc 210 dxf))) ; Normal Vector ;; 3. Compute direction vector based on rotation angle (setq dirVec (list (cos rot) (sin rot) 0.0)) ;; 4. Vector subtraction: vAxis = x2 - x1 (setq vAxis (mapcar '- x2 x1)) ;; 5. Dot Product: vAxis . dirVec (setq projDist (+ (* (car vAxis) (car dirVec)) (* (cadr vAxis) (cadr dirVec)) (* (caddr vAxis) (caddr dirVec)))) ;; 6. Calculate new X2 point: x1 + (dirVec * projDist) (setq newX2 (list (+ (car x1) (* (car dirVec) projDist)) (+ (cadr x1) (* (cadr dirVec) projDist)) (+ (caddr x1) (* (caddr dirVec) projDist)))) ;; 7. Replace the old DXF 14 (xLine2Point) with the calculated coordinates (setq dxf (subst (cons 14 newX2) (assoc 14 dxf) dxf)) ;; 8. Update and refresh the entity in the CAD database (entmod dxf) (entupd ent) ) ) ) ) ) (princ) )

If you can work with vectors, all you need is the dotProduct @Ap.Command() def doit(): ps, ss = Ed.Editor.select([(0, "DIMENSION")]) if ps != Ed.PromptStatus.eOk: return for id in ss.objectIds(Db.RotatedDimension.desc()): rotdim = Db.RotatedDimension(id, Db.OpenMode.kForWrite) x1 = rotdim.xLine1Point() x2 = rotdim.xLine2Point() dir_vec = Ge.Vector3d.kXAxis.rotateBy(rotdim.rotation(), rotdim.normal()) v_axis = x2 - x1 proj_dist = v_axis.dotProduct(dir_vec) rotdim.setXLine2Point(x1 + (dir_vec * proj_dist))

We had our notes originally in word so it would put a paragraph number in it automatically. We pasted that word doc into CAD the advantage was if a paragraph was removed it would renumber the notes. I have used a True type font to put numbers in a circle. May see if can find a hexagon one. Ok we had a multiple font add on that you typed "a" and a stop sign appeared it was a Font where each character representing a road sign had been made. I have previously looked at a "Make TTF's" So you could make hexagons with a number. This is 1234567890 Part two a edited mtext of two fonts. Had a play in word and sort of got something, Will see if there is a TTF out there. This was a manual edit of a mtext, Changed 1 2 3 4 so its doable. I did search for "hexagon TTF with numbers inside" and yes found a couple of answers. You may be able to use a SHX file will look into that also.

So the blocks are easy to make with an attribute for the number. Have the attribute with a default value such as '.' If you have one block entered with the attribute competed, this should allow you to increment the others - you need to select the first block attribute to get the value needed and then hit each other attribute in turn to add the next number. Try this LISP for incremental numbering - a part of something much larger so perhaps it isn't as nice as it could be but it works. This should also work for lettering (A -> B, and 1A ->1B, A1 ->A2) Then just have to split the mtext into parts I think - Lee Macs string to list can do part of this - just making a note in case I get time tomorrow to do that for you. Suspect you will need 2 LISPS, the one below to number the block attributes and one to split the text. (defun c:ctx+ ( / increment sel ) ;;Sub Functions (defun LM:roundm ( n m ) ;;http://www.lee-mac.com/round.html (* m (atoi (rtos (/ n (float m)) 2 0))) ) (defun uprev (base sel increments / ent entlst currentrevision revlength revisionprefix anumber ones leadingzero revcode revletter revnumber leadingzeros RL) ;;Sub routines (defun itsnotadate ( increments revlength entlst currentrevision base revisionprefix anumber / currentrevision revlength revisionprefix anumber ones leadingzero revcode revletter) (if (or (= (rtos (atof currentrevision)) currentrevision) (= (type currentrevision) 'INT) ) ; endor (progn (if (= (type currentrevision) 'STR) (setq revletter (+ (ato

@dber From your post, I understood that you want to number construction detail notes from an existing MTEXT object. I put together two versions so you can try both and choose whichever suits your workflow: - Loose geometry: separate hexagon outlines, solid fills and text numbers. - Block with attribute: each marker is a block with an editable number attribute. Both versions read manual paragraph breaks in the MTEXT. Wrapped lines remain part of the same numbered paragraph, and empty paragraphs are skipped. Each hexagon is sized proportionally to the text and centered vertically beside its paragraph. Commands: - HENL / HENB: add markers beside the existing MTEXT without moving or splitting it. - HENLC / HENBC: create separate numbered paragraphs at a location you pick, with the option to keep or delete the original. You can load both files together—their commands are different. These versions are intended for single-column, non-annotative MTEXT without fields. Give them a try and let me know how they work for your example. Code below. ;;; HEXENUM 1.2 - Loose geometry | AutoCAD Windows / Visual LISP ;;; HENL / HEXENUML: number the existing MTEXT in place. ;;; HENLC / HEXENUMLC: create separate paragraphs at a picked location. ;;; Hexagon side = 1.8 x nominal text height; SOLID fill = ACI 255. ;;; Both editions can be loaded together; command and helper names are isolated. (vl-load-com) (defun R0:HENL-Fail (msg) (setq henl-msg msg) (exit)) (defun R0:HENL-Prefix (frames / result