- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Hi,
Did anything changed with the acad20XXdoc.lsp in AutoCAD 2018 ? I can't load anything from the support\fr-fr\acad2018doc.lsp file (in French version) during startup while it worked fine in 2017, 2016, ...
Thanks !
Head of Innovation - TT Géomètres Experts Paris
Autocad / Recap / Revit user
i7-9750H / RTX 2080
¡Resuelto! Ir a solución.
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
I am sorry loading the LISP file doesn't seem to be working for you. Have tried to manually load the file? If you rename the file to acaddoc.lsp does it then work?
Please select the Accept as Solution button if my post solves your issue or answers your question.
John Vellek
Join the Autodesk Customer Council - Interact with developers, provide feedback on current and future software releases, and beta test the latest software!
Autodesk Knowledge Network | Autodesk Account | Product Feedback
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
I've tried on different computer and I have the same problem only with AutoCAD 2018.
It seems to work using the acad20XX.lsp file which is in the support folder. The only difference is that it launches once per session instead of once per drawing.
Maybe using those files is out of date but I've never find any other way to automate checking and .NET loading when AutoCAD starts.
Head of Innovation - TT Géomètres Experts Paris
Autocad / Recap / Revit user
i7-9750H / RTX 2080
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
acad20xx.lsp and acad20xxdoc.lsp is not for customizing,
try to use your own acaddoc.lsp
It is not a 2018 special, you can get that timing problem in every Version.
AutoCAD-Help:
Note: Do not modify the reserved acad<release>doc.lsp file.
and
near to topic: About Auto-Loading and Running AutoLISP Routines
Sebastian
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Tested for you in 2018: AutoCAD always loads this file (if it exists):
C: \ Program Files \ Autodesk \ AutoCAD 2018 \ Support \ @@-@@ \ acad2018doc.lsp
No other acad2018doc.lsp!
Sebastian
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
I think there is a bug in the international versions of AutoCAD 2018 and Autodesk is not likely to find it because they use a subdirectory called "C:\Program Files\Autodesk\AutoCAD 2018\Support\en-US". I've seen other people suggesting to copy acad2018doc.lsp in the parent directory. This may solve one problem but this is a partial solution. Also, I’ve seen suggestion about using APPLOAD to force the file to be loaded (being a software developer, I don't like to rely on APPLOAD because it follows the profile so this it not safe). In both cases, AutoCAD will miss the loading of the other support files in "en-US" such 3d.lsp, mvsetup.lsp, and so on.
The only workaround I found was to copy the full content of "C:\Program Files\Autodesk\AutoCAD 2018\Support\xx-XX" under "C:\Program Files\Autodesk\AutoCAD 2018\Support\en-US", where "xx-X" may be "fr-FR", "de-DE", "it-IT".
If AutoCAD was opened during this operation, you will have to restart it so it can works.
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
"I think there is a bug in the international versions of AutoCAD 2018"
I think there is a bug in the international versions of AutoCAD 2018 that Autodesk is unlikely to find because it has a subdirectory named "C: \ Program Files \ Autodesk \ AutoCAD 2018 \ Support \ en-US"
What bug, where is a problem?
With the Acad2018.lsp and Acad2018doc.lsp there is no problem, right?
There are system files in the installation folder, the user has nothing to change.
This and the corresponding documentation already exist since version 2013,
new is just that the files are really only loaded from there.
I know no problem, what problem are you talking about?
acad2018.lsp is for the complete installation "C: \ Program Files \ Autodesk \ AutoCAD 2018 \ Support \
acad2018doc.lsp is dependent on the language version "C: \ Program Files \ Autodesk \ AutoCAD 2018 \ Support \ @@ - @@ \
Sebastian
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Hi,
As you may have noticed, berson.guillau is located in Paris, so he is using a French version like me. In the international versions, and only with the 2018 version (including vanilla, Map, Civil and so on), the bug exists. Are you using an American version of AutoCAD 2018 ? If yes and you don't believe me, please install yourself a French, German or Spanish version on a new computer (or a virtual machine) where an existing copy of the US version is not already installed .
Here is a possible explanation for this bug. In ObjectARX and in Managed Code, the findfile function comes with an additional "Autodesk.AutoCAD.DatabaseServices.FindFileHint" parameter and this might have been hardcoded with the "en-us" path to locate the Acad2018doc.lsp file. Otherwise, it makes no sense since its path is in the search paths. Autodesk makes continuous changes with the trusted paths and the plug-ins mechanisms.
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Hello Serge
berson.guillaume is located in france , but he had make one or two mistakes and the issue should be solved.
Later YOU talk about an Issue and so i was asking YOU what you mean in detail.
Thanks for the answer, but I asked what you think is a mistake?
So I have not recognized any problem at all, so I wanted a complete explanation that (supposedly) does not work as it should.
And above all: where the difference to the US version lies.
I would like to know it, thank you for your patience.
Please take into account in your statement my previous answer (Post 7) to you regarding acad2018 & acad2018doc!
(My version: I initially had only a German version installed and now the English language pack for 2018, so I can call AutoCAD as German or English version - as I would like)
If I have the explanation of what you see as a bug, then I like to answer it again, or I know afterwards an error that is currently not known to me as a mistake.
Sebastian
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Hi Sebastian,
The problem I exposed was : when an international version of AutoCAD 2018 is taken without any change, the acad2018doc.lsp is not loaded so the functions like autoload are not available.
On the other hand, Guillaume didn’t say much. I’m not sure of what he as really done. Is really actually fully satisfied, or his problem related to the fact that he had changed some file content, or did he tried functions like MVS from the mvsetup.lsp file? I assume he solved his problem by making a copy of the file in its parent directory.
What I know is that I had the autoload problem myself and I’ve seen other people on different forums having experienced the same problem and what they’ve done was to copy the acad2018doc.lsp file in its parent directory. I didn’t like this solution because, has mentioned, files in C:\Program Files\Autodesk\AutoCAD 2018\Support\fr-fr like 3d.lsp, 3darray.lsp, and so on are not loaded.
Call it instinct but I decided to make a copy of C:\Program Files\Autodesk\AutoCAD 2018\Support\fr-fr under C:\Program Files\Autodesk\AutoCAD 2018\Support\en-US and all the problem were gone by magic. This solution is easy to implement for a CAD manager because they can update their deployment (MSI) files.
I also decided to dig further my intuition by using the ObjectARX function "virtual AcLispAppInfo* GetItemOfLispList(int nIndex)". With this, you can track all the locations from where the Lisp files are loaded. So, even if C:\Program Files\Autodesk\AutoCAD 2018\Support\fr-fr was in my search paths and not the en-US one, GetItemOfLispList gave me the proof that AutoCAD was loading it from the latest one. More funny, if I had a copy of acad2018doc.lsp in the 3 directories, the parent directory, the en-US and the fr-FR , GetItemOfLispList told me that AutoCAD iwas still loading from en-US (he is tubborn isn’t it). This is why I suspect a developer at Autodesk that he made a search of the rogue file with an hard-coded relative path "en-US".
I hope this help clarify my point of view.
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Thats clarified your point of view, thank you.
I read your explanation and looked at it once. However, I don't know problems in this regard.
Can you write something "against" the following statements that are reproducible for others?
1. The Acad2018doc.lsp is first searched in the *supportfolder (Standard=C:\\Program Files\\Autodesk\\AutoCAD 2018\\Support)
- By default there is no acad2018doc.lsp included in that Folder.
But you could create it or change the *supportfolder Path and it will be loaded from there regardless of the language version.
Problems with autoload/3DARRAY should not appear, because in file acad2018doc is a simple lisp (findfile "3DARRAY") statement - inside function "ai_ffile",
so it is unimportant where the currently loaded acad2018doc is located.
2. If no acad2018doc.lsp is found in *supportfolder Acad will search for it
in **supportfolderlang (Standard=C:\\Program Files\\Autodesk\\AutoCAD 2018\\Support\\<UILOCALE> - for example you start french Acad \\fr-fr
3. If no acad2018doc.lsp is found in *supportfolder and not in **supportfolderlang, searching for the systemfile acad2018doc stopped.
Explanation: *SupportFolder and **SupportFolderLang RegistryKeys
That Registry-Keys dependent of running language-version of Autocad:
de-de HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R22.0\ACAD-1001:407
en-us HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R22.0\ACAD-1001:409
aso...
You can change them during a session because Acad check the value(path information) on demand during a program session.
(but I would say, no changes are needed)
(defun getMAINPATH (? / PATH)
(if (and ?
(setq PATH (strcat "HKEY_CURRENT_USER\\" (vlax-user-product-key)))
(member (strcase ?) (mapcar 'strcase (vl-registry-descendents PATH T)))
)
(vl-registry-read PATH ?)
)
)
Befehl: (getMAINPATH "SupportFolder")
"C:\\Program Files\\Autodesk\\AutoCAD 2018\\Support\\"
Befehl: (getMAINPATH "SupportFolderLang")
"C:\\Program Files\\Autodesk\\AutoCAD 2018\\Support\\de-de"
I hope this help clarify my point of view anf if you can write something "against" the statements(reproducible for others), please let me know.
EDIT/in addition: Which language version is loaded is controlled by the commandline parameter / language, for example with an DesktopLink Start-Icon
Or if you start Acad without / language parameter, then the last used language version should be started (also registry key entry)
Sebastian
Sebastian
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
Hi Sebastian,
We just got a confirmation from Autodesk at this very moment. They admit there is a bug. Note: when we send them the case, I only had the solution of copying the file to the parent directory.
Please find in italic an excerpt
In regards to your issue, the 2018 folder structure is a bit different for AutoCAD Map 3D 2018 than in previous years. This is something we know about, and get a lot of calls in from France as well. The APPLOAD is not configured to automatically recognize the the ...\fr-FR folder and what you did by moving the .lsp in the the ...\Support folder is one of two solutions to this. Alternatively from within Map 3D if you run the APPLOAD command you can add the .lsp and add that file to the history and add it to the Startup Suite by clicking on "Contents".
Our development team knows about this, and I sure hope 2018 is the only release that has the \fr-FR folder location "unknown" by the product. Again, I get a lot of customer in France complaining about the same.
Also be aware that we do not support the actual modification of the ACAD2018DOC.lsp file so please be careful. It's a good idea to have it backed up somewhere.
I hope this information helps and please let me know if you have any follow-up questions or concerns.
Entschuldigen, wenn ich auf Deutsch extrapoliert habe. Vielleicht ist es nicht funktionniert aber ich sollte es nicht annehmen. Vielen Danke für alles.
Sorry if included German without verifying. I made an assumption. Maybe there is a bug, maybe not. Only an instalation from scratch will tell.
Tschüss