It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
It seems that a few people are experiencing crashes with this game.

If you think you've solved a crashing problem, please post details here to help other players.

------

I was getting pretty frequent crashes to desktop running under the glide video mode, but with no clear pattern to the issue.

I found that reducing the resolution in the nglide settings (by running nglide_config.exe) appears to have resolved my problem.

I originally had it set at 1280x1024 and the game appeared to run fine; but it was crashing a lot.

I tried reducing the resolution to one of the original options (640x480) and after playing for quite a while I had not had any crashes. I then tried increasing it to 1280x960 (a good match for 640x480, being exactly double in both directions) and thus far the game has seemed likewise stable for this mode.

EDIT:

Since writing the above, I have completed the main game and all of the Historical Missions.

The main game and (IIRC) the original sequence of historical missions (i.e. Marshal Training) remained completely stable. I don't believe I encountered a single crash at 1280x960 in these missions.

Some of the additional 'Handful of Missions' historical missions crashed on me a number of times, however. "Civil War" more so than the others, I think (although I've only just finished it, so other crashes are not so fresh in my memory :)

Because I encountered a Civil War crash even after setting the resolution to 640x480, I suspect that these crashes have nothing to do with resolution, so I remain fairly confident that 1280x960 is a good setting to use in general, and I believe (on my machine at least) is most likely as stable as 640x480.
Post edited April 15, 2015 by Shadowcat
I dont know if this is a crash, but i played the Last Level from the full version and i decided to run to the boss with fists. And when i arrived him, it seems that the game want try to load the video for the ending, but it doesn't come back witht the screen, i can still see the icon on the task bar from Win 10.

Outlaws made fun to play. It's like playing an animated cartoon.
Yesterday i have tried to use 1920x1080 from dgVoodoo2 2.55.4 and it was freezed and crashed, so we can't use high resolutions...
Post edited November 19, 2018 by FulVal
I've played through the entire game at 1440p, both as a resolution forced externally via nGlide (and Outlaw's glide render) and selected as the render resolution for Outlaws' Direct3D render.

Outlaws does not crash at high resolutions. Maybe some specific combination of settings you are using crashes it.
Post edited November 20, 2018 by ZellSF
avatar
ZellSF: I've played through the entire game at 1440p
Assuming that you mean 1920x1440 that is once again a precise multiple of the original resolution.

My experience was that an exact multiple of 2x (i.e. 1280x960) was as stable as the original 640x480, so it does not seem unreasonable that a multiple of 3x might also be stable, and it is unclear whether you have played the game using one of the resolutions which people have found to be problematic.

Outlaws does not crash at high resolutions.
Well we have clear evidence to the contrary, even if the exact causes might also involve other factors (video drivers would be a reasonable guess).

Maybe some specific combination of settings you are using crashes it.
You mean the exact same combination of settings which does not cause the game to crash if the resolution is different?
At least y'all can play it. I start the game, try and open a mission, the cutscene plays, and then...

"Outlaws has stopped working."

Every time. Haven't even been able to play it because it just keeps crashing.
FreelancerJosiah, if you haven't yet, try following the guide that I wrote in the "Guide for best 3D acceleration settings" thread.
avatar
FulVal: Yesterday i have tried to use 1920x1080 from dgVoodoo2 2.55.4 and it was freezed and crashed, so we can't use high resolutions...
Try downgrading to dgVoodoo 2 v2.54. I seem to recall that, in another thread, someone did that and stopped having the problem that he was having. v2.54 is also the version that I played through the whole game with in 1680x1050.
Post edited November 25, 2018 by jnisbet
avatar
ZellSF: I've played through the entire game at 1440p
avatar
Shadowcat: Assuming that you mean 1920x1440 that is once again a precise multiple of the original resolution.

My experience was that an exact multiple of 2x (i.e. 1280x960) was as stable as the original 640x480, so it does not seem unreasonable that a multiple of 3x might also be stable, and it is unclear whether you have played the game using one of the resolutions which people have found to be problematic.

Outlaws does not crash at high resolutions.
avatar
Shadowcat: Well we have clear evidence to the contrary, even if the exact causes might also involve other factors (video drivers would be a reasonable guess).

Maybe some specific combination of settings you are using crashes it.
avatar
Shadowcat: You mean the exact same combination of settings which does not cause the game to crash if the resolution is different?
I played until the sawmill at 1280x1024. Works fine.

The chances of someone sharing a problem that's specific to your computer and being able to figure out a solution for it is very tiny, if you want to play Outlaws at higher resolution you need to eliminate variables yourself.
Post edited December 02, 2018 by ZellSF
I've been having a few crashes and glitches myself.

There are two specific levels that make the game go belly up for me:

The River Basin (code OLCANYON) and the Sawmill (code OLMILL).

Each time it's mostly because of the waterfall rendering I'm guessing.
When the texture goes glitchy and turns solid white it's a bad sign and if I make the game draw more stuff in this direction with that on the screen it hangs up and crashes.
I can circumvent the problem partially by turning my back to the water and keeping focused on "stable" textures (as opposed to "animated" textures like the waterfall) but during the River Basin level it's very annoying, same when running around the mill's waterworks.

I've eventually managed to brute-force my way until the last boss, but those crashes are annoying and I can't pinpoint what screws everything up exactly given how flimsy everything seems to be in this game in terms of internal mechanics, not gameplay-wise.

I should give you the full rundown but here's what I already can remember:
Set the game on D3D HW in the Outlaws settings with 640x480 res.
Have checked all but the last two rendering options in Advanced.

I also use DgVoodoo 2.5.5 (maybe I shouldn't but it works with everything else I play, even Dark Forces II -although it's messy as all hell). I'll edit this post with more details once I've sorted out everything.
I think I put the res on max, added some FSAA, chose the closest D3D emulation possible, removed watermarks, I'll edit and add details.

I'm running it with Win10 latest version (I guess), on an Intel Core i5 7th Gen and an nVidia Geforce on my Laptop.
I have turned off DEP in Win Security a while ago, except for basic Win protocols because it prevented me from playing Unreal, Blood II and Shadow Warrior CR and a few other games.

But first I'd like to know if other people have experienced chain crashes on those two levels, or if they remember the original Win'95/'98 version having the same issues, because it seems to me those are levels that are painful for the engine for whatever reason no matter your fiddling. (Maybe full software mode would not suffer as much? I dunno).
Download dgVoodoo2 (from here: http://dege.freeweb.hu/dgVoodoo2/dgVoodoo2.html) and extract the latest version of dgVoodoo2 into the Outlaws installation directory. Copy all of the .dll files from the MS\x86 directory (yes, even if you're using a x64 operating system) to the root Outlaws installation directory. Double click on olcfg.exe

Under "Display Driver", choose Direct3D (HW Accelerated). Choose the highest resolution in available modes. Click on OK.

Create a folder named backup in the Outlaws directory. Move the following files into the backup folder in the Outlaws installation directory:

3DfxSpl.dll
3DfxSpl2.dll
3DfxSpl3.dll
glide.dll
glide2x.dll
glide3x.dll

Double click on the dgVoodooCpl.exe file. Click on the "DirectX" tab. Under Resolution, choose Max. Uncheck the dgVoodoo Watermark checkbox. Click on OK.

Double click on olwin.exe. Your game will work now.

I was unable to get the keyboard key mappings or mouse mappings to display in game. However, you can remap the controls using a program called GlovePIE (https://download.cnet.com/GlovePIE/3000-2084_4-77507726.html). My GlovePIE script contains the following (use similar syntax to remap other keys):

W = Mouse.RightButton
X = Space

I just use this GlovePIE script and click on "Run" in GlovePIE before launcKhing Outlaws to get it to apply (be sure to stop it when you quit the game).

You may be able to get the keyboard bindings to show by setting both olcfg.exe and dgVoodoo2.exe resolutions to 640 x 480. Then, change the resolutions back to the highest settings for optimial results. You may also have to use the 640 x 480 resolution trick to set some of the advanced options, as the mouse will not work properly on the menu screen at max resolution.

I hope this helps someone! I got the game to work on my AMD Ryzen 1700X rig in Windows 7 x64. Before doing the above, the game would just crash. I tried the latest version of nGlide as well, and that didn't help. You have to use dgVoodoo2!

By the way, controls can be hacked in the registry if you can't get the keyboard or mouse input screens to show. Settings are stored in this registry location:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LucasArts Entertainment Company\Outlaws\Users\Default User\ in MOUSE and Keys subfolders.
Post edited April 11, 2020 by own3mall