Commands that “work” in the AutoCAD 2013 Core Console

After seeing the feedback regarding this interesting feature in AutoCAD 2013, I decided to do a little detective work to establish which commands could be called from inside the AutoCAD 2013 Core Console. I hope this proves to be of use to at least some of the many people I expect to take advantage of this tool.

Before I go into the details on generating the list – and then look at the list itself – it's worth mentioning some additional background regarding this feature. I certainly see the Core Console as being extremely useful to many people, but it didn't necessarily start life as a headline feature for the 2013 release. It was made possible by the Big Split, and proved to be a good, early way to test out the capabilities of AcCore.dll, but it only became part of the product later in the product cycle. It's been used to implement at least one core feature inside AutoCAD 2013 – and I can certainly see it as being used much more extensively, over time – but this is a tool that has not yet benefited from much documentation investment (for instance). And – as we'll see later on – there are even some areas you just want to avoid: our test suite includes various commands to ensure our internal developers don't break important Core Console functionality, but there are full AutoCAD commands that currently prove problematic when executed from within the Core Console.

Generating the list was an interesting process: I started by implementing a core .NET module that read in the commands to test from a file (for AutoCAD OEM we maintain a list of AutoCAD commands in a file called OEMCMDS.txt, which I borrowed for this process). This module then queued up each command using SendStringToExecute() and fired off a simple AutoLISP function right after to check whether the command was active via CMDNAMES (or whether it was a sysvar – these are also included in the list) before cancelling the command (if it was still running) via an escape character. The LISP function wrote the name of the command or sysvar to the relevant file (for known or unknown commands). I also piped the output of the Core Console execution off to another text file, to help cross-check any issues.

This worked well enough, but didn't show whether commands that succeeded and returned without any user input worked or not (it assumed they did not, as they were no longer active). So I went back to the drawing board and attached some event handlers from C# to watch for commands that started and those that weren't found. These ended up proving much more reliable for commands, but less reliable for system variables.

Speaking of system variables: these have apparently not been stripped out of the Core Console, but many of the commands (and internal code) that use them won't be available, so please adjust your expectations accordingly.

Here's the C# code I used to generate the command lists:

using Autodesk.AutoCAD.ApplicationServices.Core;

using Autodesk.AutoCAD.ApplicationServices;

using Autodesk.AutoCAD.EditorInput;

using Autodesk.AutoCAD.Runtime;

using System.Collections.Generic;

using System.IO;

using System.Linq;

 

namespace TestCommandsForCoreConsole

{

  public class Commands

  {

    // Lists to be populated by our events

 

    List<string> _found = null;

    List<string> _notFound = null;

 

    // Command to test the various commands in the console

 

    [CommandMethod("TCS")]

    public void TestCommands()

    {

      Document doc =

        Application.DocumentManager.MdiActiveDocument;

      Editor ed = doc.Editor;

 

      // Create or clear our command lists

 

      if (_found == null)

        _found = new List<string>();

      else

        _found.Clear();

 

      if (_notFound == null)

        _notFound = new List<string>();

      else

        _notFound.Clear();

 

      // Attach our event handlers

 

      doc.UnknownCommand +=

        new UnknownCommandEventHandler(OnUnknownCommand);

      doc.CommandWillStart +=

        new CommandEventHandler(OnCommandWillStart);

 

      // Read in the list of commands to execute

 

      var values =

        from l in File.ReadAllLines(

          "c:\\users\\walmslk\\desktop\\OEMCMDS.TXT"

        )

        let cols = l.Split(new[] { ';' })

        select new { Command = cols.First() };

 

      foreach (var obj in values)

      {

        doc.SendStringToExecute(

          obj.Command + " \x1B", false, true, true

        );

      }

 

      // Dump our collected commands out to text files

 

      doc.SendStringToExecute("DUMPCMDS ", false, true, true);

    }

 

    void OnCommandWillStart(object sender, CommandEventArgs e)

    {

      string cmd = e.GlobalCommandName;

 

      if (!_found.Contains(cmd) &&

           (cmd != "SETVAR" || cmd != "DUMPCMDS")

         )

      {

        _found.Add(cmd);

        if (_notFound.Contains(cmd))

          _notFound.Remove(cmd);

      }

    }

 

    void OnUnknownCommand(object sender, UnknownCommandEventArgs e)

    {

      string cmd = e.GlobalCommandName;

 

      if (!_notFound.Contains(cmd))

        _notFound.Add(cmd);

    }

 

    void WriteCommands(List<string> cmds, string answer)

    {

      StreamWriter sw =

        new StreamWriter(

          "c:\\users\\walmslk\\desktop\\events-" + answer + ".txt"

        );

      using (sw)

      {

        foreach (string cmd in cmds)

        {

          sw.WriteLine(cmd);

        }

        sw.Close();

      }

    }

 

    [CommandMethod("DUMPCMDS")]

    public void DumpCommands()

    {

      _found.Sort();

      _notFound.Sort();

 

      WriteCommands(_found, "yes");

      WriteCommands(_notFound, "no");

 

      Document doc =

        Application.DocumentManager.MdiActiveDocument;

      Editor ed = doc.Editor;

 

      doc.UnknownCommand -=

        new UnknownCommandEventHandler(OnUnknownCommand);

      doc.CommandWillStart -=

        new CommandEventHandler(OnCommandWillStart);

 

      ed.WriteMessage(

        "\nFound a total of {0} commands, didn't find {1} others.",

        _found.Count, _notFound.Count

      );

    }

  }

}

Here's a list of the 573 commands I found to be available in the Core Console (and here they are as a text file):

?, +CONSTRAINTSETTINGS, +PUBLISH, +SAVEAS, +UCSMAN, +VPORTS, 3DALIGN, 3DCLIP, -3DCONFIG, 3DCONFIG, 3DCORBIT, 3DDISTANCE, 3DDWF, 3DDWFPUBLISH, 3DEDITBAR, 3DFACE, 3DFLY, 3DFORBIT, 3DMESH, 3DMOVE, 3DORBIT, 3DORBITCTR, 3DORBITTRANSPARENT, -3DOSNAP, 3DOSNAP, 3DPAN, 3DPAN2, 3DPANTRANSPARENT, 3DPOLY, 3DROTATE, 3DSCALE, 3DSWIVEL, 3DSWIVELTRANSPARENT, 3DWALK, 3DZOOM, 3DZOOM2, 3DZOOMTRANSPARENT, ABOUT, ACADWBLOCKDIALOG, ACGZDRAGACTION, ACISIN, ACISOUT, ACTMDRAGACTION, ACUCSEDITACTION, ADDSELECTED, AECDISPLAYMANAGERCONFIGSSELECTION, -AECDWGUNITS, -AECEXPORTTOAUTOCAD, AECFILEOPENMESSAGE, AECFILESAVEMESSAGE, AECOBJECTCOPYMESSAGE, AECOBJRELDUMP, AECOBJRELSHOW, AECOBJRELUPDATE, AECPOSTDXFINFIX, AECSETXREFCONFIG, AECVERSION, AI_EMPTYPRINC, AI_MOLC, AI_VIEWPORTS_ALERT, AIDIMFLIPARROW, AIDIMPREC, AIDIMSTYLE, AIDIMTEXTMOVE, AIMLEADEREDITADD, AIMLEADEREDITREMOVE, AIOBJECTSCALEADD, AIOBJECTSCALEREMOVE, ALIGN, ALLPLAY, AMECONVERT, ANNORESET, ANNOUPDATE, APERTURE, ARC, AREA, -ARRAY, ARRAY, -ARRAYCLOSE, ARRAYCLOSE, ARRAYEDIT, ARRAYPATH, ARRAYPOLAR, ARRAYRECT, ARX, -ATTDEF, ATTDEF, ATTDISP, -ATTEDIT, ATTEDIT, -ATTEXT, ATTEXT, AUDIT, AUTOCOMPLETE, AUTOCONSTRAIN, AUTOPUBLISH, BASE, -BHATCH, BHATCH, BLEND, -BLOCK, BLOCK, BLOOKUPTABLE, BMAKE, BMOD, BMPOUT, -BOUNDARY, BOUNDARY, BOX, BPOLY, BREAK, BREP, CAL, CELLSELECT, CHAMFER, CHAMFEREDGE, CHANGE, CHPROP, CIRCLE, CLASSICGROUP, CLASSICXREF, CLEANSCREENOFF, CLEANSCREENON, CLIP, CLOSEALL, -COLOR, COLOR, COMPILE, CONE, CONSTRAINTBAR, CONSTRAINTSETTINGS, CONVERT, CONVERTPOLY, CONVTONURBS, CONVTOSOLID, CONVTOSURFACE, COPY, COPYBASE, COPYCLIP, COPYHIST, COPYLINK, -COPYTOLAYER, COPYTOLAYER, CUTCLIP, CVADD, CVHIDE, -CVREBUILD, CVREBUILD, CVREMOVE, CVSHOW, CYLINDER, -DATAEXTRACTION, DATAEXTRACTION, DATALINK, DATALINKUPDATE, DBLIST, DCALIGNED, DCANGULAR, DCCONVERT, DCDIAMETER, DCDISPLAY, DCFORM, DCHORIZONTAL, DCLINEAR, DCRADIUS, DCVERTICAL, DDEDIT, DELAY, DELCONSTRAINT, DGNADJUST, DGNLAYERS, DIM, DIM1, DIMALIGNED, DIMANGULAR, DIMARC, DIMBASELINE, DIMBREAK, DIMCENTER, DIMCONSTRAINT, DIMCONTINUE, DIMDIAMETER, DIMDISASSOCIATE, DIMEDIT, DIMHORIZONTAL, -DIMINSPECT, DIMINSPECT, DIMJOGGED, DIMJOGLINE, DIMLINEAR, DIMORDINATE, DIMOVERRIDE, DIMRADIUS, DIMREASSOCIATE, DIMREGEN, DIMROTATED, DIMSPACE, -DIMSTYLE, DIMSTYLE, DIMTEDIT, DIMVERTICAL, DIST, DISTANTLIGHT, DIVIDE, DONUT, DOUGHNUT, DRAGMODE, DRAWORDER, DROPGEOM, DTEXT, DUMPCMDS, DVIEW, -DWFADJUST, DWFADJUST, -DWFATTACH, DWFATTACH, DWFCLIP, DWFFORMAT, DWFLAYERS, DXBIN, DXFIN, DXFOUT, -EATTEXT, EATTEXT, EDGESURF, EDITTABLECELL, ELEV, ELLIPSE, END, EPLOTEXT, ERASE, EXPLODE, -EXPORT, EXPORT, EXPORTDWF, EXPORTDWFX, EXPORTPDF, EXPORTSETTINGS, EXTEND, EXTRUDE, FILEOPEN, FILL, FILLET, FILLETEDGE, FLATSHOT, FREESPOT, FREEWEB, GCCOINCIDENT, GCCOLLINEAR, GCCONCENTRIC, GCEQUAL, GCFIX, GCHORIZONTAL, GCPARALLEL, GCPERPENDICULAR, GCSMOOTH, GCSYMMETRIC, GCTANGENT, GCVERTICAL, GEOMCONSTRAINT, GRADIENT, -GRAPHICSCONFIG, GRAPHICSCONFIG, GRAPHSCR, GRID, -GROUP, GROUP, GROUPEDIT, -HATCH, HATCH, -HATCHEDIT, HATCHEDIT, HATCHGENERATEBOUNDARY, HATCHSETBOUNDARY, HATCHSETORIGIN, HATCHTOBACK, HELIX, HELP, HIDE, HIDEOBJECTS, ID, -IMAGE, -IMAGEADJUST, IMAGECLIP, IMAGEQUALITY, IMPLIEDFACEX, IMPORT, IMPRINT, -INSERT, INSERT, -INTERFERE, INTERFERE, INTERSECT, ISOLATEOBJECTS, ISOPLANE, JOIN, JPGOUT, JUSTIFYTEXT, LAYCUR, -LAYDEL, LAYDEL, -LAYER, LAYERCLOSE, LAYERP, LAYERPMODE, LAYFRZ, LAYISO, LAYLCK, -LAYMCH, LAYMCH, LAYMCUR, -LAYMRG, LAYMRG, LAYOFF, LAYON, -LAYOUT, LAYOUT, LAYTHW, LAYULK, LAYUNISO, LAYVPI, LEADER, LENGTHEN, LIGHT, LIMITS, LINE, -LINETYPE, LINETYPE, LIST, LIVESECTION, LOAD, LOFT, LOGFILEOFF, LOGFILEON, LTSCALE, -LWEIGHT, LWEIGHT, MASSPROP, MATCHCELL, MEASURE, MEASUREGEOM, MESH, MESHCAP, MESHCOLLAPSE, MESHCREASE, MESHEXTRUDE, MESHMERGE, MESHOPTIONS, MESHPRIMITIVEOPTIONS, MESHREFINE, MESHSMOOTH, MESHSMOOTHLESS, MESHSMOOTHMORE, MESHSPIN, MESHSPLIT, MESHUNCREASE, MINSERT, MIRROR, MIRROR3D, MLEADER, MLEADERALIGN, MLEADERCOLLECT, MLEADERCONTENTEDIT, MLEADEREDIT, MLINE, MODEL, MOVE, MREDO, MTEDIT, -MTEXT, MTEXT, MTPROP, MULTIPLE, NAVBAR, NAVVCUBE, NCOPY, NETLOAD, NEW, -OBJECTSCALE, OFFSET, OOPS, OPEN, OPTCHPROP, ORTHO, -OSNAP, OSNAP, -OVERKILL, PAGESETUP, -PAN, -PARAMETERS, PARAMETERS, PARAMETERSCLOSE, -PARTIALOAD, PARTIALOAD, -PARTIALOPEN, PASTEBLOCK, PASTEORIG, PEDIT, PFACE, PLAN, PLANESURF, PLINE, -PLOT, PLOT, -PLOTSTAMP, -PLOTSTYLE, PNGOUT, POINT, POINTLIGHT, POLYGON, POLYSOLID, PRESSPULL, PREVIEW, PROJECTGEOMETRY, -PSETUPIN, PSETUPIN, PSFILL, PSOUT, PSPACE, -PUBLISH, PUBLISH, -PURGE, PURGE, PYRAMID, QDIM, QLEADER, QNEW, QSAVE, QTEXT, RAY, RECOVER, RECTANG, RECTANGLE, REDO, REDRAW, REDRAWALL, REGEN, REGEN3, REGENALL, REGENAUTO, REGION, -RENAME, RENAME, RESETBLOCK, RESUME, REVCLOUD, REVERSE, REVOLVE, REVSURF, ROTATE, ROTATE3D, RULESURF, SAVE, SAVEAS, SCALE, -SCALELISTEDIT, SCALETEXT, SCRIPT, SECTION, SECTIONPLANE, SECTIONPLANEJOG, SECTIONPLANESETTINGS, SECTIONPLANETOBLOCK, SELECT, SELECTSIMILAR, SEQUENCEPLAY, SETBYLAYER, SETVAR, -SHADE, SHADE, -SHADEMODE, SHADEMODE, SHAPE, SKETCH, SLICE, SNAP, SOLDRAW, SOLID, SOLIDEDIT, SOLPROF, SOLVIEW, SPACEMOUSEACTION, SPACETRANS, SPHERE, SPLINE, SPLINEDIT, SPOTLIGHT, STLOUT, STRETCH, -STYLE, STYLE, SUBTRACT, SURFBLEND, SURFEXTEND, SURFEXTRACTCURVE, SURFFILLET, SURFNETWORK, SURFOFFSET, SURFPATCH, SURFSCULPT, SURFTRIM, SURFUNTRIM, SWEEP, -TABLE, TABLE, TABLEDIT, TABLEEXPORT, TABLESTYLE, TABLET, TABSURF, TARGETPOINT, -TEXT, TEXT, TEXTEDIT, TEXTSCR, TEXTTOFRONT, THICKEN, TIFOUT, TIME, TINSERT, TOLERANCE, TORUS, TRACE, TRANSPARENCY, TRIM, U, UCS, UCSICON, UCSMAN, UNDEFINE, UNDO, UNGROUP, UNION, UNISOLATEOBJECTS, -UNITS, UNITS, UPDATETHUMBSNOW, -VIEW, VIEWBACK, VIEWCUBEACTION, VIEWFORWARD, VIEWGO, VIEWPLAY, VIEWPLOTDETAILS, VIEWPORTS, VIEWRES, -VISUALSTYLES, VPCLIP, VPLAYER, VPMAX, VPMIN, -VPORTS, VPORTS, VSCURRENT, VSSAVE, WALKFLYSETTINGS, -WBLOCK, WBLOCK, WEBLIGHT, WEDGE, WHOHAS, WIPEOUT, WMFIN, WMFOUT, -XBIND, XBIND, XCLIP, XEDGES, XLINE, XOPEN, -XREF, XREF, ZOOM.

Important note: not all of these commands actually do something useful – some simply return directly to the user, where they would otherwise have displayed a dialog, etc. – so you'll still need to test the commands you need by entering them or by executing your scripts.

I'm not going to list the commands that aren't available in the Core Console – if the command isn't in the above list, it's a fair bet that it isn't there – but there is another list of commands that is worth mentioning, as they currently cause the Core Console to crash (on my system, at least):

ACTBASEPOINT, ACTMANAGER, ACTRECORD, -ACTSTOP, ACTSTOP, ACTUSERINPUT, -ACTUSERMESSAGE, ACTUSERMESSAGE, ADJUST, CLASSICLAYER, CLOSE, CUI, CUIEXPORT, CUIIMPORT, -DGNATTACH, DGNATTACH, -DGNBIND, DGNCLIP, -LAYER, LAYER, MLEDIT, MLSTYLE, -NAVSMOTION, NAVSMOTION, NAVSMOTIONCLOSE, NAVSWHEEL, OBJECTSCALE, PAN, PASTEASHYPERLINK, PASTECLIP, -PDFADJUST, PDFADJUST, -PDFATTACH, PDFATTACH, PDFCLIP, PDFLAYERS, QCCLOSE, QUICKCALC, QUICKCUI, -QVDRAWING, QVDRAWING, QVDRAWINGCLOSE, -QVLAYOUT, QVLAYOUT, QVLAYOUTCLOSE, RECOVERALL, RIBBON, RIBBONCLOSE, RTPAN, RTZOOM, SCALELISTEDIT, ULAYERS, VTOPTIONS

I hope it goes without saying that these should be avoided – the good news is that they are mostly not commands you'll need in the Core Console. If you find you do need something from full AutoCAD that's not on the "working" list – and it's reasonable to expect would work in a version of AutoCAD with a very limited UI – please do make sure the ADN team is aware (whether by contacting them directly or posting to the AutoCAD .NET Discussion Group).

And then, last but not least, there are just a few commands that actually show some UI when launched from the Core Console (and these clearly need attention from our side):

BESETTINGS, PLOTSTYLE, VLIDE

I hope this little analysis proves to be of use to you when working with the Core Console. In the absence of more formal documentation, we (meaning the ADN team and I) will continue to do our best to make sure you at least have some guidance on how best to work with it.

37 responses to “Commands that “work” in the AutoCAD 2013 Core Console”

  1. I hope you send the "crash" list to your colleges? To crash is never the right response to a user command 😉

  2. Of course. 🙂

    Kean

  3. Thanks for the great list Kean, it will come in very handy.
    But how can -LAYER be considered "not commands you’ll need in the Core Console"?

    The good news is I just tried it & it worked, so maybe something before it caused it to crash...

  4. Mr. Walmsley:
    I'm a rookie and I wonder what's the best choise to start with.ObjectARX,or .NET? I'm waiting for your answer.Thank U very much.

  5. A useful list, we have added it to our database of AutoCAD commands at http://www.cadforum.cz/cadforum_en/command.asp?Core

    Looking forward to use the console.

  6. Here's my last response to your question. I don't like having to answer off-topic questions multiple times.

    keanw.com/2012/02/dynamic-net-in-autocad-2013.html#comment-6a00d83452464869e2016764122223970b

    Kean

  7. That is good news, and yes, it now works for me, too! 🙂

    I had also spotted that as one that would be useful to people. Hopefully we'll be abe to identify which of the earlier commands caused the instability.

    Kean

  8. jholmes1@cox.net Avatar
    jholmes1@cox.net

    I was wondering how this would work on a server? Idealy, I would like to run the core app on a server, that returns values (in the form of an xml stream) that can be consumed by an app for further processing. IIRC, the only way to do somthing before this was with ObjectDBX. Any chance this functionality is now a possability?

    HomeBoy Out

  9. Technically, yes: you'd need to check to make sure it's permitted from a software licensing perspective, though.

    Kean

  10. " var values =
    from l in File.ReadAllLines(
    "c:\\users\\walmslk\\desktop\\OEMCMDS.TXT"
    )
    let cols = l.Split(new[] { ';' })
    select new { Command = cols.First() };
    "

    Ugggggg.... what's the anonymous type with a single member for? 😮 8)

    This is all you need:

    var values = File.ReadAllLines(filename).Select( l => l.Split( new[] ';')[0]);

  11. It will load object enablers, but it will take time for "CRX" modules to be provided for vertical functionality, I expect.

    Kean

  12. Thanks, Tony.

    A couple of things got me to this point: I was previously taking more than just the command through from the text file (for more descriptive logging), but then decided to back that out.

    And as the code is basically disposable, in the sense that I've posted it for posterity (and admittedly should have taken more care considering it was being posted), but won't be using it again anytime soon.

    Thanks for (anonymously) keeping me honest! 😉

    Kean

  13. Thanks for the list. I am having troubles with the txt2mtxt command. I get an "unknown command" error. Any ideas why some of the express tools work and others don't?

  14. Looking in the Registry, it seems TXT2MTXT is implemented in the LeaderEx.arx module. As an .arx, this unfortunately won't load in the Core Console. More work is clearly needed to get Core-compatible commands such as this implemented in Core-loadable modules.

    Kean

  15. Hello
    The Open command does not work in the console.It does not ask the name of the file to open.Therefore, we do not open multiple files in a single console.And we can not launch a (SCR) script that allows to open files.

    Eric

  16. Hello Eric,

    That's correct: I should probably have pointed out that this is really a single-document experience. You open the console with the drawing of your choice - or multiple consoles for multiple drawings - but we don't have MDI-like document switching in a single console.

    Regards,

    Kean

  17. Hi,

    How can we load our own OARX-application ( ARX, CRX, DBX ) into the console since appload does not exist in the console?

    Regards,
    Jordan

  18. Hi Jordan,

    I'd expect Autoloader and demand-loading to work (although I admit I haven't tried either, so I may be overly optimistic), but otherwise you can always use ARXLOAD for .dbx/.crx and NETLOAD for .dll files.

    Kean

  19. Hello Kean,
    The console seems to not work with dxf files
    I have a crash whenever I run the console with a dxf file

  20. Kean Walmsley Avatar
    Kean Walmsley

    Hello Eric,

    I recently saw a response go our from ADN to that effect (it isn't something I'd tried myself). I assume they've submitted a change request for that behaviour.

    Regards,

    Kean

  21. Hello Kean,
    I found the 'flatshot' command in your list. Is it possible to call 'flatshot' without dialog, that is: Can I automate 'flatshot' without user interaction by help of core console or is there another way to do this? Thanks in advance.
    doc snyder

  22. SCALELISTEDIT seems a huge "fail" if it does not work, I must try that to confirm when I get my AutoCAD 2013.

  23. Kean Walmsley Avatar

    Hi doc,

    FLATSHOT made it onto the list as it didn't generate an "unknown command" error: as far as I can tell it doesn't do anything useful as it stands, however.

    What you really need is a new command-line version of the command (i.e. -FLATSHOT), of course: the best would be to submit this request to the ADN team, whether via the ADN site or the appropriate discussion forum.

    Regards,

    Kean

  24. Kean Walmsley Avatar

    It certainly (and unfortunately) fails for me. :-S

    Kean

  25. Mike Hutchinson Avatar
    Mike Hutchinson

    I would like to see a list of lisp, vl, vla and vlax functions that are useable.
    I included in the script the lisp load function to load up the lisp defuns I needed. But perhaps it was the calls to '(command "cmdname"... that caused the issues. Did I read that you should use the actual command in the script and not wrapped in '(command..' calls.
    Should I do the lisp files loading from acad.lsp as part of the profile that I use rather than from the script? At one point I tried to multiple ways to delete layout tabs by using lisp but did not have much luck.

  26. Kean Walmsley Avatar

    I can see why that would be useful. Most LISP functions should be available, although I have doubts about vla[x]-*.

    You could also be hitting issues with commands not being available. I don't remember any recommendations about not using (command "...") - it seems familiar but I suspect is from a different context.

    I would load the LISP from the script, personally.

    The discussion groups and/or ADN should be able to help with specific issues, if you want to post code there.

    Kean

  27. Hello Kean

    Sorry to comment on another old blog post, but i was wondering if there is any documentation for using the core console now that it's been around for a while?

    I was also wondering if it's possible to run the core console in the background while acad.exe is running.

    The video that Balaji Ramamoorthy did for DevTV is pretty darn cool by the way. youtu.be/ars7ZnCqpVA

    Thanks for your time. These blogs are really helpful!

    1. Kean Walmsley Avatar
      Kean Walmsley

      Hello Ian,

      No official documentation (although this blog and the ADN DevBlog tries to fill the gap, when we can). It's primarily a mechanism used within the product to implement certain features: it's getting more and more adoption, so with each release it gets more complete and stable.

      It's absolutely intended to be usable when AutoCAD is running. It's perfect for that.

      Yes, Balaji's video is cool. 🙂

      Regards,

      Kean

      1. Sounds great, i'll just dive in and start plaything then.

        Thanks again for answering my questions!

  28. Hi Kean

    I would like with "Profile" is used by accoreconsole.exe.

    For example for "print-to-pdf" you need textfonts and PC3, to find them you need supportpaths which are stored (in normal autocad) in "Profiles".

    So which settings are used?

    Regards

    Peter

    1. Hi Peter,

      You can use the /p command-line flag to specify a specific profile for the Core Console to use.

      Regards,

      Kean

      1. Good evening Kean

        thanks for the info. I looked again to the video of Balaji, where only the switches /s, /i; /l and isolate /isolate are described.

        "/p" brings me to the question: which startup switches from AutoCAD can be used? "/n" does not make sense ...

        One more question:
        I suppose that accoreconsole.exe is under current development and improvement and that version 2015 is "better" than version 2014. So my idea is to use (for a client ..) accoreconsole(2015) (existing and licenced, but no rollout to all users) with AutoCAD2014 (Standard installation in the company).

        Great idea? Or more a mad one?

        Regards

        Peter

        1. Hi Peter,

          If you run it from a command prompt with no arguments you'll see the valid switches.

          Yes, the Core Console is a new feature that is evolving quite a bit between releases. So the 2015 version will indeed be "better". I suggest testing thoroughly if you need an app developed with 2015 to work with the 2014 Core Console, of course.

          Regards,

          Kean

          1. Thanks, I will try.

            Peter

  29. Has any support been added yet for (vl-load-com) activeX functions?

    1. I don't believe so. You might try asking ADN or posting to the discussion groups.

      Kean

Leave a Reply to Eric Cancel reply

Your email address will not be published. Required fields are marked *