• Registered: 2011-07-11
  • Posts: 2

Topic: CRASH WHEN LAUNCHING FIRST STRIKE

I have recently re downloaded bf 2142 so i could play this mod. I download FS and made it widescreen. But when i click launch it just goes into a black screen then is forced to close seconds later. I read on another forums post that reinstalling it may do the trick. So i reinstalled it but I am still having the same problem. 2142 is up to date with version 1.5 but i dont know what else could fix my problem so I am downloading 2142 version 1.51.

  • From: Manchester
  • Registered: 2006-11-03
  • Posts: 9,993

Re: CRASH WHEN LAUNCHING FIRST STRIKE

You need to download BF2142 1.51 as that is the latest version of the game, and the version that First Strike 1.5 is compatible with. I suspect that is the cause of the issue you were having if you were running it with only the 1.5 version of BF2142.

http://img.photobucket.com/albums/v600/TALON_TAW/TALONSIGNEWB-1.jpg
http://stats.fsmod.com/fssig.php?player=Talon-UK
http://stats.fsmod.com/sig/pilot.Talon-UK.png

FSDev| TALON's Website

  • Registered: 2011-07-11
  • Posts: 2

Re: CRASH WHEN LAUNCHING FIRST STRIKE

Thanks a lot. It was just a little confusing because on moddb a guy said you could play it with version 1.5 but i guess it was recently updated. It would be nice if it could say the version of FS alongside the version of 2142 on the home screen of this website. Thanks for the help!!! big_smile  big_smile  big_smile  big_smile

4 Reply by Renorick (edited by Renorick 2011-11-10 12:33:32)

  • Registered: 2011-11-10
  • Posts: 3

Re: CRASH WHEN LAUNCHING FIRST STRIKE

I am having a similar problem, I made sure that '2142 was up to date to begin with (tried patch 1.51 and it said I already had a newer[?] version) and it's doing the same thing. Yes, I did input the widescreen command shortly after my first attempt. Is it because I'm running on Win7-64bit?

EDIT: In addition, vanilla 2142 seems to run just fine, at least to the menu, haven't tried to load a server yet.

  • From: Manchester
  • Registered: 2006-11-03
  • Posts: 9,993

Re: CRASH WHEN LAUNCHING FIRST STRIKE

This is another possible issue with the 1.51 BF2142 patch, because there were so many versions it was a right mess ( you need the proper final version of 1.51 which is about 2GBs that is a good way of figuring out if you have the correct one or not), and in some cases you try to update to 1.51 and it tells you it is already installed and it is lying to you. One fix for this is to edit your registration manually so you trick it into believing you are running 1.5 (which you probably still are) and that allows it to update correctly. I believe there is a thread on this issue. I'll see if I cant hunt it down for you.

http://img.photobucket.com/albums/v600/TALON_TAW/TALONSIGNEWB-1.jpg
http://stats.fsmod.com/fssig.php?player=Talon-UK
http://stats.fsmod.com/sig/pilot.Talon-UK.png

FSDev| TALON's Website

  • Gwynzer
  • Gwynzer
  • Emperor Incarnate
  • Offline
  • From: Aberdeen, Scotland
  • Registered: 2008-06-24
  • Posts: 1,926

Re: CRASH WHEN LAUNCHING FIRST STRIKE

Installation order also matters

http://www.blackintel.org/firststrike/downloads

BlackIntel Game Leader
DUKE815: Teamwork's complicated.  I've found that ramming a Lambda with a Y-wing at full boost is most effective.

Gwynzer's Website

  • Registered: 2011-11-10
  • Posts: 3

Re: CRASH WHEN LAUNCHING FIRST STRIKE

FSDev| TALON wrote:

This is another possible issue with the 1.51 BF2142 patch, because there were so many versions it was a right mess ( you need the proper final version of 1.51 which is about 2GBs that is a good way of figuring out if you have the correct one or not), and in some cases you try to update to 1.51 and it tells you it is already installed and it is lying to you. One fix for this is to edit your registration manually so you trick it into believing you are running 1.5 (which you probably still are) and that allows it to update correctly. I believe there is a thread on this issue. I'll see if I cant hunt it down for you.


Just found out about the patch(er) acting stupid myself, came back to remove my post to find that you'd already responded. Thanks for addressing this, nice to have a mod team that addresses issues so promptly!