First Strike Forums — Great...it won't start

Re: Great...it won't start

null@example.com (Gwynzer) — Sun, 28 Dec 2008 01:34:18 +0000

go to your bf2142/mods folder, delete builds 1001 through to 1004.

Open your launcher, File -> Preferences, set your "Version" to 1000. Hit launch. See if that helps, that is basically re-updating from 1.4 normal.

Re: Great...it won't start

null@example.com (NaturalViolence) — Sun, 28 Dec 2008 01:14:40 +0000

I had first strike 1.3, which was working fine, then I used the launcher which automatically downloaded and installed 1.4. I am not downloading 1.4 full client off my shatner dsl, it will take wwwwwwwaaaaaaaaaayyyyyyyy to long.

Re: Great...it won't start

null@example.com (Gwynzer) — Sat, 27 Dec 2008 23:21:10 +0000

NaturalViolence wrote:

Nope, gives me the exact same error message as when it's not there at all "shaders.mesh not found" or something like that.
Edit: Can you email an IM client and address that I can use to reach you to cabin85laurel@hotmail.com? That might help this go faster if I can IM you, I understand if you can't for privacy reasons.

CLICK - Ask for Gwynzer or Nekosaur.

I know a few people with this problem. They ended up deleting their FIRST STRIKE folder in their bf2142/mods and installed 1.4Full again. Don't know what caused the error, nor why this fixed it, but it did.

Re: Great...it won't start

null@example.com (yultemsee) — Sat, 27 Dec 2008 23:10:58 +0000

try going to preferences in the first strike launcher and setting it back to 1000. also how did you get up to 1.4

Re: Great...it won't start

null@example.com (NaturalViolence) — Sat, 27 Dec 2008 22:25:39 +0000

Nope, gives me the exact same error message as when it's not there at all "shaders.mesh not found" or something like that.

Edit: Can you email an IM client and address that I can use to reach you to cabin85laurel@hotmail.com? That might help this go faster if I can IM you, I understand if you can't for privacy reasons.

Re: Great...it won't start

null@example.com (nekosaur) — Sat, 27 Dec 2008 21:51:07 +0000

what if you remove the zip file (back it up somewhere) and then rename the .zip.bak file to .zip. does vanilla 2142 work then?

Re: Great...it won't start

null@example.com (NaturalViolence) — Sat, 27 Dec 2008 21:35:09 +0000

OK...well both Shaders_client.zip and Shaders_client.zip.bak exist. So should I delete the .bak one?

Edit: I cut and pasted the .bak file to my desktop. Still has the same problem, no change. When I remove the .zip it gives me an error message saying it's not there (as I figured) so I put it back. It's not the drivers because it was working fine yesterday or the day before with build 1000 and I haven't changed the video card drivers since then, or any drivers for that matter. It has to be something that changed when the build was installed, I'll keep looking.

Re: Great...it won't start

null@example.com (nekosaur) — Sat, 27 Dec 2008 21:16:07 +0000

Hmm, so you can't start vanilla 2142 either? Go into the directory you've installed 2142 to, and go to mods\bf2142. Make sure that there is a file called Shaders_client.zip there. It might have been renamed to Shader_client.zip.bak. If so delete the .bak part. If it's not that, it sounds like there's a bigger problem than First Strike. Make sure you've got recent drivers for your GFX card and monitor (although if you have an nvidia card you might have problem with the latest drivers).

Great...it won't start

null@example.com (NaturalViolence) — Sat, 27 Dec 2008 20:44:15 +0000

At 3:30 EST on Saturday I booted up the first strike launcher to get ready to go on the community event (whatever your calling it). It updated to build 1004 from build 1000 after which for the first time ever first strike did not start (I've been using first strike since it first came out, literally two days after it came out). After it checks for updates the bf2142 splash screen comes up, the screen then turns black as it usually does, but then instead of the login screen coming up it just exits to my desktop. I did just get a new monitor so it's more likely that than the update. It's a 24" BenQ 1920 x 1200. I used this in the arguments to ensure compatibility: +menu 1 +widescreen 1 +szx 1920 +szy 1200. I'm gonna go try one last idea and if that doesn't work then I need all the advice you got. Damnit! Worst time for this to happen. And yes I did try exiting the launcher and restarting it, and doing force quit with task manager instead of normal exit as well. I'm going to see if it works without the arguments.

Edit: Nope, it does not work without the arguments either, I'm out of ideas for now. If anyone can fix this within the next 15 minutes I will build a temple so I can worship them every day .

Edit again: I just checked, it does the same thing with vanilla 2142 as well! With or without the arguments. hamsters damnit!