Set FileDia doesn't work in accoreconsole ( with specific argument)
It is not very clear to me why you need to worry about FILEDIA when using core console. Are you saying that after running core console in your computer and then start AutoCAD desktop, the FILEDIA of that AutoCAD session becomes 0? In my experience that does not happen. There is simply no need to worry about FILEDIA in the core console at all. FILEDIA is stored in Windows registry (HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\Rxxx\ACAD-xxxx.xxx\FixedProfile\General Configuration\FileDialog), you can check this key's value right before and after you use the core console, to see if it gets changed.
Is there particular reasons that you have to open a drawing or drawings with code that runs with core console, as opposed to open the drawing as core console's startup argument? if you try to let single core console session process multiple drawings (batch processing), then that is wrong way to do the work. It should be one drawing per core console instance; that is, start a core console instance with one drawing, do the work, and then quit the core console. This way, if you need to do batch drawing processing, you can spawn multiple core console instances in parallel, taking advantage of modern computer's multi-core CPUs power to get the batch work done much faster.
Well, as I said, from my experience, core console setting FILEDIA to 0 does not affect the FILEDIA value in the desktop session. See the video clip here that recorded my quick test:
1. Verify the FILEDIA in registry is 1;
2. Start core console instance, and then check the value in registry: it becomes 0;
3. Do something (or not do anything) in the core console; then quit the core console;
4. Check the FILEDIA value in the registry: it turns back to its original value (1).
In your case, if the FILEDIA in the registry is not restored, are you sure you close the core console correctly (i.e. execute command "QUIT", assuming you did not call Process.Kill() to end the core console process)?
The core console being started manually (as showed in my video clip), or started by code/BAT command would not make difference, I'd say. You may want to verify it with your scrip, in which you DO NOT try to set FILEDIA, and somehow pause the core console. Then, you can examine the registry for the FILEDIA value; then let your script go ahead and quit core console properly; examine the registry again to see if it is restored (of course, you want to make sure the original value is 1.
That was I suspected: the core console instance may not be ended properly for it to have chance to reset the FILEDIA. I mean, there is no need to set FILEDIA in the script. See the end of my reply in message 7.
Another idea is to use a separate profile for your automation workloads so it doesn’t interfere with your other profiles.
You can start from C3D_METRIC, save it as "Automation", and then import that profile.
D:\Dev\29756>"D:\Acad\AutoCAD 2025\accoreconsole.exe" /p Automation /s D:\Dev\29756\run.scr
Redirect stdout (file: C:\Users\moogalm\AppData\Local\Temp\accc398442).
AcCoreConsole: StdOutConsoleMode: processed-output: enabled,auto
AutoCAD Core Engine Console - Copyright 2024 Autodesk, Inc. All rights reserved. (V.171.0.0)
Execution Path:
D:\Acad\AutoCAD 2025\accoreconsole.exe
Current Directory: D:\Dev\29756
Version Number: V.171.0.0 (UNICODE)
LogFilePath has been set to the working folder.
Regenerating model.
**** System Variable Changed ****
1 of the monitored system variables has changed from the preferred value. Use SYSVARMONITOR command to view changes.
AutoCAD menu utilities loaded.
Command:
Command:
Command:
Command: (getvar "CPROFILE")
"Automation"
Command: (print "Hello World")
"Hello World" "Hello World"
Command: (setvar "FILEDIA" 1)
1
Command: QUIT
**** No System Variable Changed ****QUIT
QUIT
Madhukar Moogala
Senior Developer Advocate
Forge Blog | AutoCAD Dev Blog | ObjectARX Developer Guide | ObjectARX Reference Guide|Schedule A Chat
