Working Stubbs Fix (nvidia/AMD) (Windows Vista/7/8)

[alec100_94]

I don't normally post in discussion forums, but after spending a fair portion of the last week trying to get this game working and finding the fix to be rather straight forward, I thought I would share it to avoid any future frustration.

This simple fix will work for both nvidia and AMD users (assuming you are using moderately up to date drivers) and does not require any additional software (like nvidia inspector), or outdated dll files (which I couldn't get to work). However if you are using an Intel Graphics Card Then this fix probably won't work.

Just browse to your Stubbs install directory (A Clean Install is recommended if you have tried any other fixes) and rename "stubbs.exe" to "CoDSP.exe" (without the quotes) now the game should run from "CoDSP.exe" regardless of what operating system or graphics card you have. And now the game works, and that is all most people will care. If you want you could write a simple script (called "stubbs.exe") to launch "CoDSP.exe" so the game still runs from shortcuts and/or steam (as shown here) but this isn't really necessary.

For the more technically minded among us lets go into the details of why this fix works. The reason the game didn't work in the first place is because of the amount of calls it makes to OpenGL extensions. For nvidia users you could use a tool (like nvidia inspector) to create a custom profile for the game and set an extension limit, which got the game running. However no such tool existed for AMD users, and having to download an additional piece of software was not an ideal workaround. So in the nvidia inspector we choose the extension limit that would be used for Call of Duty (and is therefore set automatically for that game). Now the extension limit does also exist on AMD cards, there is just no interface for it, AMD users will find a file called "atiogl.xml" in "C:\Windows" which essentially creates profiles for certain executables and sets OpenGL Extension limits (much like nvidia inspector). As this uses the same extension limit as Call of Duty, and Call of Duty already has an extension limit set in the config file (for both graphics card vendors), simply renaming the executable will make the graphics card think you are running Call of Duty and hence the right extension limits will be applied automatically. AMD users could also technically get this to work by editing the "atiogl.xml" file manually. Renaming the executable to any other game that uses that extension limit by default in both graphics drivers (like Return to Castle Wolfenstein) would also work.

Most people will probably figure this out themselves but if you get a OpenAl32.dll is missing error simply download it from here[download.dll-files.com] and throw it in the game directory. And if you have any version of atioglxx.dll in your Stubbs directory left over from any previous fix (or the installer?) then delete it, as it may cause the game to not start.

I hope this post is useful to anyone still trying to get this game to work, and saves people the hassle and time of going through dead end fixes, trying to find a solution (like I did).

[rodrrj]

Sorry to bother you but im having trouble with steam, it keeps saying that it cannot find the "Stubbs.exe" if i rename it "CoDSP.exe" is there a way around this?

[ItchyDani3l]

Originally posted by Jrod:

Sorry to bother you but im having trouble with steam, it keeps saying that it cannot find the "Stubbs.exe" if i rename it "CoDSP.exe" is there a way around this?

As he said, you can make a script that calls "CoDSP.exe" that is named "stubbs.exe".

Also @OP, I dont think this will work for people who... dont play call of duty.
You should give direction to people trying to play from all backgrounds.

[alec100_94]

Originally posted by Jrod:

Sorry to bother you but im having trouble with steam, it keeps saying that it cannot find the "Stubbs.exe" if i rename it "CoDSP.exe" is there a way around this?

The way I would do it is make a simple script in something like AutoIT and call it stubbs.exe and have it launch "CoDSP.exe" then steam should launch the script. I have written a script that can be downloaded here[www41.zippyshare.com] that does that for anyone who doesn't want to do it themselves (just put it in the stubbs directory). It is written in AutoITv3 and is incredibly simple, the source code is shown below. I didn't bother including this in the original post as I am not using the steam version.

#NoTrayIcon

Run("CoDSP.exe");

[alec100_94]

Originally posted by ItchyDani3l:

Also @OP, I dont think this will work for people who... dont play call of duty.
You should give direction to people trying to play from all backgrounds.

It does, I don't have (and have never had) Call of Duty, the profile for Call of Duty is hard coded into the nvidia and AMD drivers to automatically apply the extension limit. I have used it on 3 separate PC's (2 AMD, and 1 nvidia) none of which have ever had Call of Duty installed, and it works just fine on all of them. [/quote]

[ItchyDani3l]

Originally posted by alec100_94:

Originally posted by ItchyDani3l:

Also @OP, I dont think this will work for people who... dont play call of duty.
You should give direction to people trying to play from all backgrounds.

It does, I don't have (and have never had) Call of Duty, the profile for Call of Duty is hard coded into the nvidia and AMD drivers to automatically apply the extension limit. I have used it on 3 separate PC's (2 AMD, and 1 nvidia) none of which have ever had Call of Duty installed, and it works just fine on all of them.

[/quote]

Why would they do that? That makes no sense.

[alec100_94]

Originally posted by ItchyDani3l:

Why would they do that? That makes no sense.

Because It's a popular game and if they hadn't, trying to run it would cause a similar issue to this, where the game either wouldn't run at all, or wouldn't run properly (I haven't tested it so I'm not sure which one). Proof of it being hard coded is seen if you open nvidia inspector and search for call of duty (a whole bunch of games have pre-determined settings/tweaks) and then look at the extension limit, a similar profile (again with a bunch of other pre-set profiles) can also be found for it in the AMD xml file I mentioned in the original post. Looking through this was partly how I discovered this fix for it on AMD machines and also why I chose Call of Duty, because it is included in both.

[Sephiroth983-ThrilledGamersTV]

I can confirm it works, so Alec, you really made something amazing in figuring it out and fixing!
http://steamcommunity.com/sharedfiles/filedetails/?id=338467725
Congratulations.

[Tracido]

Dang, over and over, all I get is 998 error with this from a fresh install, does it have to be the C drive or something? (not a steam version this is 3 CD's and the 1.02 patch).

*EDIT: Alright folks IF YOU HAVE CD VERSIONS, YOU MAY NEED TO DELETE atioglxx.dll I had a fresh install and this was the ONLY FILE STOPPING the game. Holy flipping crap (widescreen fix no longer works but whatever, 1600x1200 I'll take it). Screenshot time. Thank you OP!

[alec100_94]

Originally posted by Tracido:

*EDIT: Alright folks IF YOU HAVE CD VERSIONS, YOU MAY NEED TO DELETE atioglxx.dll I had a fresh install and this was the ONLY FILE STOPPING the game. Holy flipping crap (widescreen fix no longer works but whatever, 1600x1200 I'll take it). Screenshot time. Thank you OP!

Yes atoglxx.dll is part of the problem as there are so many different versions of it. However I didn't think the installer actually installed that. So if you deleted the install directory after uninstalling that shouldn't have been there. And also the widescreen fix from here[github.com] works just extract to the game directory and change the x and y values in the config file to what ever resolution you want. However it looks a bit stretched, I think it looks better at 1280x1024 and using GPU Upscaling (from nvidia control panel).

[Sephiroth983-ThrilledGamersTV]

Originally posted by Tracido:

*EDIT: Alright folks IF YOU HAVE CD VERSIONS, YOU MAY NEED TO DELETE atioglxx.dll I had a fresh install and this was the ONLY FILE STOPPING the game. Holy flipping crap (widescreen fix no longer works but whatever, 1600x1200 I'll take it). Screenshot time. Thank you OP!

There are 2 widescreen fixes, one alters the savegame with hex editor, the other one adds 3 files to the game's directory

make sure to check:
1) http://www.wsgf.org/dr/stubbs-zombie-rebel-without-pulse
2) http://thirteenag.github.io/widescreen_fixes_pack#stubbsthezombie

[Scorch Hold]

Thank you so so so much! This works!
I salute you!

[Tracido]

Originally posted by alec100_94:

Originally posted by Tracido:

*EDIT: Alright folks IF YOU HAVE CD VERSIONS, YOU MAY NEED TO DELETE atioglxx.dll I had a fresh install and this was the ONLY FILE STOPPING the game. Holy flipping crap (widescreen fix no longer works but whatever, 1600x1200 I'll take it). Screenshot time. Thank you OP!

Yes atoglxx.dll is part of the problem as there are so many different versions of it. However I didn't think the installer actually installed that. So if you deleted the install directory after uninstalling that shouldn't have been there. And also the widescreen fix from here[github.com] works just extract to the game directory and change the x and y values in the config file to what ever resolution you want. However it looks a bit stretched, I think it looks better at 1280x1024 and using GPU Upscaling (from nvidia control panel).

It worked on 1920x1200, the one I had must have just not been functional, same files and all, huh, maybe just chance of where I grabbed it. I don't want upscaling, I want FOV, but no worries. I might try a few more things. Thanks again. :)

Also, I installed from CD's not steam, and I deleted even my save games when I removed it, as even radeon pro wouldn't fix it after all these years. It was just odd.

[the.chad]

Originally posted by alec100_94:

Originally posted by Jrod:

Sorry to bother you but im having trouble with steam, it keeps saying that it cannot find the "Stubbs.exe" if i rename it "CoDSP.exe" is there a way around this?

The way I would do it is make a simple script in something like AutoIT and call it stubbs.exe and have it launch "CoDSP.exe" then steam should launch the script. I have written a script that can be downloaded here[www41.zippyshare.com] that does that for anyone who doesn't want to do it themselves (just put it in the stubbs directory). It is written in AutoITv3 and is incredibly simple, the source code is shown below. I didn't bother including this in the original post as I am not using the steam version.

#NoTrayIcon

Run("CoDSP.exe");

Hi

I've completed the steps described in this post.
Still having the same issues I've had with every other recommendation to fix this game though :(

I can get as far as loading the game and surfing the menu (bodies and a few other items disappearing) but the game crashes as soon as I select the difficulty to start the game.

Could you advise of anything to fix this?

[Sephiroth983-ThrilledGamersTV]

Originally posted by the.chad:

Still having the same issues I've had with every other recommendation to fix this game though :(

I can get as far as loading the game and surfing the menu (bodies and a few other items disappearing) but the game crashes as soon as I select the difficulty to start the game.

Could you advise of anything to fix this?

http://forums.steampowered.com/forums/showthread.php?t=1990348
try here first

[the.chad]

Tried those steps previously, even tried a combo of the OP's fix and that but still not working :(

Something I didn't mention in my original post, it is running off my HTPC which has the Intel HD4400 running the graphics.

Still the same issue though, can load up to menu (bodies disappearing in background). Then crashing when trying to start a game.

Any other suggestions?