SF2V / WOV Air & Ground Expansion Packs

[jomni]

You're going to end up bombing Vietnam most of the time anyway expecially when the MiG squadrons are decimated.

[verde13]

Go in the appropriate campaign's Data.ini, until you find something like this:

 

MissionChance[sWEEP]=90

MissionChance[CAP]=70

MissionChance[iNTERCEPT]=90

MissionChance[ESCORT]=90

MissionChance=0

MissionChance[CAS]=0

MissionChance[sEAD]=0

MissionChance[ARMED_RECON]=0

MissionChance[ANTI_SHIP]=0

MissionChance[RECON]=0

 

This is from one of the SF2E campaigns, but the format is the same. Find your preferred aircraft, and change the "MissionChance[CAP]=" to a higher number. The example above says that in that campaign, the particular aircraft will have a 70% chance of flying a CAP mission in the mission/role selection. Same thing for any other aircraft.

 

I know, i have the CAP at 90. Still no CAPs are generated, except for those sweeps who appear as CAPs thanks to Eric's fix.

 

You're going to end up bombing Vietnam most of the time anyway expecially when the MiG squadrons are decimated.

 

I expected this to happen, but so far both at Rolling Thunder and at Linebacker I the MiGs appear in greater and greater number as the campaing progresses, despite them getting slaughtered. In one mission my flight downed 7 for no losses only to encounter 15! at the next one in the same area some 3 days after.

 

Also 99% of my missions are strikes and escorts when i used to also get SEAD, armed recon and of course sweeps.

I have a feeling that something is off.

[orsin]

Hi everyone,

 

I ve done some quick test on the tree/cloud issue on Mar 2010 update and the answer is still: not fixed.

 

did anyone actually escalate that issue to TK? i cannot find a relavant bug report on TW forum...

 

 

Insky_orsin

Edited April 1, 2010 by orsin

[+eburger68]

orsin:

 

Yes, the issue has been raised with TK. I am a bit skeptical of whether he'll actually fix it, but he did say he would look into it.

 

Thanks for testing it with the Mar 2010 patch for SF2I.

 

Best,

 

Eric Howes

[dogshu]

Hi all,

 

I'm seeing a crashing bug with SF2:V and the Air and Ground expansion pack.

 

I'm running a merged SF2/SF2:V/SF2:E/SF2:I install with the March 2010 update. I have the V2.1 Final version of the mod installed, with the updated mission types installed. I did install the \For_Dec2009_Patch directory stuff as well as the ThirdWire MiG-17PF. Other than that nothing special is installed.

 

I'm doing the Steel Tiger campaign in the 429th TFS, flying the F-5A. The date is October 4th, 1965.

 

The problem is the game freezes when I exit a mission. I was able to exit the first mission of the campaign without problem. However, I have now twice tried to exit my second mission, and the game froze both times. The first time I hadn't landed when I tried to exit the mission, and just now I successfully completed a close support mission and landed at Bien Hoa. When I press "Esc" to exit the mission, it just freezes. When I alt-tab back to windows (I'm running Vista), windows tells me the program has stopped working.

 

Any ideas how I can fix this issue?

[+eburger68]

dogshu:

 

I've seen several reports from users of campaign freezes/crashes with Mar and May 2010 patch levels in the various SF2 titles. This problem does not appear to be specific to the SF2V Expansion Pack. Unfortunately, I don't know of any fix for this behavior other than to wait for the next round of patches from ThirdWire.

 

Eric Howes

[+X RAY]

Hi,after the SF-2I expansion,my SF-2VXP install is completely messed up,and can't start anymore if I click on the Icon!

Do you guys know why????Same for NF-4+

[GwynO]

Hi,after the SF-2I expansion,my SF-2VXP install is completely messed up,and can't start anymore if I click on the Icon!

Do you guys know why????Same for NF-4+

 

I think so! Was one of the program executables a copy of the default Vietnam exe renamed something like SF-2VXP.exe? That's what I do, so I have the default exe for each game, and a copy renamed for each major mod conversion. When the updater scans your Strike fighters folder, it only updates the default executables, so after it's done that, let your mouse hover over the program icon and you will notice the version number will be one higher for the default copies, but not your modded ones. Simple solution is to delete all the copies, then make more copies of the newer default programs, rename them to what they used to be e.g. SF-2VXP.exe and you should be back in game!

 

However, I don't know but I'm fairly certain that the updater will overwrite inis in your mod folder if there were any changes to default aircraft, objects and so on in the update, this will happen the first time you load the exe, no matter if you have renamed it.. just to be safe, it is best to comment out your mod folder FIRST like put an x in front of it e.g. SF-2VXPmods to xSF-2VXPmods , then load up your freshly renamed exe, play an instant mission, exit, go to Strike Fighters folder and you will see that the game has just made a new SF-2VXPmods folder with all the updates applied. Next you can just move all files from your xSF-2VXPmods folder to the SF-2VXPmods and you will be good to go. However, a simple overwrite from the old to new means that you could be overwriting the fixes put in for some of the planes e.g. decal placement and things like that , but keeping the updated inis as default might mean you loose some of the changes meant for the mod, the only way to get the best of both worlds is to role up the sleeves and copy all the modified data from your old on into the newer files line by line so that you only add what needs to be there for the mod while keeping the rest stock. If that sounds time consuming, believe me it is! I gave up on that a while back and now just do the lazy method of replacing new with old.

 

Hope that helps.

G.

[+X RAY]

I think so! Was one of the program executables a copy of the default Vietnam exe renamed something like SF-2VXP.exe? That's what I do, so I have the default exe for each game, and a copy renamed for each major mod conversion. When the updater scans your Strike fighters folder, it only updates the default executables, so after it's done that, let your mouse hover over the program icon and you will notice the version number will be one higher for the default copies, but not your modded ones. Simple solution is to delete all the copies, then make more copies of the newer default programs, rename them to what they used to be e.g. SF-2VXP.exe and you should be back in game!

 

However, I don't know but I'm fairly certain that the updater will overwrite inis in your mod folder if there were any changes to default aircraft, objects and so on in the update, this will happen the first time you load the exe, no matter if you have renamed it.. just to be safe, it is best to comment out your mod folder FIRST like put an x in front of it e.g. SF-2VXPmods to xSF-2VXPmods , then load up your freshly renamed exe, play an instant mission, exit, go to Strike Fighters folder and you will see that the game has just made a new SF-2VXPmods folder with all the updates applied. Next you can just move all files from your xSF-2VXPmods folder to the SF-2VXPmods and you will be good to go. However, a simple overwrite from the old to new means that you could be overwriting the fixes put in for some of the planes e.g. decal placement and things like that , but keeping the updated inis as default might mean you loose some of the changes meant for the mod, the only way to get the best of both worlds is to role up the sleeves and copy all the modified data from your old on into the newer files line by line so that you only add what needs to be there for the mod while keeping the rest stock. If that sounds time consuming, believe me it is! I gave up on that a while back and now just do the lazy method of replacing new with old.

 

Hope that helps.

G.

 

 

Thank u!I will give ir a try!

[dapit]

hi all :)

 

I'm probably too dumb, but I could not find the download link for this "very appealing" mod

 

vietnam enhanced sf2

 

Where is it ?

 

Does it exit anymore at all ?

 

cheers....

[+eburger68]

dapit:

 

You can find the four main install packages here:

 

http://combatace.com/files/category/407-sf-series-add-on-missions-and-campaigns/page__sort_by__DESC__sort_key__file_submitted__num__10__st__10

 

Please read the ReadMe before plunging in.

 

Eric Howes

[stingray77]

dapit: take care of following the instructions closely, but once you got everything running, YOU WILL LOVE IT!!! I promise...

[stingray77]

Eric: I just read about the "ejection seat"-effect here here (CA General Discussion). I am not fully sure, but I thing I have seen those effects in the Expansion Pack already, right?

 

If not, implementing that oneself (by "simply" putting those extra lines into the "Particlesystem.ini" and changing "AircraftFireEffect" accordingly) should not be much of a problem - what do you think?

[+eburger68]

Folks:

 

A July 2010 Update is out for the WOV & SF2V Exapnsion Pack:

 

SF2V Update

http://combatace.com/topic/52002-sf2v-air-ground-war-expansion-pack-v20-jul-2010-update/

 

WOV Update

http://combatace.com/topic/53706-wov-air-ground-war-expansion-pack-gold-jul-2010-update/

 

Eric Howes

[stingray77]

Eric, I just applied the July Update to a fresh new SF2V-(standalone)-install with the XP Gold v2.1 - and encountered some problem.

 

As you can see from the attached screenies, either I didn't get the F-8's tail fin displayed at all (blue except for the tail number and the rudder) or with double decals on it (small plus large and some of them inverted)...

I experienced that on the VF-111-Sundowners aircraft and VMF-235-Death Angels (same without those double decals here, but correctly displayed tail "from time to time" or "after some mission-time").

To me it very much looks like that "too-many-decals-on-tail-fin-problem".

 

I checked the most on the VF-111, a little less on the VMF-235 and just once on the VMF-333, which showed no such problems then.....

 

As it was applied to an "oob" fresh download and all according to the books (all /To Mods plus the Dec 2009-files of the Gold March applied, then /All Patch levels plus the Dec 2009-files from the July-update applied over that) I don't see that much room for mistakes maken....

 

Can you lead me to sth. else to check, or do you have some ready solution, maybe?

 

(I also saw some persisting prob with ground objects' shadows, but I still need to get screenies of those..... And this thing with the fin is far more unnerving.)

 

Your help is very much appreciated (again).

Thanks

 

Oliver

 

 

Here the first screenie, showing the blue fin:

[stingray77]

#2 - fin okay, but double decals - where does that red "flash" in the AK come from?

 

#3 - port side of fin is okay...

Edited July 14, 2010 by stingray77

[stingray77]

#4 here's the same aircraft (same flight just panned around the plane) starboard side - again that "double decal"....

 

 

 

#5 same aircraft, new mission, new set of double decals.....

 

and

 

#6 Death Angels-example...

 

Hope you can help. Thanks!

[+eburger68]

stingray77:

 

There were no changes to the F-8s in the recent update -- none. Moreover, I don't get any of those problems with VF-111 or VMF-235.

 

You could try reverting to the stock DECALS.INI on those skins (USNGrey4, USMCGrey3) -- rename the DECALS.INI to DECALS.OLD.

 

If that doesn't solve the problem, then the cause of it lies elsewhere -- perhaps with your viedo card settings.

 

Eric Howes

[stingray77]

Hum, not really the answer I was hoping for.... But anyhow I wondered, where there THAT change might have come from...

 

So I'll try out reverting to stock decals and/or going through the whole install once again.

 

But HOW could such a thing come from a viedo-card settings??? Btw. I'm running GeForce 8600 GSon latest drivers (257.21).

 

Thanks for answering so fast again.

Edited July 14, 2010 by stingray77

[future_tuskegee_airman]

Thank you so much for this awesome mod! It's intense and a wonderful addition to SF2:V!

[stingray77]

Eric, yes - renaming the decals.ini (into DECALSold in my Vista case - I don't know if I can also change the .INI-endings...) seems to do the trick.

But I feel, I'm losing some of the XP's details. Do I? (Well, what exactly AM I doing by this renaming???)

 

As said: all that's on a clean new re-install with a virgin application of the XP v2.1 and the July update to it...

 

But thanks in any case... Will keep on "checking".

 

Oliver

[+eburger68]

Stingray77:

 

By renaming the decals.ini you're reverting to the stock decals.ini provided in the .CAT files, which means means you're losing the serial numbers on the vertical stab supplied by the Expansion Pack version of the decals.ini. If that's what it takes to fix it, then that's what it takes. I have no other solution to suggest.

 

Eric Howes

[stingray77]

Yeah, fully understand, Eric... (But: what a pity!)

 

Thanks anyhow - for the outstanding XP and all your patient support.

 

Oliver

[stingray77]

Just in case sb. else runs into some similar prob or wants to re-check:

I just tried all F-8 versions (on which only this seems to occur) - the F-8H 69 and J 69 check out allright. All others seem to have that decal-issue.

And it seems as if a second smaller decal appears on the fin, too (or makes it turn blue if too many decals to handle)..... And it seems to be the decal of the leader, irrespective what squadron:

[stingray77]

Sorry, for bothering you so long with this! Eric, you were right with your very first answer: yesterday I put my NVIDIA drivers to the lates level (I missed an update before), and everything seems to be fine again now..... At least F-8C and D models (incl. _66's) checked out fine for several squadrons (incl. VF111, 211, VFMA 235)......