First Strike Forums — Issues with starting FirstStrike

Re: Issues with starting FirstStrike

null@example.com (Twigs) — Sat, 08 Feb 2014 23:02:40 +0000

Wait..the FS one is how big??? That aint right.

Do what AfterDune says above, copy and rename your BF2142.exe to FirstStrike.exe

Re: Issues with starting FirstStrike

null@example.com (Commandos) — Sat, 08 Feb 2014 22:13:31 +0000

Hey, I just got back... Not sure what you meant by Battlefield 2142 Pace, but the main exe for the vanilla is 6,967kb. While for FS it's 11,830kb
The game crashed as per usual even while running admin privileges, so that might not be it :L

Re: Issues with starting FirstStrike

null@example.com (AfterDune) — Sat, 08 Feb 2014 18:42:19 +0000

You might want to try this, this sure helped me back then .

1. Rename "FirstStrike.exe" into something else
2. Copy "BF2142.exe" and rename it to "FirstStrike.exe"
3. Launch First Strike and see if it works

If you launch First Strike through the launcher, it'll fire up FirstStrike.exe.

If you first launch BF2142, then through that launch First Strike, it'll use BF2142.exe - which works just fine.

Re: Issues with starting FirstStrike

null@example.com (Commandos) — Sat, 08 Feb 2014 18:00:12 +0000

Thank you, tho I'll check it tonight...
I'll report back as soon as I can

Re: Issues with starting FirstStrike

null@example.com (Twigs) — Sat, 08 Feb 2014 17:55:02 +0000

Thanks for understanding

Ok, lets try this then. Go to:

C:\Program Files (x86)\Electronic Arts\Battlefield 2142

And locate BF2142Pace and FirstStrike and let me know what the file sizes are for those two items. While you are in that directory, right click on the FirstStrike.exe, select properties and then the compatability tab. Select run as administrator and see if that helps.

Don't forget to tell me the file size for the exe files I mentioned above.

Thanks

Re: Issues with starting FirstStrike

null@example.com (Commandos) — Sat, 08 Feb 2014 17:48:11 +0000

Yes, I did all of that. I'd expect you to ask all these questions
Anyway, the problem was present even with the older launcher as I mentioned before, and it still crashed regardless of the resolution. I had it on my native 1366x768, even changed it to windowed 800x600, still same crash to the desktop.

Re: Issues with starting FirstStrike

null@example.com (Twigs) — Sat, 08 Feb 2014 17:43:25 +0000

Ok, so just to clarify, the problem you now have is that it crashes to desktop when you start using the new launcher?

Sorry for the questions, I just want to make sure I fully understand what is happening.

When you open the new launcher, have you clicked file, preferences and selected your native monitor resolution from the drop down list? then made sure you click save?

Re: Issues with starting FirstStrike

null@example.com (Commandos) — Sat, 08 Feb 2014 14:00:46 +0000

Hey twigs,
It was one of your posts "http://forums.fsmod.com/viewtopic.php?id=11072"
If you need any pics of the problem, do let me know...

Re: Issues with starting FirstStrike

null@example.com (Twigs) — Sat, 08 Feb 2014 13:15:40 +0000

Hmm. Ok, can I ask where you got the new launcher from? Is it the one linked to in the news post at moddb, or from a link I posted to help a few people?

As for the reported version, don't worry about that, just an oversight on our part

Issues with starting FirstStrike

null@example.com (Commandos) — Sat, 08 Feb 2014 10:40:46 +0000

Hey there, I went to moddb to get some help from the devs. The main issue came from the game both crashing and telling me that there was an error in the error log. The new update did not fix the issue with the error but the new launcher did. The problem now lies when I start First Strike, it starts like bf2142 with the black screen, except the game crashes to the desktop. I never had this sort of problem, and irregardless of the resolution (windowed or not) I cannot run the game. BUT... The amazing thing happens when I start the vanilla game (which run perfectly fine) and run FS from custom games. I noticed it's reporting the 1.55 version but I played yesterday on one of the servers, I even asked a fellow player for their version, to which he responded "1.6".
I hope this gives you some insight on my issue