All Activity

That's an Image, not a drawing. But since you want guesses only, my WAG is the direction of whatever object you are using for the 'curve path".

IIRC, I have just frozen all layers (or use LAYISO is usually easier) except what I need or even create a couple of new layers and only have those on. You can also try tweaking the scale, angle, etc.

Best way to troubleshoot an issue in general is to watch the commandline and history, or in my case, the Text Window. I keep as much screen as possible when working on something, so no commandline ever. Dual screens I can have the Text Window open on the other monitor. Also, Properties can be opened with a Right-Click, so need need for that always on screen, mine is always docked. Is this question about 3D modelling only or just in general? If it's a geometry issue a close inspection usually can detect that if nothing shows in the commandline history. For 3D SECTIONPLANE can check for issues. LIST is handy in some cases, I sometimes use it for LISP uses, but I have various DUMP LISPs too, those can also help detect some issues. If it is a drawing I started, there usually should be no issues with geometry, like open gaps where you expect closed shapes, etc. so exactly what specific issues are you thinking of? LIST is probably behind a look at the Text Window and history, Properties, and a quick glance. But I usually use LIST for a way to quickly copy and paste that information and/or for double checking LISP results et. al.

This group already has 30+ members, welcome all developers, CAD managers, and users to join for CAD usage, technical discussions, development, and plugin sharing.

'Appload' and Startup suit is in the bottom right corner... in AutoCAD.... Must be AutoLoad in BricsCAD

@BIGAL I'm awre of APPLOAD... that's why I asked @Steven P what did it means - is it the use of APPLOAD or other way?

Just type Appload in Bricscad, you will ser the "Load Application Files" click on "Autoload" and the lisp entry will be loaded on startup.

That makes sense! Keeping Properties open is definitely more convenient when checking and changing values repeatedly. I guess LIST is still useful when you want a quick text-based report of an entity, but Properties is more practical for everyday editing.

@Steven P what do you mean by "startup suit"?

FYI, I used to run the LIST command quite a bit to give me information about the object(s) in question. But with the introduction of the Properties command in AutoCAD 2000, I slowly got used to leaving the Properties window opened/docked in the drawing area. Then as an object is selected, it's "properties" would automatically be filled out for me to inspect inside the Properties window. There's no need to run an extra command sequence like the LIST command which then would have to display the information on on a separate Text screen. In addition, the Properties window makes it possible for you to enter new values into those property items that can be modified.

Just thought of another trick I've used in the past. I would let AutoCAD create a brand new outline of the area to be hatched for me with the Boundary command. But in the Boundary Creation window under Boundary set, do not use the default Current viewport setting. But instead click on the New button and then select only the objects that form the hatch area outline. This restricts AutoCAD to only consider those objects selected to generate the new boundary. Leave the Object type as Polyline and usually with this new Pline boundary generated, the Hatch creation completion success rate would increase just a tad more.

The LIST command is useful when I need to inspect an entity’s properties, such as its coordinates, length, radius, or object type. It can help when a drawing looks correct but I need to verify the actual geometry. However, one limitation is that LIST reports geometric data rather than explaining why an operation failed. For example, if a 3D Boolean operation fails, the LIST output alone may not reveal whether the problem is caused by intersecting geometry, invalid solids, or another modeling issue. When troubleshooting a difficult 3D modeling problem, how far do you rely on LIST before switching to other inspection methods?

Good point. Using the object option can simplify things when the existing geometry already defines a usable boundary.

That’s a smart workaround, especially when you’re up against a deadline! Using a polyline on a nonplotting layer seems much easier than trying to fix every tiny gap in the original boundary.

Breaking a complicated area into smaller sections makes sense, especially when only part of the boundary is causing trouble. Mirroring a hatch across a symmetrical part is also a useful workaround I’ll keep in mind.

Interesting point about different hatch patterns behaving differently with the same boundary. I hadn’t considered that moving the geometry or changing the pattern could sometimes help. It shows that the issue isn't always just the boundary itself.

Green line should follow white curve path instead the duplicating lines are offsetting in opposite direction of curve

After launching VedaCAD and talking with several developers here, I noticed a universal architectural bottleneck we all face in the CAD industry: 99.9% of our custom plugins are strictly local and tightly coupled. Traditionally, if you build a tool that relies on specific external data—like a slide library (.SLB), a steel shape parameter table (.CSV), or a layer standard dictionary (.INI)—you hardcode that data into the .LSP or compile it directly into the .VLX. When a profile dimension changes or a new standard block is added, you have to modify the source code, recompile, and email a new ZIP file to everyone. This rigid "Logic + Data" coupling inevitably leads to a version fragmentation nightmare across an office. The obvious solution is to fetch data from a cloud API on the fly. But as we all know, writing WinHttp requests in AutoLISP is incredibly fragile. Because AutoLISP is single-threaded, waiting for a network response usually freezes the AutoCAD UI—a terrible user experience. The "Pseudo-Cloud" Architecture I realized that with VedaCAD acting as the underlying infrastructure, we can achieve true "Cloud-Native" behavior without writing any network code in LISP, simply by decoupling Logic from Data. Because VedaCAD handles the secure transmission and silent hot-swapping of physical files in the background, you can build tools like this: The Logic (Asset A): You publish your core .LSP plugin. The Data (Asset B): You publish your external data file (e.g., Shapes.csv, Blocks.slb, or Standards.ini). Instead of making risky network calls, your LISP simply reads the local data file from the isolated VedaCAD sandbox directory. To locate the data file dynamically, you can use these two lines of code (AutoCAD example): ;; Find the isolated VedaCAD Plugins and Assets sandbox paths dynamically (setq vc_plugins_path (strcat (getenv "APPDATA") "\\VedaCAD\\AutoCAD_R" (substr (getvar "ACADVER") 1 2) "\\Plugins\\")) (setq vc_assets_path (strcat (getenv "APPDATA") "\\VedaCAD\\AutoCAD_R" (substr (getvar "ACADVER") 1 2) "\\Assets\\")) How the Sync Loop Works (The Magic) Because AutoLISP releases the file handle as soon as you (close) the file, the data is never locked. When the data needs to change, the developer (requires a PRO account to unlock the push-update feature) simply updates the Shapes.csv or Blocks.slb file in their VedaCAD Client. Here is what happens on the users' end globally: For PRO Users: VedaCAD's background engine (24h heartbeat cycle) detects the version drift and silently hot-swaps the data file in the background. The next time the user runs your command, the LISP reads the new datasets instantly. For FREE Users: The engine (72h heartbeat cycle) receives the update beacon. It won't annoy them with popups, but an "Update" card will silently appear in their VedaCAD panel, allowing them to pull the latest data with one click. 5 Wild Possibilities with this Architecture: By relying on VedaCAD to handle the file delivery and background syncing, developers can breathe new life into traditional CAD formats: The "Live" Visual Block Library (.SLB / .DWG): You have a custom DCL with image tiles (slide_name) for inserting standard doors or mechanical parts. By separating the .SLB file, when the company introduces 5 new part models, the admin just pushes a new .SLB and .CSV index. Everyone's visual menu updates automatically the next time they open the dialog, without touching the core LISP. Dynamic Engineering Parameter Sets (.CSV / .XML): A structural plugin that draws H-beams or piping based on manufacturer catalogs. If the manufacturer updates their standard sizes, you just push a new .CSV. The plugin remains lightweight and eternally accurate. Auto-Updating Drafting Standards (.INI / .JSON): A "CAD Checker" routine that reads a dynamic .ini file mapping Layer Name -> Color -> Linetype. As the BIM Manager evolves the company standards, the ruleset updates silently across the fleet. The checker script always enforces the latest rules. Live Quoting / Pricing Engines: A cost-estimation LISP that reads a Prices.csv file to calculate the bill of materials (BOM). The CAD Manager updates the material costs quietly in the background each month. Remote Feature Toggles & Team Kanban: You publish a simple Config.ini. Change ENABLE_BETA=1 to unlock experimental features for your users, or add NOTICE="Server maintenance this weekend", which your LISP prints to the command line upon loading. You can even use a Tasks.txt that pops up a DCL dialog showing the team's drawing assignments for the day. We built VedaCAD to be an invisible infrastructure so that you guys can focus purely on solving engineering problems rather than fighting network protocols, UI freezes, and file locks. Has anyone else experimented with decoupling data from their LISP routines to mimic a cloud architecture? I’d love to hear your thoughts and see what else we could build with this!

@BIGAL Appreciate the thought! I actually went down that exact rabbit hole during early R&D. We deliberately decided against dynamic CUI generation because messing with AutoCAD's menu tree on the fly is a notorious recipe for workspace corruption across different releases. We'd much rather keep VedaCAD strictly as an unbreakable, lightweight delivery pipe (like npm) and leave the bespoke UI craft in the hands of creators like you and Paul! --- @Steven P Definitely not! The VCID is strictly a one-time install code (like an Amazon tracking number). Once installed, you simply type your normal LISP command name in the command line as usual(or the custom shortcut keys you have configured)—zero VCID to memorize!

@Steven P yes email a lsp and a ZIP file, with all the other stuff MNU CUIX lisp's dwg's dwt's etc. If using a server based solution then don't need a ZIP. One thing I did look at was making a custom CUI & CUIX file, they are xml files the later zipped and named CUIX. As mentioned before copy a CUIX rename to zip and have a look inside. Was looking at using Excel to write the menu then convert to XML code -> CUI, CUIX. For a custom mnu just need to work out how to write the XML code. Avoiding the CUI command. @VicoWang maybe have a look at making a CUI would be very helpful.

A lot of times if you use the object option it does better. When I get back to work, I'll see how many old threads are around on hatch and boundary issues.

Some times with very odd shaped boundaries AutoCAD just has a hard time filling it with any hatch pattern. That's when I would break the single hatch area up into different area sections. The boundary would be drawn using a PLINE and placed onto a non-plot layer. This usually resolves the issue. Another solution that worked for me involves odd shaped boundaries that are symmetrical. The hatch area when broken up in half hatches perfectly on the left side but refuse to hatch properly on the right. So I would just create the hatch pattern on the side that works and then mirrored that to the other side.

AutoCAD is terrible at hatching in several ways, that at least usually is reported by BricsCAD users to do better with the same shape(s). Several threads here and other forums of quirks for this and that on hatching. On another forum, someone posted a spline shape that didn't hatch correctly, though I was able to "FIX" it by offsetting it (with delete option) and then offset it back where it was also with delete option), it also worked fine originally with several hatch patterns and failed on a few others, it also had no issues in BricsCAD reportedly. Sometimes zooming in or zooming out and/or moving closer to 0,0,0 works. Sometimes just using a slightly different pattern works better. I mostly use Solid, Gradient, Steel, Aluminum, et. al. made of straight lines and usually they work better in most instances, seldom do I need Earth, Gravel, Sand, etc. which seems to be the type to have issues.

It would still be needing manual tweaking or if by LISP still more coding. As I mentioned above I fixed the sizing portion of the original LISP for lines, I will post that version if getting CENTERMARKS automatically placed is too much for me. I think I actually made one once, it's not a bad idea for most and probably, better than the old manual method. I just never understood why you would have a center crosshair or mark or whatever and it not allow associativity. That's the place where you would dimension a feature with a radius. P.S. for @BIGAL and other Aussies, my grandkids are headed back to the States, leaving today getting back Wednesday evening Eastern USA Time. They had a lot of fun and enjoyed Australia, at least what they saw of it. I may have to head over sometime.

Yes, I already mentioned that. Easy enough to place them manually, but replacing the dimrad/dimdia marks are not as easy as I was hoping, or I am going about it wrong. I set the Layer I create Centermark to Bylayer and the CENTERMARK layer on that with CENTERLTYPE to ByLayer and that issue is fixed. CENTERLTYPEFILE, I think I have a way to detect Metric and change that to acadiso.lin, so that's solved. I have to get it to find the object, since CENTERMARK works by getting the Circle or Arc object. I am thinking about just turning off the Dimrad/Dimdia Mark/Line and placing a CENTERMARK on all circles and arcs in current space or entire drawing, though that would have concentric objects with more than one, so I have to still sort for the largest for correct size. I have the original using lines working better and properly sizing automatically now, but still tweaking, I am leaving the crosshair lines option for older AutoCAD and CAD's that don't have CENTERMARK option.