Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.


Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

User talk:Sigma 7

About this board

Not editable


Shattered Union memory fix

3
Garrett (talkcontribs)

I have made a preliminary fix for the memory issue. This applies the GlobalMemoryStatus2GB compatibility fix to ShatteredUnion.exe which should achieve the same result without affecting the whole system. I don't have this game to test, so let me know if this works and I'll finish it up and add it to the wiki.

Sigma 7 (talkcontribs)

The SDB file had no effect, and the compatability fix GlobalMemoryStatusLie also didn't change anything.

One thing I do know is that it's linked to entry 10141 in the language file, which can be used to trace what's going wrong for detailed debugging.

Garrett (talkcontribs)

Ah, so it's doing something even worse; well it was worth a shot.

Ageia PhysX workaround necessary?

3
Garrett (talkcontribs)

The older PhysX games I've tried (e.g. Two Worlds) run fine with the last legacy driver installed alongside the latest normal PhysX version without any tinkering; do you know if any games other than Infernal require the workaround described on Ageia PhysX?

Sigma 7 (talkcontribs)

The difficulty with Aegia PhysX was running the legacy and modern versions side-by-side, and manually adjusting drivers was the only option until NVidia released the legacy versions of PhysX. It was necessary in the past, as there was no official workaround. While the latest driver update fixes that, the page may still be required in case something messes up the game.

The proper test is running Two Worlds, followed by a modern game such as Metro 2033. Both of those require different versions of PhysX drivers that aren't compatible.

In case of Infernal, the official drivers still don't work, as it didn't include v2.5.2 even in the legacy pack. There may be other games like that - as such, the general workaround should still be visible in case something fails.

Garrett (talkcontribs)

Thanks for clarifying the problem and updating the pages. :)

There are no older topics