Update: compatibility agent did pop, told it the package installed correctly. I'm off to Omega.
Update 2: no crashes at any locations modified or added by Zaeed. Suggests that DLC interaction between multiple installs is more likely to cause crashes. Going to go for broke and remove all DLC currently installed and then install every DLC package without letting the compatibility agent reinstall with correct permissions.
Update 3: Compatibility agent popped for all packages that hadn't been previously installed except Shadow Broker. Checked registry for entries that referenced the DLC, but couldn't find any that weren't pointing to actual install executables, so not sure why compatibility agent wouldn't have popped for the DLCs i had installed and then deleted and reinstalled. Chose "installed correctly" when compatibility agent popped.
Now, bad news: experienced no crashes when I checked the locations connected with the DLC. Went to the start point for each DLC, checked all areas of Normandy, and visited Illium and Citadel (all places where crashes had either occurred for me or were likely to occur). This of course doesn't confirm anything-- the conflict causing the crash might be triggered in different locations or points in the DLC content that I don't have immediate access to. I will obviously update this thread if I do encounter the crash again later.
I think it's reasonable to mention preliminary conclusions: This crash has been shown to be reliable and consistent when it appears, causing crashes upon *every* attempt to load into the area it appears with. However, it is unreliable in where it initially manifests. For one player it might manifest on Omega when Zaeed's DLC is installed, for another player it might cause a crash at operation Overlord. We can also agree that this particular crash is tied to the DLC, as removing DLC can be a viable workaround if the player is willing to forgo using that DLC. It also seems to be more common when multiple DLCs are installed, so there may be an interaction between the various DLCs (so content from one DLC might only crash when it encounters another?). Finally, the reliability of the crash when it does manifest coupled with the fact that it doesn't always manifest in the same places for different players or clean installs (but very reliable when you simply reinstall the DLC or game without cleaning out old files, even to the point of crashing in the same exact place) suggests that it does indeed have something to do with the integrity of the installation and specific files within those installations (possibly a specific kind of file, but different files depending upon what happens during installation?).
I think it's a reasonable hypothesis that this has a lot to do with files left over from previous installs, since I didn't encounter the crash when I expected I would, though this hypothesis doesn't account for the crash appearing in the first place. Also, the hypothesis that there is a conflict during installation, probably involving UAC, can't be rejected because I wasn't able to reproduce the crash after the clean install. Had I been able to, I could have done another clean install with UAC disabled.
So, recommendations for people who do experience regular, consistent crashes with DLC: first step is to completely remove ME2 from your computer (saves and settings in your my documents folder aren't a problem, so keep them). Then go to the ME2 install location and delete any files or folders that are left over. Reinstall from disk or cloud. Install DLC either with UAC off (recommended) or by choosing to reinstall with recommended settings if the compatibility agent appears.
Modifié par AureateFlux, 14 janvier 2011 - 04:30 .





Retour en haut







