Description

Giveaway via gift not key.
Good luck :D

Thanks for this giveaway! By WCrAzYW

8 years ago
Permalink

Comment has been collapsed.

:)

8 years ago
Permalink

Comment has been collapsed.

Thank you blur92
I wish you a good day ;)

8 years ago
Permalink

Comment has been collapsed.

I form Portugal. Good night!

8 years ago
Permalink

Comment has been collapsed.

ok, i am french 06h29 ;)

8 years ago
Permalink

Comment has been collapsed.

:)

8 years ago
Permalink

Comment has been collapsed.

thanks for sharing.

8 years ago
Permalink

Comment has been collapsed.

yes!

8 years ago
Permalink

Comment has been collapsed.

As far as I know, this will only work on 32bit rigs, NOT 64bit systems

8 years ago
Permalink

Comment has been collapsed.

Yes, since 1996

8 years ago
Permalink

Comment has been collapsed.

Well, obviously, but I've not seen ONE single person who got the Steam version working on their 64bit systems. I found it only fair to warn users so they have the knowledge of what might happen, or not happen in this case, before entering. The GOG version, however, seems to work fine. This is from the reviews page;

Originally posted by Saleck:
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

8 years ago
Permalink

Comment has been collapsed.

Interesting. I did not know anything.
Thank you for information.

8 years ago
Permalink

Comment has been collapsed.

It's cool, thought I'd better explain my comment, you seemed a little defensive and possibly like you were thinking that I was trolling or whatever :)

8 years ago
Permalink

Comment has been collapsed.

Obrigado pela chance

8 years ago
Permalink

Comment has been collapsed.

De nada :)

8 years ago
Permalink

Comment has been collapsed.

You do not have permission to comment on giveaways.