. . . CMS . . .
. . .scene at startup, . . ..
according to tests i made the CMS doesnt seem at fault, i also did tests about the startup scene
just now i used process monitor to see step by step what DS4.5 is doing at startup
i see it do things expected,
but i also see it go through my entire F: drive , which is a data drive, not the system drive
it also seems to repeatedly ( hundreds of times ) set the values of the registry keys in the section
atkogl.dll is an AsusTek OpenGl dll (according to a cursory google search )
it’s not a solution but it may give clues
if i look in DS4.5’s main registry keys i see that many of the default directories ( example the import directory ) point to F:\
which is normal since that’s where i render and import/export the most
so, at this point my hypothesis are,
issues with versions of openGL32.dll
issues with how the nvidia card reports its OpenGL version
the main goal is probably to get DS to NOT want to scan my F:\ drive
i’m closer to the solution i think !
update, i read this in a forum
For others who find this thread, ASUS installs a custom opengl driver ATKOGL.dll,
which is apart of the Asus enhanced display driver, this must be removed via add remove
programs, when using any driver other then those provided by ASUS, even if you are using
the same asus card otherwise the OGL subsystem is rendered useless.