Thanks, Wasn't sure what you meant by "commication center in Civil 3d" but I figured it out.
it will be here when autodesk posts it to their website: http://usa.autodesk.com/adsk/servlet/ps/dl/index?s
1st bug to report....
It does not find acad2013.lsp and acad2013doc.lsp in my custom support path even though it is the highest path in my support path. Even when I remove them from their default locations, C3D will not find them in my support path. It just ignores them completely. I had to appload them in. (This will not be fun to support… Manual labor on everyone’s PC to get their computers to load the correct files…)
You shouldn't be modifying those files in the first place.... acad.lsp and acaddoc.lsp are intended for users to create/edit, as these are never touched by installs/updates.
I wonder if that has to do with the feature they added to try to prevent the acad.lsp "virus" people have misunderstood.
My gripe to add is the hotfix 2 does not install silently. I think the install makers need a little checklist, it would go like this:
1) make it easy to do silent installs of every product, for ever and ever, from here on out.
2) do not forget rule No. 1
3) Our first impression of software is the install. At least get that part right by not forgetting rule No 2.
Yes, I would imagine In some places they are for the "users" to create/edit. In my office they are for me "The Supervisor" to edit. I use them to load custom applications, force variables, etc.
Rather than rely on everyone to overwrite their acad.lsp in all versions of their AutoCAD’s I release updates to C:\_AutoCAD\Config\lisp\
Then, regardless if someone is running C3D, Map 3D, AutoCAD, they all point to that location to pull from the master acad.lsp and acaddoc.lsp
If I add a new command for the department, all I have to do is add it to their .net folder and add the line to load it into their acad2013.doc.lsp file. Then it’s there next time the open a drawing….
I definitely do not want them tinkering in there….
I’ll try dropping the 2013 from the file to see if it works…
I never heard the acad.lsp and acaddoc.lsp were more for users of not.
I know the acad2013.lsp is present in an OOTB install, and I thought was not for customization.
We also use one acad.lsp and acaddoc.lsp for each version of acad, and I also have a company key-ins file that works for all versions (2009-2013) and also for bricscad.
The trick is to make your own load function that detects what version and prog you are in, and selects the file to load from an input list.
Dropping the 2013 seems to have worked.... although I do not see acaddoc.lsp in my appload menu, but the function in there seem to be working....