Widescreen fixer broke again with the 168 update. Let us know if/when you can get the fix out DP! Thanks again :) On a positive note, let's hope they fixed the buggy IWNet Matching.
Another update?
I didn't even see a changelog for the last update. Hopefully this one comes with a changelog.
They're not breaking it on purpose... or "blocking" it.
You have to realize that I edit specific parts of the game's memory. When they edit the game and recompile it, it's going to have a different memory layout. This is going to cause my fixer not to work until I update it. It's just a side-effect of them updating their game.
It's a good idea not to try and use it when you know the game was updated, because there is a 99% chance that it's not going to work anymore, or crash, or possibility even trigger a bluescreen. :)
SP might work still because they only updated the MP executable. They are two separate .exe's afterall.
v1.65.0 is live [list]
[*]I have not had EB or whatever Infinity Ward uses to test this version. Use at your own risk.[/*:m]
[*]Added support for Wolfenstein v1.11[/*:m]
[*]Added support for Call of Duty: Modern Warfare 2 v1.0.168 (I'm just going to use the reported version in the game since there's no actual point releases)[/*:m][/list:u]
It can be downloaded here as usual:
http://imk.cx/pc/widescreenfixer/
v1.65.0 is live [list]
[*]I have not had EB or whatever Infinity Ward uses to test this version. Use at your own risk.[/*:m]
[*]Added support for Wolfenstein v1.11[/*:m]
[*]Added support for Call of Duty: Modern Warfare 2 v1.0.168 (I'm just going to use the reported version in the game since there's no actual point releases)[/*:m][/list:u]
It can be downloaded here as usual:
http://imk.cx/pc/widescreenfixer/
They're not breaking it on purpose... or "blocking" it.
You have to realize that I edit specific parts of the game's memory. When they edit the game and recompile it, it's going to have a different memory layout. This is going to cause my fixer not to work until I update it. It's just a side-effect of them updating their game.
It's a good idea not to try and use it when you know the game was updated, because there is a 99% chance that it's not going to work anymore, or crash, or possibility even trigger a bluescreen. :)
SP might work still because they only updated the MP executable. They are two separate .exe's afterall.
Yer i know dunno why i said that :P
Was my first thought though as the game just crashed instantly.
Thanks for the quick fix btw! Couple of hours on multiplayer with a single screen is just awful.
Well I don't know how well it will play with IWnet. It uses the same method that I used for CoD4 and CoD5, which PB doesn't detect. And from my experience, PB is better than any other anti-cheat solution online. So if PB doesn't pick it up, there's a pretty good chance that IWnet/VAC won't do any better. This is, of course, speculation, so it's still up to you if you want to risk it.
I'll look into getting in contact with IW and Valve and see about some kind of approval/test.
I'll try and elaborate on how it works and why I feel safe with it.
Most anti-cheat systems work by scanning specific ranges or items in memory. They look at cvars and settings and such. The main way they handle this is locked/unlocked values, but not specific values.
For example, a locked value might be a cvar setting for grass. The anti-cheat system will expect that value to be on. If anything modifies that value, it will trigger a kick/ban.
An unlocked value is something that gets freely modified by the game or user. There's no way that the anti-cheat system can know what a valid or invalid setting for it might be, so they don't scan it. An example of this would be the resolution of the game. The anti-cheat system is not going to scan that setting because it could be anything, and it would take too many resources to check for valid values constantly.
Another good example of an unlocked value is the aspect-ratio and HUD position. These aren't checked for specific reasons. The aspect-ratio isn't checked because it can be set by the user. The default choices may be limited, but it's a value that can be different per user. The HUD position isn't checked because the position itself changes based on the resolution of the game.
In other words, the values I edit should be fine. I make no modifications to the memory layout itself or anything that should bring on a violation. I simply read from a few addresses in memory and write to a few addresses in memory, overwriting a variable that gets freely modified by the client anyway.
Anyway, if it were PB, I'd feel safe telling people to run it, but I really have no experience with IWnet or VAC or whatever the anti-cheat system is actually called. I feel pretty confident that it won't trigger anything, but there's really no way to be certain for sure.
ok, the first time i have read your post, i have just understand the method of scanning... thanks to google translation for precision about your method.
modifying memory is something that i can't do. and found values to change is also too hard for me.
well... i'll stop my video project.
but really thanks to you dopfish for your widescreen fixer! widescreengaming community needs guys like you !
You'd think that with all this patching, they'd pull their heads out of their asses and address this issue.... I guess ignoring PC community must be a IW requisite now.
This is an Aspect Ratio fix for Multi-monitor gaming ... hence the section it's in.
A temporary FOV fix for SP can be found over here. You may be screwed for MP though.
