![]() This game is from 96, so don't expect high graphics or super depth, your smart phone has higher capabilities then the computers of that era. If you don't do this, after the intro, the game crashes. Ok, to the review, keep in mind that to play this game properly on Windows 7 and Windows 10 (I've tested both), you have to delete the file "WAI元2.DLL" in the Deadlock Planetary Conquest folder which generally is in "Program Files/Steam/steamapps/common/Deadlock" (It can be different if you choose a different installation path). No need for a bad review from folks who can't get it to work. This game does work for windows 10 if you follow instructions from one reviewer, which I will place here. So yes, I recomend this game to every strategy fan out there. The soundtrack is quite nostalgic, anyone here remember the song "Son, be a colonist"? xDĪnyway, in my opnion it's not game breaking. Maybe it's because I tested it on laptops, they don't have dedicated sound cards, or older hardware is needed, I don't know. At first I thought "Hey maybe it's my Windows 10 laptop, it's so new", so I tried it on an old 2006 Windows 7 laptop (Actually it's antique for today standards, but hey it still works pretty good xD), but no, still no music after the intro. I gotta tell you that for some reason, I don't have music ingame. Ok, to the review, keep in mind that to play this game properly on Windows 7 and Windows 10 (I've tested both), you have to delete the file "WAI元2.DLL" in the Deadlock Planetary Conquest folder which generally is in "Program Files/Steam/steamapps/common/Deadlock" (It can be different if you choose a different installation path, but the "/Steam/" path is the same). You can always check the ingame manual for help if needed. I've played this game for countless hours! I can tell you that at first I had no idea how to play this game properly, it took me a while to even realize how to end my turn! This game might be quite complex at first but you get the hang of it pretty fast. The first time I played this game was in 1997, it's one of the first games I've ever played on PC. Hopefully something will happen in the next week or so. I apologize again for this, there isn't much more I can say but I am trying to get you your money back. ![]() I am going to see about getting your money back and am talking with Valve to see what I can do. 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. The week and month this game went out was very stressful. Everything is run on a level where it will write to the Wow6432Node registry folder, its fullproof. The thing that makes this worse is that it doesn't matter how many workarounds I try. It is technically impossible at this time for me to provide a fix for the game if you are on a 64-bit machine. So since Deadlock 1 does not and cannot read from this Wow6432Node folder. I've discussed this with Valve and they say that there is no way to work around this behaviour. The worse thing about this is that there is no way to get around this. 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.Ħ4-bit machines use a Wow6432Node directory in the registry and Steam on 64-bit machines writes to this place by default for everyone. This gives me a unique problem for Deadlock. Valve's system runs on a level that recognizes what architecture a machine is running on: 32 or 64-bit. I have requested numerous times to people to get this game down and we're getting there.Īs for the fix, it's impossible right now and here's why. Originally posted by Saleck:Here's an update from me:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |