Update #4: Raven is looking into the problem!

Update #3: Grab v1.3. I’ve fixed a bug that was preventing backups from being created. I also added detection routines to make sure the Singularity path in the registry is correct. Thanks to those who were brave enough to test the patch and find this one for me.

Update #2: v1.2 is available now. I’ve added an undo capability (basically a glorified file copy). It requires backups of the original files created by the program.

Update #1: So some testing revealed that v1.0 had a minor problem… minor enough to make it not work. I’ve uploaded v1.1 which seems to do the trick.

Inspired by this hacktastic workaround for Singularity’s texture streaming issues on PC, I decided to whip up a tool to automate all that byte-changing and hopefully rectify the problem.

I don’t have the game, but I’ve tested the tool as well as I can with dummy files. It should work, but I’m not quite ready to release this to the world at large. If anyone wants to give it a go, I’d love some feedback. Mainly on whether it does anything. Don’t worry, it makes backups of the files before modifying them so it’s easily reversed if something goes wrong.

What it should do is open up Coalesced_INT.bin and increase the texture streaming pool size to 400. It will then calculate the SHA1 hash for the new file and write it to Singularity.exe. That’s it!

Note: I’m sure Raven will get round to fixing this fairly soon… but then, I thought the same thing about Mass Effect 2′s processor affinity problems.

Download Singularity Texture Streaming Patch v1.32 [Playwrite]

And, if you’d like to do it manually, here are the instructions.
Singularity Texture Streaming Fix [DEAR WANDY]

No related posts.

* Fixed video hitching and crashes related to single core machines.

* Single core users may experience short periods of black screen that may last up a few seconds between level loads, cinematic transitions or movies.

* In rare cases, some single core users may notice dialog lines in certain conversations may be delayed up to a few seconds.

* Fixed an issue where it appears ammunition can be picked up, but can’t.

* Fixed an issue where all Codex entries were marked as ‘viewed’, even if the player chose not to view them.

* Fixed an issue where weapon icons are re-organized after downloadable content is used.

* Fixed an issue where pressing F9 after the mission completion screen reset Shepard to Level 1.

* Fixed an issue where remapping the right mouse button blocks camera control in the command HUD.

* Fixed an issue where remapping the ‘use’ command affects the decryption minigame.

* Fixed an issue where users were not prompted to restart when logging in to a different EA Online account.

* Fixed an issue where movies do not play in DLC.

* It is recommended that players reset their keyboard mapping to default values to ensure proper vehicle control.

* Added useful messaging during the ME1 save game import.

* Weapon icon for henchmen never changes from Collector Assault Rifle.

* Czech language – Issues with Czech localization (subtitles) were amended, all text was corrected and improved.

* Fixed an issue where the Mass Effect 2 launcher was being associated with files that have no extension.

* Fixed an issue where uninstalling the game under Windows Vista or Windows 7 might uninstall Mass Effect 1.

I’ve emphasised the fixes that relate to CPUs. While none of them explicitly state that the slow dual-core loading times (that MassAffinity nicely addresses) have been rectified, it’s not entirely insane to think one of the aforementioned singe-core tweaks may have done the trick.

Sadly, I haven’t found any conclusive evidence to suggest this is true. So far, I’ve only found this thread on BioWare’s Social Network, which seems to indicate that the slow load times are still present. It’d be great if any ME2 players out there could confirm whether they’re still encountering the problem, so I can update the original MassAffinity post.

On an unrelated note, I found the following bug hilarious:

Fixed an issue where uninstalling the game under Windows Vista or Windows 7 might uninstall Mass Effect 1

According to ME2 Technical Director Derek French, Windows itself is to blame for this nasty blighter:

That is actually a bug that Microsoft introduced in Vista and 7. We keep our uninstallers in a common location and if you don’t encase the full path to the Uninstaller in double-quotes, Windows will just pick another random executable from that directory and run it, instead of the executable the you explicitly entered. It is pretty crazy when you tell Windows to run ‘Uninstall Mass Effect 2.exe’ and Windows decides to run ‘Uninstall Mass Effect.exe’

Best. Feature. Ever.

No related posts.

Several requests for improvements prompted me to update the app to v0.2. Here’s a list of what’s new:

• Allows you to use an executable name other than the default (for those who have renamed MassEffect2.exe to enable anti-aliasing);
• Automatically detects your ME2 path via the registry;
• Shuts down immediately if ME2 is closed before MassAffinity can apply the fix (previously it would wait ten seconds);
• Added some graphics. Okay… one graphic;
• Added a “Help” button.

That’s it! The functionality remains unchanged, so no need to update if it’s working peachy already. No harm though if you do download it.

Download MassAffinity v0.2

No related posts.