Basecamp very slow to load - FIXED

Former Member over 12 years ago

From day 1 I have found Basecamp very slow to load, to the point where it is almost unusable. On my previous system it took just over 2.5 MINUTES to appear, and on my current high-spec system (3.2GHz 6-core, 32Gbyte RAM) it still takes just over a minute.

Well, I've analysed what Basecamp is doing, and it's try to work with two files that aren't present. It tries 50 or so time for each, goes off and does something else, and comes back and tries again - over and over again.

It would appear that these are NVIDIA-related files called petromod_nvidia_profile_identifier.ogl and aurora.dll

By creating empty files with these names in the Basecamp folder, the load time has gone from just over a minute to 1.1 seconds!

0 Former Member over 12 years ago

It would appear that these are NVIDIA-related files called petromod_nvidia_profile_identifier.ogl and aurora.dll

Hmnnn, neither of these files is present on my Win7 system with Nvidia graphics and my load time is about 7 seconds. However, BC does do a bunch of odd drawing, placing items in different places and redrawing them several times before getting the screen right. This takes about 4 seconds.:confused:

Where is your BC folder that you created the empty files in?

Good job of detective work!!!:cool:

0 Former Member over 12 years ago

My guess is that this has little to do with BaseCamp as such.

I'd say your NVIDIA driver/software is looking for those files and that is holding up BaseCamp.

0 Former Member over 12 years ago

My guess is that this has little to do with BaseCamp as such.

I'd say your NVIDIA driver/software is looking for those files and that is holding up BaseCamp.

Even if it is the driver that's looking for the file, it doesn't necessarily mean that it has "little to do with Basecamp". While the NVIDIA driver is certainly being accessed by Basecamp, it's quite possible that Basecamp is passing something to the driver that is causing this, or that the driver is returning an error but Basecamp keeps calling it over and over again.

That's not to say that it isn't just a driver problem, but since it is only affecting Basecamp on my system and no other of the 100+ applications, it does suggest that it's a Basecamp/NVIDIA interraction problem.

LATER: One possibility is that Basecamp is asking NVIDIA to use an invalid custom display profile (possibly passing an empty index), and the NVIDIA driver is picking up the first profile filename in its nvdrsdb0 file (actually for Petromod, a geophysical program) and it has been told to look in the Basecamp folder. It can't find it, returns an error, and Basecamp gets it to try again and again.