Jump to content
Sign in to follow this  
GodsLt

Other SF titles crash after Oct'11 patch

Recommended Posts

Hey guys, I installed the Oct'11 patch just recently. Since I mainly play on the SF2:V portion of the game, I thought everything was coming along just fine. However, when I tried to play SF2:I, or the NF4+ Expansion in SF2:E, or the Swedish expansion on SF2:E, or even the A&G Expansion on SF2:V all of the games crashed each time with a "Strike Fighters has stopped working..." message. I tried the "10 close cure", but that doesn't seem to be working either. Any ideas?

 

I'm running Windows 7 Home Premium 64-bits, 4Gigs of Ram, AMD Dual Core 2.3Ghz processor, ATI Mobility Radeon HD4530M 512Mb's dedicated video memory, and 500Gb's worth of HDD space.

Its a two year old HP Pavilion DV6 Entertainment PC.

Share this post


Link to post
Share on other sites

If you copied and renamed any of the .exe's for those (which most people do for NF4, SF2V AGXP, etc...), you need to delete those old .exe's and make copies of the new ones that were updated with the patch.

Share this post


Link to post
Share on other sites

Cut out the folder C:\Users\<you>\Saved Games\ThirdWire and paste it to a very safe location

 

then try the games

 

Actually....... try Malibus suggestion first!!

Edited by MigBuster

Share this post


Link to post
Share on other sites

Cut out the folder C:\Users\<you>\Saved Games\ThirdWire and paste it to a very safe location

 

...

 

But do this before you try my suggestion!!! Otherwise the game will overwrite the .ini files for stock aircraft when it runs the first time, which will screw up a lot of things in those modded installs.

 

So:

 

1. Copy and paste your mod folder (for each modded install) to a safe location.

2. Delete old exe's.

3. Copy and rename new .exe's.

4. Run the .exe's once.

5. Copy the folders from #1 back into your mod directory, overwriting when asked.

Share this post


Link to post
Share on other sites

actually, you forgot one vital step....

 

1. Copy and paste your mod folder (for each modded install) to a safe location.

2. Delete old exe's.

3. Copy and rename new .exe's.

4. Run the .exe's once.

5) Go into the game, select Single Mission, and fly one

6. Copy the folders from #1 back into your mod directory, overwriting when asked.

 

selecting and flying a single mission allows all the 'new' file to be built and placed

Share this post


Link to post
Share on other sites

Doesn't SF2 create files at the "Initializing" during startup?

Share this post


Link to post
Share on other sites

actually, you forgot one vital step....

 

1. Copy and paste your mod folder (for each modded install) to a safe location.

2. Delete old exe's.

3. Copy and rename new .exe's.

4. Run the .exe's once.

5) Go into the game, select Single Mission, and fly one

6. Copy the folders from #1 back into your mod directory, overwriting when asked.

 

selecting and flying a single mission allows all the 'new' file to be built and placed

 

 

I just checked and you do not have to fly any missions. You can simply start the exe. and then quit from the mainscreen. The folders and .ini files will be written.

Share this post


Link to post
Share on other sites

no crash reported here with the october patch

 

with win7 64bit

a core2duo E8400@3.28ghz

3go of ram

a radeon 4870 with 512mo

catalyst 11.2

Edited by Murphy'S

Share this post


Link to post
Share on other sites

i have to do the same that says Malibu, the AUG11 patch made the same...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..