Performance Enhancement Tool

[jmayo-EE]

Anyone see and/or test this?

[AllenJessup]

Yes John, They took away the ability to add an .msp file. It all has to be done through the Applications Manager. (AppMangler)

[rkmcswain]

jmayo wrote:

What's the issue adding it to the admin image?

@jmayo-EE - without trying to sound condescending, read the README file, and then check out the screenshot in my post above.

To directly answer your question, no, I do not see a way to add an MSI file to an admin image. It looks like the method described in the README is the way now.

[thejac]

Does this affect the Civil Object Enabler at all, used with TruView for example?  I noticed the COE 2017 now says SP1, will there be a COE 2017 SP1.1?

[AllenJessup]

Autodesk is looking in to SP1.1 not being shown in App Manager.

http://forums.autodesk.com/t5/installation-licensing/add-sp-to-deployment/m-p/6547986#M136663

[AllenJessup]

Autodesk is asking for information from those who are not seeing SP1.1 in the Application Manager. See post #25 of this thread

http://forums.autodesk.com/t5/installation-licensing/add-sp-to-deployment/m-p/6553065/highlight/fals...

[AllenJessup]

This is the workaround I received from Autodesk:

Now to resolve this issue on the computer on which you are adding the SP1.1 to the deployment please proceed as follows:
 

1. Exit Autodesk Application Manager by right-clicking on the icon in the System Tray and selecting Exit.

2. Click the Start button and type services.msc in the search box, then hit Enter.

3. Locate AdAppMgrSvc in the list. Right click the service and select Stop.

4. Delete these directories:
   • C:/Program Files (x86)/Common Files/Autodesk Shared/AppManager
   • %programdata%\autodesk\sds
   • %userprofile%\Documents\Autodesk Application Manager

5. Launch the registry editor (Start > Run > regedit). Delete the keys listed below:
   • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Autodesk\Autodesk Application Manager
   • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Autodesk Application Manager

6. Reinstall Autodesk Application Manager using the AdApplicationManager-WebInstaller.exe file located on this site:

 
http://knowledge.autodesk.com/search-result/caas/downloads/content/autodesk-application-manager.html
 

7. Repeat steps 2 and 3 above but this time select Start instead of Stop.

Reboot the computer and now attempt to modify the deployment and see if the SP1.1 appears. 

I won't be able to try this right away. But I thought I should share.

[rkmcswain]

_That_ is the workaround? Great, except I can't just reboot the server that this data is sitting on when I feel like it.

I suppose I'll just create a deployment on a different server and then move it back to the real server, and _then_ fix that deployment using another hack....

[tcorey]

@louisa_holland, have you or has someone else at Autodesk had a chance to create a batch file for 2017?

[louisa_holland]

Drumroll please...

Here is the zip file containing the 2017 batch file. (I've added a 2017 folder to the zip)

https://autodesk.box.com/v/C3DPerformanceFix

Let me know if this helps.

Thanks all!

Lou

[rkmcswain]

Would still like to know:

1. Why isn't SP1.1 for 2017 available in the downloads section of the knowledge network.
2. Why isn't this "fix" being published as a hotfix downloadable for 2014 and 2015?
3. Lastly, can we ever expect the "Application Manager" for 2017 deployments, to pick up SP1.1 so we can patch deployments, or are we stuck with the workaround posted above?

I'm actually just fine with this not being published or promoted any more than it is. No reason to help out our local competitors who are still on 2014 and 2015; but it's not the style of Autodesk to release patches and fixes via a post in the forums and then post the actual files in a "box" somewhere.

[lou.holland]

I'll tell ya' what I know...

#1: Going forward, updates and service packs will only be available to subscribed users. Not all of the product teams have conformed to this yet, which is why some 2017 products have updates on AKN. The fact that the direct download link I posted works is essentially a fluke. 

#2: The "official" KB article with the info for all releases should be out any minute now. You'll recognize it when you see it, becuse it is the same text that I posted here. 

#3: SP 1.1 not showing up in application manager is still a mystery. Thanks to your help I've given the team that develops that tool several logs. If it requires an update, the good news is that Autodesk Application Manager can update itself (with local admin access and user input of course).  

I hope this helps.

Thanks!

Lou 

[rkmcswain]

1. Perfect. So I just noticed that it is available while logged on, at http://manage.autodesk.com
2. Okay, great. I'll keep an eye out for it.
3. I sure wish we could simply append a SP onto a deployment like we could in the past. I have the deployment ready to go and I have the SP, but just no way to combine the two.

Thanks @lou.holland ! P.S. This is the kind of responsiveness that goes a long way with your customers!

[JamesMaeding]

Just saw this thread.

We are on 2015, and I got the new dbx, and opening (slow) in civil3d and saving does clean out drawings.

Opening in AutoCAD 2015 and saving does not do anything. I have the OE's installed too.

The sad thing here is so many have suffered from the issue for so long.

The sadder thing is Autodesk supplied a batch that uses coreconsole to open and save the file.

That flies in the face of every single autodesk developer I know.

The right (conservative) way to clean files, once your update is installed, goes like this:

1) uninstall the C3D OE's for your AutoCAD. This does not affect C3D. This will make acad ignore the bad c3d styles and open fast.

2) get a .net routine that opens and saves files via dbx. That does not load xrefs, so will be way faster than coreconsole. Use it in an acad session, not civil3d.

I attached code you need to make the .net tool. I don't have 2016 or 17 installed yet so need others to compile for them. I'll have those soon though.

The code I supply has the tools to open dbx style, and save. It has much more though. Rename to remove the .txt and make .cs.

As is, the command it defines purges app ids, anno scales, regular purge, and deletes the "Root" entry to the NOD (Named object dictionary)

OBVIOUSLY, get rid of those calls if you don't want that done.

You might notice the code is set up to work in acad or Bricscad. See the #if BCAD?

The reason you would use Bricscad is its fast, even with acad OE's enabled as it does not care about acad.

Our company separates between civil3d drawings and sheets/bases, so we simply nuke the civil3d styles as well as app ids and other lovely stuff.

We have been doing this for years now, but its still a challenge even with super fast cleaning tools.

Now the coolest thing here, is I found the form to request a refund from Autodesk for all the trouble.

[Jeff_M]

James, did you test this without removing the Root NOD? I may be wrong, but if C3D isn't loaded then neither will the AeccNetwork.dbx file which is responsible for the 'cleaning'. You confirmed this by loading plain Autocad and saying it didn't do anything. So if it didn't do anything there, what makes you think it will work using the process you described? For all C3D users who intend to keep using these drawings in C3D, do NOT delete the Root NOD!

[JamesMaeding]

BTW, I'm now uninstalling the Civil3d 2015 OE's for all computers, and having seen this debacle, will never again install them.

I want the default to be that things open fast in vanilla acad session no matter what.

Its sad to see this all happen, as the information to solve it is readily available if Autodesk will just maintain communication with some key cad managers.

[JamesMaeding]

Yes, I tested on a file with the bad styles in an acad session with OE's and it opened slow.

Then uninstalled the OE's and it opened fast.

I did not modify the file between, so that is rock solid.

I say autocad "did nothing", meaning saving the file does not clean out the junk.

This is with the updated dbx.

If I was not clear, deleting the Root entry of NOD deletes all civil3d styles for a drawing.

You may want that, or it may be disaster.

If you do delete that entry on file with c3d objects, the worst I have seen is you must run audit on the file to reassign the styles to standard.

In any case, assume file cleaning will fail, so you have a copy of stuff handy.

Our full cleaning tools back up the file locally, log the activity, and tag the drawing with activity history.

Like I say, this file cleaning stuff has become a big part of project cad management.

Part of the reason I only posted code was so whoever uses it must have the skills to make into a project, and compile.

Those that do will not get into trouble with just code.

thx!

[JamesMaeding]

Jeff, I realized I should clarify my strategy.

You might wonder why, on a fully updated 2015 system, opening in vanilla acad and saving does not clean out a drawing, yet opening it dbx style and saving does.

I don't know, it does though. I tested it three times to be sure.

And it does not matter if the OE's are installed, but you should uninstall them for speed reasons as the dbx open is slow if you don't.

That would likely not have occurred to most people, and I bet even Autodesk did not catch it.

So if you do it right, my way is 10-20x faster than Autodesk's, so can be used during a real work day without ruining relationships.

[Jeff_M]

---

@Anonymous wrote:

Yes, I tested on a file with the bad styles in an acad session with OE's and it opened slow.

Then uninstalled the OE's and it opened fast.

I did not modify the file between, so that is rock solid.

I say autocad "did nothing", meaning saving the file does not clean out the junk.

This is with the updated dbx.

thx!

---

Exactly! In order for the new DBX file to do what it does when a file is saved, it must be loaded. It is not loaded when plain Acad is used, therefor one must open the files where C3D is present. I have never used the accoreconsole, but based on what Louisa created with the batch files, I am guessing that this still permits the C3D stuff to get loaded.

Now, your solution may very well work fine, as long as it is initiated from a C3D session (yes, the files will still load slow, but that is unavoidable that I can tell) and the NOD entry is left alone. 

[Jeff_M]

I would be willing to bet that 99.9%of the C3D users would not want to have their styles all reset to Standard....and if that is what speeds up a drawing for you, it would be a disaster for the other 99.9% of us. I'll take the initial slow load with the new dbx in order to get the drawings back up to speed. BTW, I think that the Root dictionary holds more than just styles...such as Coordinate zone, Point Groups, etc.

[JamesMaeding]

Oh, I see. You are correct, if simply opening and saving using .net or any method, you must run from a c3d session, and you cannot escape the slow load and save speed.

I fooled myself as I was not just opening and saving, I was deleting the c3d styles at the same time.

Still, using .net and dbx style will prevent full xref loading that coreconsole does. so its much better.

That solution is not acceptable for my company though, as its too slow.

Also, it requires C3D which many companies do not have.

Instead, we delete the c3d styles using .net and the code posted, and do that using an acad session without OE's or Bricscad.

Once I get 2016 and 17 going, I can compile our tools and provide for free. We just want clean files out there.