Autodesk Solutions, Revit & Autocad combined with Nvidia drivers
Autodesk Solutions, Revit & Autocad combined with Nvidia drivers
Hi there,
this is general request for comparative information from anyone who regularly uses the above mentioned software - Revit and/or Autocad - that also uses a GPU with Nvidia drivers.
Simply put, if you use either Revit or Autocad with any of the following Nvidia drivers installed (studio or game ready):
466.77
471.11
471.41
471.68
471.96
and you have a diagnostic program such as GPU-Z or MSI Afterburner, can you please tell me how your GPU clock is behaving while either of these programs is open and running?
Is your GPU clocking up to load levels while they are open and being used?
Any and all information regarding this would be greatly appreciated.
Thanks in advance
This setup uses an unapproved GPU and drivers optimized for Revit/Autocad, which is probably causing most of your issues.
studio or game ready"
- we've encountered problems with both options.
But to address your query more clearly, I rely on game ready drivers on my personal computer (since I play games there when it isn't functioning properly) and have managed without issues for the past 4-5 years, never facing any problems with the card upgrading while using those programs.
This information comes directly from Autodesk:
"As a general guideline, it's advised to install the newest driver available from the graphics card manufacturer."
Nevertheless, with the most recent driver versions (from 466.77 to 471.96), I've observed that the card would increase its load levels when using Revit or Autocad.
Even more surprising, it doesn't increase when running other comparable software such as 3Ds Max or Sketchup—3Ds Max is another Autodesk product.
This has been tested on my 1080Ti system. Last week in our office, a new employee started with a brand-new machine and fresh installations (RTX 3060, studio driver 471.68). Despite not having diagnostic software to check the clock rate, he experienced strange graphics issues (objects disappearing after prolonged use) and the Task Manager reported the card usage at over 50% when it shouldn't have exceeded 20-30% for the task, eventually causing the CPU to freeze at 100% even when idle.
We switched back to driver 466.47—the latest version we found without this issue—and everything functioned normally.
The performance variations observed during testing were consistent:
- 466.47 – no unusual upclocking
- 466.77 – upclocking with Revit or Autocad
- 471.11 – upclocking with Revit or Autocad
- 471.41 – upclocking with Revit or Autocad and multiple screens (usually stayed at base levels, though one instance was notably higher)
- 471.68 – upclocking with Revit or Autocad
- 471.96 – upclocking only with Autocad
Currently, I'm using 471.96 and the upclocking issue is absent for Revit, which is acceptable as it's my primary work tool, though it remains unusual.
I intend to conduct further tests on our office machines tomorrow, comparing studio and game ready drivers, hoping to identify similar experiences among others.
We have been relying on uncertified drivers for years, never using quadro cards before. This issue appears to be new, and based on our tests, it doesn’t seem to be a driver-related problem. The testing shows inconsistent results, but one driver we tried caused the GPU to clock up during idle time with multiple monitors active—something unrelated to Autocad or Revit. This behavior is unusual because it shouldn’t increase when more screens are connected at different refresh rates.
And this is exactly WHY you do not run uncertified GPU's with Autodesk products. It is irrelevant that this has worked previously as it is not a supported configuration to start with. It's very likely that they have made changes to the product that do not play well with uncertified GPU's/drivers. And if that's the case you do not have a leg to stand on when complaining. What did Autodesk tell you when you contacted them? Part of what you pay for with your license is support when you need it.
My guy, who's complaining here?
This issue already has a quick fix—just reverting to a stable driver version.
I was looking to confirm if there were other users facing the same problem, to ensure it wasn't just a bug with my setup or the GPU I'm using.
I reached out to Autodesk via both support and forums, but haven't received a response yet.
Thanks for your reply, boss—your assistance has been really valuable.