@ Stevedroid
Sorry the tool is behaving this way for you ... as you say it could be your Steam version ... the tool certainly doesn't behave erratically for me.
It was never designed to remove the pixelization some are experiencing ... it is just a bonus that some found it helped.
Oh I totally understand, but I'm really jealous of the people for whom it is removing the pixelization issue. :)
Again, I'm not totally sure how Racer_S's hacks work. My guess is they're either:
a) A memory hack that modify values in memory based on some offset that Racer_S figures out. Essentially an automated ArtMoney hack.
b) A DirectX wrapper that intercepts and changes calls to DirectX viewport functions.
If it's (a), it would be heavily dependent on having the correct memory offsets - and actually could cause big trouble if it's touching the wrong values. It's not improbable that the Steam version might have a slightly different layout in memory - slight enough that sometimes it modifies the correct memory values, but not other times.
I'd also throw out a guess that that's why people with the no-cd version are having troubles too. The executable is modified so the layout in memory might be a bit different as a result.
I'm not sure if there's a way Racer_S can track down the memory offsets in a more dynamic manner, or if he would simply need track down and add options for every different flavor of the game.
------
<
>: What version of the game do you have? Steam or retail or "other" (shame, shame)? Are you using a no-CD patch?
Are you sure the key isn't the step that you active the hack before you start the game? This had not occurred to me, I figured the hack wouldn't even intercept the key press if the game had not been started, but I'll have to try it out.