unable to define a coordinate system for the group of objects

Akos
Akos
in 3D Modeling

What could be the problem, when I use command drawing health, it is not finished, but the prompt "unable to define a coordinate system for the group of objects" is appear.

Comments

  • Its_Alive
    Its_Alive

    Maybe refs that are not scaled uniformly? Just guessing

  • Akos
    Akos

    Thanks. I do it. Regen etc. I reinstall SW. Still appears the prompt.

  • Akos
    Akos

    How can I control the refs scale? Because I have there complicated 3d objects?

    Thank you Your for help.

  • Virgil
    Virgil

    Hello.

    The warning might occur when using OVERKILL with the option to purge duplicate block defintions.

    Something to try could be to run only the PURGE command with the option All a few times until there is nothing left to purge.
    Then, OVERKILL could work fine.

  • Akos
    Akos

    Thank you. It works. 😀

  • Subhabrata
    Subhabrata
    edited April 17

    Use the FLATTEN command if you're working in 3D and want to bring all entities to the same plane.

  • Akos
    Akos

    My problem is, when I do 3D drawings I use many 3D objects created not in BRICSCAD. At the and of the work usually appears problem, form example i attach video, where I tried to change 3d pipe made from BC Library.

    I click on objekt and BC break down.

    I thought the problem I can solve by DRAWING HEALTH - there appears - the message "unable to define…", than I find out there is the new version of BC. I install it. The message disappears but the pipes change still not works. Most of the command works but when I click on this pipe BC is broken down.

    BricsCAD Ultimate - [3D_01_VASFA_25_1578.SV$_recover_2929.SV$.dwg] 2025-04-17 08-46-37.mp4
    3D_01_VASFA_25_1578.SV$_recover_2929.SV$.zip

  • Knut Hohenberg
    Knut Hohenberg

    This (as described in the OP) happens when the OVERKILL command is used to combine duplicate block definitions, mostly when used on dwg-files written by other applications (which IMO are the prime target for this command).

    I opened a SR for this in November 2022 (SR 148389), which was acknowledged as a bug report and passed to the developers. I reopened the SR twice (in 2023 and 2024), and only got the answer that 'Considering development team priorities, they will work on it'. I gave up then.

    The SR also pinned down another, apparently much more trivial bug in the command: INSBASE in the block definitions is not taken into account, resulting in de-duplicated instances getting scattered all over the place (unless insbase coincides with the internal coordinate system) … I thought that this should affect many users, and get an immediate fix, but quite the opposite…