Autodesk Developer Blog

Innovate. Integrate. Automate

Using AutoCAD MEP Object Enablers in AcCoreConsole

—

by

Jeremy Tammik
in ,

By

Jeremy

Tammik.

Question:
Using AcCoreConsole I’d like to move an object via AcCoreConsole.

The object type in question happens to be an AutoCAD MEP MVBlock.

Is this possible?

Would AcCoreConsole recognise the object as valid or would it be a zombie, i.e. a proxy object?

Answer:
I checked with the development team and received several confirmations saying that this should work:

AcCoreConsole does recognise MVBlock, and the object can be moved in the same way as in AutoCAD.

The AutoCAD MEP object enablers get loaded on demand in AcCoreConsole.exe.

Here is a test suite proving it:

  1. accoreconsole.exe: Just run accoreconsole.exe, following modules were loaded. Please note AEC modules are not loaded:

AcCoreConsole Object Enablers

  1. accoreconsole.exe /i oneBox.dwg: Open a dwg with only one box. A few more AutoCAD modules get loaded, but no AEC modules:

AcCoreConsole Object Enablers

  1. accoreconsole.exe /i oneWall.dwg: Open a dwg with only one wall. AEC modules are loaded. Also note that AECB modules are loaded, even though there are no MEP objects in the DWG:

AcCoreConsole Object Enablers

Following is the output of list command:

AcCoreConsole Object Enablers

  1. accoreconsole.exe /i oneDuct.dwg: Open a dwg with only one duct. AEC and AECB module are loaded:

AcCoreConsole Object Enablers

Following is the output of list command:

AcCoreConsole Object Enablers

I hope this helps.

Comments

6 responses to “Using AutoCAD MEP Object Enablers in AcCoreConsole”

  1. Mike Hutchinson Avatar
    Mike Hutchinson

    I tried this on two machines… both with AutoCAD MEP 2014. One machine didn’t recognize the mvBlock. The other one did. I checked DemandLoad variable… and believe this was the issue. I will test this.

    Reply
  2. Mike Hutchinson Avatar
    Mike Hutchinson

    I think I found the issue… DEMANDLOAD was set to 1. According to help though.. a setting of 1 should have helped.

    Reply
  3. Mike Hutchinson Avatar
    Mike Hutchinson

    Alas… DEMANDLOAD 3 does not help. Does DEMANDLOAD have to be set before the drawing is loaded? It must be something with the profile?

    Reply
  4. Balaji Avatar
    Balaji

    Hi Mike,
    DEMANDLOAD set to 3 should be good enough for it to load the object enablers. But I will need to investigate this a little further. I am looking into this and will get back to you.
    Regards,
    Balaji

    Reply
  5. Jeremy Tammik Avatar
    Jeremy Tammik

    Hi Balaji,
    Thank you! I will add the final result to the main blog post above once we know.
    Cheer, Jeremy.

    Reply
  6. Balaji Avatar
    Balaji

    Hi Mike,
    With DEMANDLOAD set to 3 (default) in AutoCAD MEP 2014, the core console did load the enablers in my system. The MVBlock ref could also be moved with the script that you shared.
    In the sample files that you shared, i find the /isolate switch being used. Can you try without that ?
    Also since you mentioned that the behavior was system specific, I would suggest comparing the LOADCTRLS value for the enablers under : HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\ObjectDBX\R19.1\Applications. Each dbx shoud have a LOADCTRL value with its first and fourth bit set for it load on proxy detection. The ObjectARX developer guide explains the relevance of each bit.
    Regards,
    Balaji

    Reply

Leave a Reply

Discover more from Autodesk Developer Blog

Subscribe now to keep reading and get access to the full archive.

Continue reading