Ongoing issues with Revit 2015 - Esc key + UI issues

Ongoing issues with Revit 2015 - Esc key + UI issues

Anonymous
Not applicable
689 Views
2 Replies
Message 1 of 3

Ongoing issues with Revit 2015 - Esc key + UI issues

Anonymous
Not applicable

Hi everyone,

 

I have a client with an ongoing Revit 2015 issue...

 

There are 2 distinct problems:

 

1. The Esc key does not deselect the currently selected object

2. UI elements such as the properties window loads empty and the app must be restarted (sometimes several times) to resolve the issue.

 

 

Here is what we've done so far:

1. Upgraded graphics drivers (AMD Firepro v3900) to most recent version. Resolved UI problem temporarily.

2. Repaired Revit. Resolved both problems temporarily.

3. Reinstalled Revit. Resolved UI problems temporarily.

4. As per other posts on the subject, ensured that no Adobe apps were running while using Revit, as I've read it can interfere with the esc key function. No change.

5. Updated Windows. No change.

 

Has anyone else encountered these particular issues with 2015?

0 Likes
690 Views
2 Replies
Replies (2)
Message 2 of 3

rosskirby
Advisor
Advisor

I've been using Revit 2015 for over a year, and haven't had any of those issues, so the error must be with either their hardware or some conflicting software.  Sorry I can't offer more, but given your description of the problems, you may need to check and make sure that you have the correct version of the .NET framework installed to work with Revit.  If your client has some other software on their machine that is constantly updating or rolling back the .NET framework to the wrong version, then that could be causing the repeat problems.  That's why you see a temporary improvement when you repair/reinstall Revit, since it installs the correct version of .NET.

Ross Kirby
Principal
Dynamik Design
www.dynamikdesign.com
Message 3 of 3

Anonymous
Not applicable

Thank you Ross for your suggestions.

 

I have gone through and uninstalled all applications that are no longer required on the system, or could potentially cause issues with .NET. Unfortunately this did not resolve the issue for us.

 

I have also attempted using a different Windows Profile thinking that the current one could have been corrupt, but that is also not the case as the issues continue there. However, it did appear to resolve the issue with the view, but I cannot confirm whether that was just temporary as what we have been experiencing seems to be quite random when it works and doesn't.

 

Any other suggestions?

0 Likes