Does not work. Crashes after into. Please fix or refund,

This game is broken.

Does not work. Crashes after into. Please fix or refund,

I have fond memories of this game, so it's a shame that the Steam release lives up to its title. It locks up after the intro cutscenes, rendering the game unplayable.

I can get it to launch in compatibility mode for Win95, but only in demo mode (the game asks for the CD.) The developer appears to be working on a solution, as evidenced by the presence of two "launch-fix-" betas available in Steam under Deadlock>Properties>Betas. Neither resolves the launch issue under Windows 8.1 x64.

I'll update this review if the crash bug is fixed.

Don't buy this game does not work

Please fix this game. Crashes after intro.

This is a great game, but do not buy it on Steam. It is just broken and will not get past the intro video. If you put the game into Windows 95 compatabilty, you will be able to play the demo, but to play the game you need the CD-ROM

Edit: Looks like the game just will not play well with Steam.

#Discussions_QuoteBlock_Author

Here's an update from me:


I have requested numerous times to people to get this game down and we're getting there.

As for the fix, it's impossible right now and here's why.


Valve's system runs on a level that recognizes what architecture a machine is running on: 32 or 64-bit.

This gives me a unique problem for Deadlock. Deadlock seems to be a game where, if the user is on a 64-bit machine, it cannot find the registry entries that are put into the user's computer by Steam.

64-bit machines use a Wow6432Node directory in the registry and Steam on 64-bit machines writes to this place by default for everyone. The worse thing about this is that there is no way to get around this. I've discussed this with Valve and they say that there is no way to work around this behaviour. It's just the way it's built.

So since Deadlock 1 does not and cannot read from this Wow6432Node folder. It is technically impossible at this time for me to provide a fix for the game if you are on a 64-bit machine.

The thing that makes this worse is that it doesn't matter how many workarounds I try. Everything is run on a level where it will write to the Wow6432Node registry folder, its fullproof.


So whos fault is this?

Mine.

The week and month this game went out was very stressful. I was responsible for porting about 30+ games to Steam (double this if you include Mac versions and Triple this if you include Linux versions) over the course of 1 month or so and, in this case, I ended up missing something that was crucial to the functionality of the game. It shipped and it's all gone wrong. This I am sorry for.

So what is happening now?

I am trying to get things sorted out. I am going to see about getting your money back and am talking with Valve to see what I can do.

I apologize again for this, there isn't much more I can say but I am trying to get you your money back. Hopefully something will happen in the next week or so.

-Dan

It's a good game, which is why I bought it when I saw it on steam. Unfortunately, I can't recommend it buying it as it is now, since the game freezes as soon as the intro is finished.

Steam have ///FINALLY/// fixed the issue with the game not launching. Great game, just like i remembered it!

I have 848 games on this Steam profile alone, I have waited for Deadlock planetary conquest ever since I found it on sale at G O G. I patiently waited for it to come out on steam, I loaded up steam and was jumping for joy when I say that my wish finally came true....... ♥♥♥♥ u Steam... Game crashes after intro.
Game does not work.
Been looking for a way around the cd to enable retail version but no luck..
Please message me if anyone of you's get this fixed I missed this game so much.

for the last 5 to 6 hours i have been trying to play this game for some reason it will not load .... all i have been getting is the showing of the game the intro movie but after that it just says Deadlock not responding ...please help

One of the best games i've ever played, and it's nice to see it on Steam. Most reviews are right about this release being bugged (freezes after the opening cutscene), but it is not completely impossible to play and enjoy.

Altough the game is bugged, there are a few tricks to make it possible to play in Windows 7 and 8/8.1 (32/64 bits), even without compatibility mode.

The easiest workaround to make the game playable is to use a different WAIL32.dll, and, as so, use it to substitute the one that comes shipped trough this Steam release (which may be illegal).

If you've managed to do this, the game will actualy load to the point that you will be able to start a new game. Do this and after the map loads up you must disable the sound effects (you may let the music on if you want to, but the sound effects are the real issue). If you don't, the game may crash after sometime.

Of course I know this not the best solution, but it may save you some time and frustration if you already enjoyed this game in the past and was happy to see it on Steam.

A few crashes may happen even if you've managed to do all these steps, so be prepared to have autosave as your allie (or save by yourself from time to time).

One of the things that I missed so much in this release is the lack of network gameplay. Which is not impossible if you use the old CD version.

The best possible (and legal) solution to play this game in Win7/8/8.1 would be running Steam inside a virtual machine with Win XP.

If the crashes are something you are considering to workaround with, and have hopes that Retroism/Night Dive Studios (or who else may have the power to) do any proper fix in the future, buy this game.

If you have patience, and don't want to have headaches because of the possible crashes, don't buy this release yet and wait for a proper solution.

I bought this as part of the Classic Action Pack after reading the review posted that said Steam "finally fixed" the problem with the game not being able to read the WOW6432NODE folder, which is why it hangs.

The writer of that review is either a dirty liar or entirely unaware that they are running a 32-Bit version of Windows. Still does not work in x64, and per the other reviews, looks like it never will.