topic Re: Boundary command not working correct on ACAD 2025 in ObjectARX Forum

Boundary command not working correct on ACAD 2025

Klemen.ozimek — Wed, 12 Jun 2024 11:49:27 GMT

Hello all,

It seems that BOUNDARY command is not working the same in ACAD 2025 as in the previous versions. Although elements for boundary set are selected, it also recognizes other elements (not selected) for boundary creation (on 2025).

(detected boundary after choosing the same options)

Does anyone know about is and is this related to something else (like some change in the settings,...)?

(view in My Videos)

Thanks in advance

Re: Boundary command not working correct on ACAD 2025

daniel_cadext — Wed, 12 Jun 2024 13:39:30 GMT

are vars PICKFIRST the same?

Re: Boundary command not working correct on ACAD 2025

Klemen.ozimek — Wed, 12 Jun 2024 14:51:45 GMT

PICKFIRST is the same (1).

It seems that it is working different from dialog window (BOUNDARY) and from command line (-BOUNDARY).

(view in My Videos)

Re: Boundary command not working correct on ACAD 2025

Klemen.ozimek — Fri, 14 Jun 2024 08:22:14 GMT

FYI. Found a workaround by using "-HATCH" command and creating boundary with that. Boundary set is then taken correctly and is working as with "BOUNDARY" (not "-BOUNDARY").

Re: Boundary command not working correct on ACAD 2025

wayne_warry — Thu, 30 Jan 2025 22:36:48 GMT

I am having the same issue with most of my drawings which were working fine with autocad 2022 now not working with 2025. However 1 drawing is still working but I can't find any differences,.

Re: Boundary command not working correct on ACAD 2025

Klemen.ozimek — Fri, 31 Jan 2025 09:25:54 GMT

This issue was submited to Autodesk support and will probably be fixed in the future.

"On further researching and testing on the drawing file, as well as reached out to my contacts on our Development Team and have determined that the behavior you have reported is in fact a defect.

I have raised a request to brief this issue to our developers and they will directly look into it and try to implement in the upcoming updates. Unfortunately, I can't really say when or how this might be adjusted though.

For your records, the defect number for this behavior is ACD-44172."