Hi,
compare it with two people working together on one project, but have different jobs to do.
In one case they speak the same language, but these two guys are doing their work quite slow. As they speak the same language the orders they give to each other are well understood and so clear for everyone.
The second case is now you have two guys that are specialists, they do their jobs great but they don't speak the same language. The result is that the orders they give are not clear to understand, there may be some misunderstandings or there may be that there are some questions to repeat the order with other words to make it understandable.
The first case is AutoCAD and the internal software-driver, hw accerator off (both are speaking "Autodesk-language") and as they have no GPU they are slow, yes. 😉
The second case is AutoCAD and a gc-driver, hw acceleration on. Now the language they comunicate is "DirectX", but AutoCAD doesn't use now the primary language "Autodesk-language", but DirectX with dialect A ..... and the gc-vendor uses not the primary (e.g.) nVidia-language, the vendor also has to use the foreign language DirectX with dialect B.
And as there are different version of DirectX + different interpretations of how these function do have to interface each other there may be more or less communication-problems. If you get a pairing of AutoCAD version, OS version and gc driver version that can communicate better you will have better success using the hw acceleration, otherwise turning it off has advantages.
Hope the story is not too long and the comparision between people and language to gc + drivers/interfaces is good to understand.
- alfred -
------------------------------------------------------------------------------------
Alfred NESWADBA
ISH-Solutions GmbH / Ingenieur Studio HOLLAUS
www.ish-solutions.at ...
blog.ish-solutions.at ...
LinkedIn ...
CDay 2025------------------------------------------------------------------------------------
(not an Autodesk consultant)