Need Help after Patching a clean install - NOW CTD!

[TheStig 39]

FIXED, but now another problem...

Edited March 28, 2009 by TheStig

[TheStig 39]

Fixed it... now My nuclear explosions don't work (all Enhanced Explosions packs don't work actually). I've already transferred all my weapons over again and ran the new Weapon Data program to update them to Oct 08 specs. Still no luck. Help.... :beta1:

[TheStig 39]

Ah I see! Once you patch up, you have to extract the MissileObject.INI in the Objects folder out of the catalog ( CAT ) file. From a previous thread I found Lexx's INI edits to input in.

 

Looks like I'm all good to go now!

 

 

Closing Thread.

Edited March 28, 2009 by TheStig

[Hairog 0]

I have to open this thread again because I have the same problem but you never said what the solution is. I get the same screen after I install and then try and patch to 10/09

[TheStig 39]

You need to goto the Microsoft Website and download an updated version of DirectX.

 

 

If you have Lexx's nuclear explosion effects, follow the directions below...

 

 

Open your MissleObject.ini and add this under the WeaponTypeList=WeaponData.dat part at the top.

 

 

 

[KT003Effects]

AirBurstEffectName=KT003

AirBurstSoundName=Nuclear.wav

GroundHitSoundName=Nuclear.wav

WaterHitSoundName=Nuclear.wav

ObjectHitSoundName=Nuclear.wav

CraterType=5

 

[KT030Effects]

AirBurstEffectName=KT030

AirBurstSoundName=Nuclear.wav

GroundHitSoundName=Nuclear.wav

WaterHitSoundName=Nuclear.wav

ObjectHitSoundName=Nuclear.wav

CraterType=5

 

[KT300Effects]

AirBurstEffectName=KT300

AirBurstSoundName=Nuclear.wav

GroundHitSoundName=Nuclear.wav

WaterHitSoundName=Nuclear.wav

ObjectHitSoundName=Nuclear.wav

CraterType=5

 

[MT003Effects]

AirBurstEffectName=MT003

AirBurstSoundName=Nuclear.wav

GroundHitSoundName=Nuclear.wav

WaterHitSoundName=Nuclear.wav

ObjectHitSoundName=Nuclear.wav

CraterType=5

 

[MT030Effects]

AirBurstEffectName=MT030

AirBurstSoundName=Nuclear.wav

GroundHitSoundName=Nuclear.wav

WaterHitSoundName=Nuclear.wav

ObjectHitSoundName=Nuclear.wav

CraterType=5

 

 

[LKT000Effects]

ObjectHitEffectName=LKT000

ObjectHitSoundName=Nuclear.wav

GroundHitSoundName=Nuclear.wav

WaterHitSoundName=Nuclear.wav

ObjectHitSoundName=Nuclear.wav

CraterType=5

 

[LKT003Effects]

ObjectHitEffectName=LKT003

ObjectHitSoundName=Nuclear.wav

GroundHitSoundName=Nuclear.wav

WaterHitSoundName=Nuclear.wav

ObjectHitSoundName=Nuclear.wav

CraterType=5

 

[LKT030Effects]

ObjectHitEffectName=LKT030

ObjectHitSoundName=Nuclear.wav

GroundHitSoundName=Nuclear.wav

WaterHitSoundName=Nuclear.wav

ObjectHitSoundName=Nuclear.wav

CraterType=5

 

[LKT300Effects]

ObjectHitEffectName=LKT300

ObjectHitSoundName=Nuclear.wav

GroundHitSoundName=Nuclear.wav

WaterHitSoundName=Nuclear.wav

ObjectHitSoundName=Nuclear.wav

CraterType=5

 

[LMT003Effects]

ObjectHitEffectName=LMT003

ObjectHitSoundName=Nuclear.wav

GroundHitSoundName=Nuclear.wav

WaterHitSoundName=Nuclear.wav

ObjectHitSoundName=Nuclear.wav

CraterType=5

Edited April 1, 2009 by TheStig

[vhill 0]

I would like to know how you fixed Nato fighter problem? I have same thing in SFP-1 with F-104G, When I change to USAF, the rest of the planes are German? Thanks Vince P.S. I have latest patch

[jomni 6]

I would like to know how you fixed Nato fighter problem? I have same thing in SFP-1 with F-104G, When I change to USAF, the rest of the planes are German? Thanks Vince P.S. I have latest patch

 

His first problem is about directX. New updates for the game need new directX versions. So you need to update.

His second problem is about .ini. Once patched, it makes it default so all mods will be gone.

 

Best way is to uninstall, install, and install the mods.

Nato Fighter installers point to different directions of the drive by default so you should manually direct them to the right folders.

[Hairog 0]

I have DirectX10 the newest version on a brand new machine. I don't think this is the problem.

 

I tried loading it from scratch twice now. The version off the cd works fine. The patch first of all wants to install in another directory and then gives me the error.

[Fubar512 1,350]

I have DirectX10 the newest version on a brand new machine. I don't think this is the problem.

 

That doesn't mean squat. You need still to install the latest DirectX user runtime, as per directions on ThirdWire's website:

 

============================

Strike Fighters 2 / Feb 2009

Readme File

============================

 

-----------------

Table of Contents

-----------------

 

1. Update Notes

2. Troubleshooting

3. Contacting Customer Support

 

---------------

1. Update Notes

---------------

 

If you have applied any mods to the game, please check the list

of updated files to see any data files you've extracted have

been changed. You must manually delete and/or updated these

files, or the patched game may not run correctly.

 

List of changes in this Update include:

 

Feb 2009

--------------------------

2. Troubleshooting

------------------

 

Troubleshooting Tips

 

Before installing the game, please try the following:

 

- Close all other applications.

- Verify that your system meets the minimum system requirements.

 

If you are experiencing difficulties in getting the game to run,

please try the following solutions:

 

- Obtain the latest drivers for your video and sound card.

 

- Obtain the latest version of Direct X from:

 

http://www.microsoft.com/downloads/details...6A-9B6652CD92A3

 

- Install the latest update for your game from:

http://www.thirdwire.com/downloads_sf2.htm

 

=============================================================================

Is that clear enough for you, or shall I try a larger font-size?

[Hairog 0]

Ha Excussssssssssssssssssssssssssse me. lol.

[jomni 6]

Ha Excussssssssssssssssssssssssssse me. lol.

 

so did it solve your problem?

Even if you have DX10 it does not mean you're updated.

And WOE needs dx9. It's not built for Vista and dx10.

Your dx10 maybe updated but not your DX9 (I believe they co-exist independently).

 

And make sure you get your directories correct.

Different install directory between CD and downloaded versions. The patch is following the new standard install directory used in the download versions.

Edited April 3, 2009 by jomni

[Hairog 0]

so did it solve your problem?

Even if you have DX10 it does not mean you're updated.

And WOE needs dx9. It's not built for Vista and dx10.

Your dx10 maybe updated but not your DX9 (I believe they co-exist independently).

 

And make sure you get your directories correct.

Different install directory between CD and downloaded versions. The patch is following the new standard install directory used in the download versions.

 

 

Thanks for asking. No it still doesn't work. I'll try again next week. I don't have time to fool around with it now. Thanks again for your help but dx10 is not my problem.

[Fubar512 1,350]

so did it solve your problem?

Even if you have DX10 it does not mean you're updated.

And WOE needs dx9. It's not built for Vista and dx10.

Your dx10 maybe updated but not your DX9 (I believe they co-exist independently).

 

And make sure you get your directories correct.

Different install directory between CD and downloaded versions. The patch is following the new standard install directory used in the download versions.

 

 

The DirectX user runtime is an all inclusive update for Winows 2000 & up. Try reading the release notes next time.

 

And I quote: "Brief Description March 2009

The Microsoft DirectX® End-User Runtime provides updates to 9.0c and previous versions of DirectX — the core Windows® technology that drives high-speed multimedia and games on the PC.

 

System Requirements

Supported Operating Systems: Windows 2000; Windows 2000 Advanced Server; Windows 2000 Professional Edition ; Windows 2000 Server; Windows 2000 Service Pack 2; Windows 2000 Service Pack 3; Windows 2000 Service Pack 4; Windows 98; Windows 98 Second Edition; Windows Home Server; Windows ME; Windows Server 2003; Windows Server 2003 R2 Datacenter Edition (32-Bit x86); Windows Server 2003 R2 Standard Edition (32-bit x86); Windows Server 2003 Service Pack 1; Windows Server 2003 Service Pack 2; Windows Server 2003 Service Pack 2 x64 Edition; Windows Server 2003 x64 editions; Windows Server 2003, Datacenter Edition (32-bit x86); Windows Server 2003, Enterprise Edition (32-bit x86); Windows Server 2003, Standard Edition (32-bit x86); Windows Server 2003, Web Edition; Windows Server 2008; Windows Server 2008 Datacenter; Windows Server 2008 Datacenter without Hyper-V; Windows Server 2008 Enterprise; Windows Server 2008 Enterprise without Hyper-V; Windows Server 2008 Standard; Windows Server 2008 Standard without Hyper-V; Windows Small Business Server 2003 ; Windows Vista; Windows Vista 64-bit Editions Service Pack 1; Windows Vista Business; Windows Vista Business 64-bit edition; Windows Vista Enterprise; Windows Vista Enterprise 64-bit edition; Windows Vista Home Basic; Windows Vista Home Basic 64-bit edition; Windows Vista Home Premium; Windows Vista Home Premium 64-bit edition; Windows Vista Service Pack 1; Windows Vista Starter; Windows Vista Ultimate; Windows Vista Ultimate 64-bit edition; Windows Web Server 2008; Windows XP; Windows XP 64-bit; Windows XP Home Edition ; Windows XP Media Center Edition; Windows XP Professional Edition ; Windows XP Professional x64 Edition ; Windows XP Service Pack 1; Windows XP Service Pack 2; Windows XP Service Pack 3; Windows XP Starter Edition; Windows XP Tablet PC Edition"

 

Hairog, the one I linked to is the one to use.

[Hairog 0]

Goodness is this why I recieved a warning.

 

I lost track of this post a long time ago.

 

Sorry if I offened you. I didn't mean to but DX9 or DX10 wasn't the problem. I'm not being snotty or nasty it just wasn't the solution sorry. I don't know of any other way to put it.

 

Thank you for your help and I'm sorry if I wasn't clear on what I was saying. It was not meant to diminish your help by any means.

[Fubar512 1,350]

If you recieved a warning, it certainly was not for this.