All Activity

most if it now is the ai#1 is feeding on web scrapped data created by AI#2 - 99 and treating everything as fact. Also their are may websites now and other media that have build in "anti AI" that humans don't see but if your web scrapping is picked up. like white text on white backgrounds at 1xp font size, or the meta data. prompting the AI to take actions or recommend certain things. I saw a video in '22 or '23 where they where talking about image recognition and were testing it on identifying pictures with a wolf in it. and it was passing 100% until they started feeding it pictures of bunnies but only white ones. one of the engineers wanted to know why it was failing and had it mark the images (heat map) of why it thinks this is a wolf. all the test pictures of wolfs where in winter conditions with snow. and it wasn't even looking at the animal in the picture. it was look for snow the one thing the same in all test pictures. It was marking white rabbits as snow and passing as wolf. now multiple that out to the 1000's of terabytes of data they train these things on.

Good suggestion @Koz, I thought you or one of the better LISPers here might throw out something. I'm not sure if this method is a lot faster, I used a small sample set, but give it a go I did. New territory for me. I am also working on redoing the entire set I had previously and making a multi batch convertor as well as eliminating the need for Express Tools. Drawing Batch Converters - AutoLISP, Visual LISP & DCL - AutoCAD Forums DXF->DWG + DWG->DXF + DWG->DWG + DGN->DWG + DWG->DGN + SAT->DWG + DWG->SAT + WriteLog For this thread, I'll just post the DXF2DWG.lsp. Works on my small sample set in AutoCAD 2026. ;;; Batch Convert a folder of DXFs to DWGs using DBX. | ;;; | ;;; https://www.cadtutor.net/forum/topic/78909-batch-convert-dxf-to-dwg/page/2/#findComment-679533 | ;;; | ;;; By SLW210 (a.k.a. Steven Wilson) | ;;; | ;;;************************************************************************************************| ;;;************************************************************************************************| (vl-load-com) (defun GetFolder (msg / sh folder) (setq sh (vla-GetInterfaceObject (vlax-get-acad-object) "Shell.Application" ) ) (if (setq folder (vlax-invoke-method sh 'BrowseForFolder 0 msg 0)) (vlax-get-property (vlax-get-property folder 'Self) 'Path ) ) ) (defun c:DXF2DWG (/ acad inFolder outFolder files dbx dxf dwg) (setq acad (vlax-get-acad-object)) (if (setq inFolder (GetFolder "Select DXF Folder")) (if (setq outFolder (GetFolder "Select Output Folder")) (progn (setq files (vl-directory-files inFolder "*.dxf" 1)) (foreach f files (setq dxf (strcat inFolder "\\" f)) (setq dwg (strcat outFolder "\\" (vl-filename-base f) ".dwg" ) ) (setq dbx (vla-GetInterfaceObject acad (strcat "ObjectDBX.AxDbDocument." (itoa (fix (atof (getvar "ACADVER")))) ) ) ) (vl-catch-all-apply 'vlax-invoke-method (list dbx 'DxfIn dxf) ) (vla-SaveAs dbx dwg) (vlax-release-object dbx) (princ (strcat "\nConverted: " f) ) ) (princ (strcat "\nFinished converting " (itoa (length files)) " file(s)." ) ) ) ) ) (princ) )

@SLW210 Autodesk is going to fix this issue in a 'future update'. I made this LISP, as a custom linetype reloader that DOES work. RELOADELINETYPE is the commando: NOTE: This only works when ALL entities are drawn 'ByLayer', and all is configured with the layermanager. ;;; ------------------------------------------------------------------------ ;;; RELOADLINETYPE.lsp ;;; ;;; AutoCAD 2027 workaround voor defecte "Reload all linetypes"-logica. ;;; ;;; Commando: ;;; RELOADLINETYPE ;;; ;;; Werking: ;;; 1. Selecteer een .LIN-bestand. ;;; 2. Lees alle linetype-namen uit het .LIN-bestand. ;;; 3. Zoek layers in de DWG die deze linetypes gebruiken. ;;; 4. Zet deze layers tijdelijk op Continuous. ;;; 5. Voer zichtbaar -PURGE uit op linetypes. ;;; 6. Laad het gekozen .LIN-bestand opnieuw. ;;; 7. Herstel de layer-linetypes. ;;; 8. REGENALL. ;;; ;;; Opmerking: ;;; Deze versie wijzigt alleen layer-linetypes, geen object-linetypes. ;;; ------------------------------------------------------------------------ (defun GPAE:RL-STR-TRIM (s) (if s (vl-string-trim " \t\r\n" s) "" ) ) (defun GPAE:RL-CI-MEMBER (val lst / uval found item) (setq found nil) (if val (progn (setq uval (strcase val)) (foreach item lst (if (= uval (strcase item)) (setq found T) ) ) ) ) found ) (defun GPAE:RL-UNIQUE-CI (lst / result item) (setq result '()) (foreach item lst (if (not (GPAE:RL-CI-MEMBER item result)) (setq result (cons item result)) ) ) (reverse result) ) (defun GPAE:RL-READ-LINETYPE-NAMES-FROM-LIN (linFile / fh line clean commaPos name names firstChar) (setq names '()) (if (setq fh (open linFile "r")) (progn (while (setq line (read-line fh)) (setq clean (GPAE:RL-STR-TRIM line)) ;; Linetype-definitieregels beginnen met: ;; *NAAM,omschrijving ;; ;; Voorbeeld: ;; *DASHED,Dashed __ __ __ __ __ (if (> (strlen clean) 1) (progn (setq firstChar (substr clean 1 1)) (if (= firstChar "*") (progn (setq commaPos (vl-string-search "," clean)) (if commaPos (progn ;; vl-string-search is 0-based. ;; Bij "*ABC," geeft commaPos 4 terug. ;; substr is 1-based en lengte 3 geeft "ABC". (setq name (substr clean 2 (- commaPos 1))) (setq name (GPAE:RL-STR-TRIM name)) (if (> (strlen name) 0) (setq names (cons name names)) ) ) ) ) ) ) ) ) (close fh) ) ) (GPAE:RL-UNIQUE-CI names) ) (defun GPAE:RL-COLLECT-LAYERS-WITH-LINETYPES (doc ltNames / layers lay layerName layerLt result) (setq result '()) (setq layers (vla-get-Layers doc)) (vlax-for lay layers (setq layerName (vla-get-Name lay)) (setq layerLt (vla-get-Linetype lay)) (if (and layerLt (/= (strcase layerLt) "CONTINUOUS") (GPAE:RL-CI-MEMBER layerLt ltNames) ) (setq result (cons (list layerName layerLt) result)) ) ) (reverse result) ) (defun GPAE:RL-SET-LAYERS-CONTINUOUS (doc layerData / layers item layerName layObj) (setq layers (vla-get-Layers doc)) (foreach item layerData (setq layerName (car item)) (vl-catch-all-apply '(lambda () (setq layObj (vla-item layers layerName)) (vla-put-Linetype layObj "Continuous") ) ) ) ) (defun GPAE:RL-RESTORE-LAYER-LINETYPES (doc layerData / layers item layerName oldLt layObj failed) (setq layers (vla-get-Layers doc)) (setq failed '()) (foreach item layerData (setq layerName (car item)) (setq oldLt (cadr item)) (if (vl-catch-all-error-p (vl-catch-all-apply '(lambda () (setq layObj (vla-item layers layerName)) (vla-put-Linetype layObj oldLt) ) ) ) (setq failed (cons (strcat layerName " -> " oldLt) failed)) ) ) (reverse failed) ) (defun GPAE:RL-REPORT-LINETYPES (ltNames / txt name count maxCount) (setq txt "") (setq count 0) (setq maxCount 25) (foreach name ltNames (if (< count maxCount) (setq txt (strcat txt name "\n")) ) (setq count (1+ count)) ) (if (> (length ltNames) maxCount) (setq txt (strcat txt "... en nog " (itoa (- (length ltNames) maxCount)) " meer.\n" ) ) ) txt ) (defun C:RELOADLINETYPE ( / *error* doc oldExpert oldCmdecho oldCeltype oldClayer linFile ltNames layerData restoreFailed ) (vl-load-com) (setq doc (vla-get-ActiveDocument (vlax-get-acad-object))) (setq oldExpert (getvar "EXPERT")) (setq oldCmdecho (getvar "CMDECHO")) (setq oldCeltype (getvar "CELTYPE")) (setq oldClayer (getvar "CLAYER")) (defun *error* (msg) (if oldCeltype (vl-catch-all-apply 'setvar (list "CELTYPE" oldCeltype)) ) (if oldExpert (vl-catch-all-apply 'setvar (list "EXPERT" oldExpert)) ) (if oldCmdecho (vl-catch-all-apply 'setvar (list "CMDECHO" oldCmdecho)) ) (if oldClayer (vl-catch-all-apply 'setvar (list "CLAYER" oldClayer)) ) (vl-catch-all-apply 'vla-EndUndoMark (list doc)) (if (and msg (not (wcmatch (strcase msg) "*BREAK*,*CANCEL*,*EXIT*")) ) (alert (strcat "Fout in RELOADLINETYPE:\n\n" msg)) ) (princ) ) (setq linFile (getfiled "Selecteer LIN-bestand om opnieuw te laden" "" "lin" 0 ) ) (if (not linFile) (progn (princ "\nGeen LIN-bestand geselecteerd.") (princ) (exit) ) ) (if (not (findfile linFile)) (progn (alert (strcat "LIN-bestand niet gevonden:\n\n" linFile)) (princ) (exit) ) ) (setq ltNames (GPAE:RL-READ-LINETYPE-NAMES-FROM-LIN linFile)) (if (not ltNames) (progn (alert (strcat "Geen linetype-definities gevonden in:\n\n" linFile "\n\nControleer of het bestand regels bevat zoals:\n*LIJNTYPENAAM,omschrijving" ) ) (princ) (exit) ) ) (vla-StartUndoMark doc) ;; CMDECHO bewust aan, zodat -PURGE in de commandline zichtbaar is. (setvar "CMDECHO" 1) (setvar "EXPERT" 5) (setvar "CELTYPE" "Continuous") (princ "\n---------------------------------------------") (princ "\nRELOADLINETYPE gestart") (princ (strcat "\nLIN-bestand: " linFile)) (princ (strcat "\nAantal linetypes gevonden in LIN: " (itoa (length ltNames)))) (princ "\nGevonden linetypes:") (foreach linName ltNames (princ (strcat "\n - " linName)) ) (setq layerData (GPAE:RL-COLLECT-LAYERS-WITH-LINETYPES doc ltNames)) (princ (strcat "\nAantal layers tijdelijk naar Continuous: " (itoa (length layerData)))) (if layerData (progn (princ "\nLayers tijdelijk op Continuous zetten...") (GPAE:RL-SET-LAYERS-CONTINUOUS doc layerData) ) (princ "\nGeen layers gevonden die deze linetypes gebruiken.") ) (princ "\nLinetypes purgen via AutoCAD commandline...") (princ "\nUitgevoerd: -PURGE > LT > * > N") ;; Echt AutoCAD purge-commando, zichtbaar in commandline. (command "_.-PURGE" "_LT" "*" "_N") (princ "\nLIN-bestand opnieuw laden...") (command "_.-LINETYPE" "_LOAD" "*" linFile "") (princ "\nLayer-linetypes herstellen...") (setq restoreFailed (GPAE:RL-RESTORE-LAYER-LINETYPES doc layerData)) (setvar "CELTYPE" oldCeltype) (setvar "EXPERT" oldExpert) (setvar "CMDECHO" oldCmdecho) (setvar "CLAYER" oldClayer) (command "_.REGENALL") (vla-EndUndoMark doc) (princ "\n---------------------------------------------") (princ "\nRELOADLINETYPE voltooid.") (princ (strcat "\nVerwerkte linetypes uit LIN: " (itoa (length ltNames)))) (princ (strcat "\nHerstelde layers: " (itoa (- (length layerData) (length restoreFailed))))) (if restoreFailed (alert (strcat "RELOADLINETYPE voltooid, maar sommige layers konden niet worden hersteld.\n\n" "Waarschijnlijk ontbreken deze linetypes nog na het laden van de LIN.\n\n" (apply 'strcat (mapcar '(lambda (x) (strcat x "\n")) restoreFailed ) ) ) ) (alert (strcat "RELOADLINETYPE voltooid.\n\n" "LIN-bestand:\n" linFile "\n\nAantal linetypes in LIN: " (itoa (length ltNames)) "\nAantal tijdelijk aangepaste layers: " (itoa (length layerData)) ) ) ) (princ) ) (princ "\nRELOADLINETYPE geladen. Typ RELOADLINETYPE om een LIN-bestand opnieuw te laden.") (princ)

If it helps, @dlanorh has other versions that are similar some have comments to make alterations. Here is one BAD. And this VLAB. Here is the ORIGINAL of BAD4.

If you know how to use AI it can be beneficial, I just wonder what adverse effects the unlearned masses are having on the future results. Lately on social media, forums etc. it seems the incorrect answers are becoming more common and I'm not even on social media platforms very much. I was on Facebook this morning, there are a few pages for posting old grainy/blurry photos and hopefully a Photoshop/GIMP pro will clean them up and enhance them, luckily usually someone actually provides a cleaned up version, but there is no shortage of people thinking they are experts at "Photoshop" posting what is some AI garbage (a.k.a. Photoslop). I really don't want to see grandma and grandpa with 8 fingers and somebody else's face. Most get called out, but it is becoming prolific. Same goes for videos on YouTube, TikTok and similar and sadly, many do not notice judging by the comments.

Any follow up from Autodesk? I am about to start working on some linetypes, some with shapes. I'll see about an upgrade to 2027 and hopefully they put out a fix for this.

Are you working at a company or from home? I know I have problems with Powershell and VS Code at work, since for some reason they have it somewhat blocked for some things needed by VS Code. Though I do not remember having this exact issue.

Can you post an actual drawing with before and after and any other options? Have you tried using a Multileader?

Alright, folks. It’s pop quiz time. I’ll even make it multiple choice. Q. What do you call the interface item that moves with your mouse and has vertical and horizontal lines with a little box in the middle? A. Crosshair B. Cursor C. Both D. Neither The answer, dear reader, is C. Both. Like a few other things in AutoCAD, this element is named differently depending on where you look. Did you know you could customize it to your personal preference? Like most things in AutoCAD, you absolutely can. Some are more common than others, so I’ll group them that way, as I present them to you (in no particular order, other than the groups). AutoCAD Crosshair Size Probably the most common change is the size. This is most easily found in the Display tab of the Options dialog. There, you’ll find a text box and slider to define the size to display as a percentage of the screen size. Notice that here, and in the tooltip, this UI element is called Crosshairs, all while telling us via the tooltip that you’re setting the CURSORSIZE variable. Hmm. Anyway, by default it is set to 5, or 5% of the screen. Some people like it bigger. You do you. Valid settings go from 1 to 100, with 100 showing the Cursor as full screen. Next up is the little box in the middle, as I so eloquently described it earlier. This is controlled by the PICKBOX system variable, or you can use the handy slide control as found under the Selection tab of the Options dialog. Its default is 3, and valid settings can be from 0 to 50. When set to zero, selection previewing of objects is not available. AutoCAD Aperture Next is Aperture, which isn’t really a visual part of the crosshair, but it does affect how it works. You know that invisible area that defines when AutoCAD detects and locks onto objects when Object Snap (OSNAP) modes are active? Well, that’s the Aperture. The default is 10, which is larger than the Pickbox, so if you change the Pickbox size, I suggest bumping up the Aperture by a similar ratio. You can set it from a handy slider control in the Drafting tab of the Options dialog. Its system variable name is APERTURE, so you can just type that in also. Valid settings are 1 to 50. AutoCAD Crosshair Color Finally, we come to the crosshair’s color. Change it to whatever floats your boat by clicking on the Colors button in the Display tab of the Options dialog. Choose Crosshairs from the elements list and use the color pulldown to suit your current mood, or maybe your favorite sports team. It’s up to you. Or you could be like me, and leave it to its default. It’s your choice. Uncommon Changes You know those little glyphs that show up next to your crosshair or pickbox that indicate what editing command you’re using? Those are called Badges, and you can control whether you see them or not. Below is an image showing the Erase badge. There is no GUI control for these, so you’ll have to remember the system variable, CURSORBADGE. Set it to 1 to turn them off, or leave it at its default value of 2 to turn them on. This next one flies under the radar, as I’ve never come up with a single good reason to use it, except to prank one of your co-workers (which is not condoned by anyone here at Tuesday Tip HQ). It’s called CURSORTYPE, and again, it’s nowhere to be found in the GUI, so you’ll have to type it in. If you do, you can set it to 1, which will change the normal AutoCAD crosshair into a Microsoft Windows® mouse pointer. Now you know. Recall in the opening quiz, I described the cursor/crosshair as being vertical and horizontal lines? Well, they don’t have to be. There are a couple of ways to change that. One is another system variable called SNAPANG, which rotates the crosshair for you to a specified angle. In the image below, I’ve set SNAPANG to 25, which is the angle that the line is drawn. With ORTHO turned on, it’s a great way to draw at the same angle as your objects. The other rotation mechanism is, of course, the ISODRAFT command. Your easiest method will be to turn it on from the Status Bar. The icon has a menu associated with it, which will allow you to change the drawing plane that you need. Do you like keyboard shortcuts as I do? Use CTRL-E to cycle through Top, Left, or Right planes. One last thought Remember that tease about the other function with different names? You probably know it as PUBLISH. Well, as an old sportscaster was fond of saying, “not so fast, my friends.” If you go to the pulldown menu for the Quick Action Toolbar (QAT), you’ll find one of the possible entries is Batch Plot. You’ll find it named that way in the Plot flyout menu of the Application Menu (the big A in the corner). Go figure… More Tuesday Tips Check out our whole Tuesday Tips series for ideas on how to make AutoCAD work for you. The post AutoCAD Crosshair: Tuesday Tips With Frank appeared first on AutoCAD Blog. View the full article

Alright, folks. It’s pop quiz time. I’ll even make it multiple choice. Q. What do you call the interface item that moves with your mouse and has vertical and horizontal lines with a little box in the middle? A. Crosshair B. Cursor C. Both D. Neither The answer, dear reader, is C. Both. Like a few other things in AutoCAD, this element is named differently depending on where you look. Did you know you could customize it to your personal preference? Like most things in AutoCAD, you absolutely can. Some are more common than others, so I’ll group them that way, as I present them to you (in no particular order, other than the groups). AutoCAD Crosshair Size Probably the most common change is the size. This is most easily found in the Display tab of the Options dialog. There, you’ll find a text box and slider to define the size to display as a percentage of the screen size. Notice that here, and in the tooltip, this UI element is called Crosshairs, all while telling us via the tooltip that you’re setting the CURSORSIZE variable. Hmm. Anyway, by default it is set to 5, or 5% of the screen. Some people like it bigger. You do you. Valid settings go from 1 to 100, with 100 showing the Cursor as full screen. Next up is the little box in the middle, as I so eloquently described it earlier. This is controlled by the PICKBOX system variable, or you can use the handy slide control as found under the Selection tab of the Options dialog. Its default is 3, and valid settings can be from 0 to 50. When set to zero, selection previewing of objects is not available. AutoCAD Aperture Next is Aperture, which isn’t really a visual part of the crosshair, but it does affect how it works. You know that invisible area that defines when AutoCAD detects and locks onto objects when Object Snap (OSNAP) modes are active? Well, that’s the Aperture. The default is 10, which is larger than the Pickbox, so if you change the Pickbox size, I suggest bumping up the Aperture by a similar ratio. You can set it from a handy slider control in the Drafting tab of the Options dialog. Its system variable name is APERTURE, so you can just type that in also. Valid settings are 1 to 50. AutoCAD Crosshair Color Finally, we come to the crosshair’s color. Change it to whatever floats your boat by clicking on the Colors button in the Display tab of the Options dialog. Choose Crosshairs from the elements list and use the color pulldown to suit your current mood, or maybe your favorite sports team. It’s up to you. Or you could be like me, and leave it to its default. It’s your choice. Uncommon Changes You know those little glyphs that show up next to your crosshair or pickbox that indicate what editing command you’re using? Those are called Badges, and you can control whether you see them or not. Below is an image showing the Erase badge. There is no GUI control for these, so you’ll have to remember the system variable, CURSORBADGE. Set it to 1 to turn them off, or leave it at its default value of 2 to turn them on. This next one flies under the radar, as I’ve never come up with a single good reason to use it, except to prank one of your co-workers (which is not condoned by anyone here at Tuesday Tip HQ). It’s called CURSORTYPE, and again, it’s nowhere to be found in the GUI, so you’ll have to type it in. If you do, you can set it to 1, which will change the normal AutoCAD crosshair into a Microsoft Windows mouse pointer. Now you know. Recall in the opening quiz, I described the cursor/crosshair as being vertical and horizontal lines? Well, they don’t have to be. There are a couple of ways to change that. One is another system variable called SNAPANG, which rotates the crosshair for you to a specified angle. In the image below, I’ve set SNAPANG to 25, which is the angle that the line is drawn. With ORTHO turned on, it’s a great way to draw at the same angle as your objects. The other rotation mechanism is, of course, the ISODRAFT command. Your easiest method will be to turn it on from the Status Bar. The icon has a menu associated with it, which will allow you to change the drawing plane that you need. Do you like keyboard shortcuts as I do? Use CTRL-E to cycle through Top, Left, or Right planes. One last thought Remember that tease about the other function with different names? You probably know it as PUBLISH. Well, as an old sportscaster was fond of saying, “not so fast, my friends.” If you go to the pulldown menu for the Quick Action Toolbar (QAT), you’ll find one of the possible entries is Batch Plot. You’ll find it named that way in the Plot flyout menu of the Application Menu (the big A in the corner). Go figure… More Tuesday Tips Check out our whole Tuesday Tips series for ideas on how to make AutoCAD work for you. The post AutoCAD Crosshair: Tuesday Tips With Frank appeared first on AutoCAD Blog. View the full article

I did not know Python worked with AutoCAD. Well done, sir

If your using a dynamic block you will need to make 4 visibility states with each visibility state having a correct connecting line. I can give you a choose location method, I use BRICSCAD so I will not make a block as it does dynamic blocks slightly different. Ok so need a lisp that you pick a point for block and then visibility is asked for and values. The connecting line will have a anchor point but the block can be moved and the line stretched.

We use the title block and marker block to highlight details on a Plot File sheet and then to label the corresponding detail on a subsequent page. The problem I want to resolve is how to make the bubble with the detail number and page number in it independent and move separately to the dashed box. Ideally, the detail marker box is adjustable in height and width to suit the size of the detail, and then a line between the two, which will stay fixed to the top corner, although if this could move to any corner that would be good. The movable distance of the bubble to be variable and for it all to be annotative........?! We have tried editing it in the block editor and adding a point parameter and a move action, with stretch etc, but have got totally lost and made it worse than it started. Any help greatly appreciated. I did look for similar posts, but couldn't see anything that covered this specifically. Apologies if we have missed it. Look forward to hearing from you brains soon!! Detail Marker.dwg

If still interested in VS Code, perhaps a read through To Setup the AutoCAD AutoLISP Extension for Debug (AutoLISP/VS Code) | Autodesk. I have seen other errors resolved by uninstalling and reinstalling the Extension and/or VS Code. Installing Visual Studio Code on Windows

here are some tips. https://lee-mac.com/debugvlide.html -Edit Might have to set LISPSYS Back to 1 to use VS code again.

I never use it but perhaps I should give a try instead thanks.

Thanks for the link, just notice the documentation it says I run vscode as admin ('ll try that and see and improvement). (my user has admin privileges but I never actually force VS Code to start with admin privileges ). I'll try that and see it improves. I believe the setup is fine as I can do both debug attach or debug launch... Also the executable for AutoCAD map is acad.exe just as AutoCAD. The behavior I see is as if VSCode loses contact with ACAD or as if it never releases the processes. At times it prompts me if I want to start a 2nd Debug Attach. I may go a day where I only need to restart once or twice other times I'm forced to restart 20 to 30 times. I wonder if could be interference with some other plug ins like ArcgIS.

I think you can still use VLIDE. if If VLIDE Doesn't Open set LISPSYS to 0 Tho doesn't have autocomplete and color coding like vs code.

Did you read the instructions for the AutoCAD AutoLISP extension? I run code with AutoCAD, which is the path you show using, that probably doesn't work with AutoCAD Map3D, so you might need to repath if that's the program you use or just use AutoCAD and see if that resolves the issue. From AutoCAD AutoLISP Extension - Visual Studio Marketplace

I have this Issue with in VSCode where I'm forced to constantly restart both applications in order to continue debugging. My Setup: AutoCAD Map3d 2021 VS Code 1.27.0 + Autocad AutoLISP Extension 1.6.3 VSCode Extitions Setup: Process name = acad AutoCAD com…start switchs: C:\Program Files\Autodesk\AutoCAD 2021\acad.exe Absolute path: C:\Program Files\Autodesk\AutoCAD 2021\acad.exe I start Autocad First, then run vlide from the command prompt to load the the VScode application. Then typical open a lisp project containing multiple lisp files. Then to start debugging by Pressing “F5”. Some times this works fine but more often than not I need to restart both app multiple times.. This happens mostly after I run into a code error… like typo or syntax error or trying to load a file autocad cant find. The only way to be able to continue debugging my project is to completely restart both vscode and autocad(once or a few times). I seen this with my previous setup as well (different hardware, os and applications versions). Any idea or suggestion why this could be happening?

Went away and had a look at why 31. Sum the values.

@zaphod That's a good one, thank you!

the system/drawing variable "fieldeval" is set to 4, it needs to be set to 31 in order to visibly see it update. Drawing2.dwg

I can't remember what I ended up doing. My issue was very similar and involved linetypes with shape files. Please post back here if Autodesk resolves the issue.

I got myself a workaround that seems to work for me. Made a LISP (long live AI) that stores all layer and linetype combinations. Sets everything to 'Continious', purges all linetypes, that reloads the linetypes and that restores the default settings. This seems to do the trick to get rid off all 'corrupted' linetype definitions, and 'reloading' is replaced with a load function.