Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

_Serge
en respuesta a: cadffm

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.