Tool Pallette Disappearing

[mikeshick]

I've seen a few threads of tool pallette corruption.  This has been a problem for both Architecture and Civil 3D software for years, where the pallettes disappear and cannot be reloaded, or certain pallettes lose their ability to be modified or refreshed, etc.

For many years, I've made the practice of creating a custom profile and exporting with each new version. I also create a custom workspace.  I also export my custom tool pallettes to the content browser under a custom library that I carry over from version to version.

In the past, I've resorted to deleting currupted tp's and then just reloading from the content browser.  Occassionaly, more severe corruptions have resulted reloading a fresh version of my profile (arg) file.

Today, however, nothing is working.  I've attemped to do both, but cannot load my tp's from the content browser.  They just wont appear.

I've also reloaded the profile, but it does nothing for the tp's.

I also copied an aws file from a working computer, but this didn't do anything either.

Anyone out there have some another solution?

Thanks!

[klaus.schumann]

Hi Mike,

Sorry to hear about hte trouble with yout toolpalettes. If you have not yet solved the problem and all else has failed, the next try would be to use the "Reset Settings to Default" link available from the Start menu group.

If this works you can then reload your arg file to get back your custom settings you had previously saved.

If still no luck, try deleting the program's registry key... Please let us know also what verion of the software you are using so we can point you to more specific troubleshooting steps.

Kind regards,

Klaus

[mikeshick]

Solution required a reinstall of Autodesk Architecture 2013. All is working fine now. This has been a problem with Autodesk products ever since tool palettes became a feature in the software, both in Land Desktop, Civil3D, and Architecture....and I'm sure others. Inevitably, I and several others have had tp get corrupted ever now and again. Always there is a slight nuance, but corrupted nonetheless.

Thanks,

[klaus.schumann]

Hi Mike,

Thanks for letting us know. Glad the problem is resolved now.