eburger68

toonces: The "disappeared trees fix" is exactly what it sounds like -- a workaround that removes the trees from the terrain so that they don't produce the ugly trees/clouds visual mish-mash that you occasionally see with the Dec2009 and later patch level. By default, however, the Expansion Pack does not install the "disappeared trees" fix. You have to take an extra step (outlined in the ReadMe) to apply the fix, which is part of a larger set of fixes/updates for installations running at the Dec2009 or later patch level. See step g) in the installation section of the ReadMe for instructions. Eric Howes

Stingray77: Why don't you apply it and find out? Eric Howes

Stingray77: No, you do not need to apply the DATA.INIs to a May2009b or Jun2009b install. The changes to the F-4 models post-date those patch levels. (If you did apply the new DATA.INIs to a May2009b install, you'd break the ailerons again.) To change the VF-111 tail decals, drop the contents of the attached ZIP in the \Decals dir of your SF2V Mod Folder. Eric Howes

Stingray77: No, the updated Expansion Pack files were built March 1. You posted March 4, and I produced the new DATA.INIs later that night. No, because what you're seeing is a difference in decals -- nothing to do with that DATA.INIs. Let me know if the new DATA.INIs fix the gear door hole. Eric Howes

Stingray77: Try the attached F-4 DATA.INI files. There was a minor change to the node names on the nose gear for the F-4s. I also updated a few other weapon station node names that changed as well. Eric Howes

Folks: SF2V Expansion Pack users can find an SF2V version of this package here: http://forum.combatace.com/index.php?app=downloads&showfile=10466 Eric Howes

verde13: I think the attached may be what you're looking for. Simply unpack the file(s) from one of the attached the ZIPs and drop it in the \Menu directory of your WoV Installation Directory or your SF2V Mod Folder. The file(s) simply restore WoV-style naming for mission types. Eric Howes

Stingray77: As I said in my post: Eric Howes

Folks: I have uploaded updated versions of all the main files for both the WoV and SF2V Expansion Packs. These updated versions collect all the fixes and updates that were released over several months. They also contain some updates to both terrains -- see below for more info. Dave, now that the "roll-up" versions of the Expansion Pack files are uploaded, would you please remove the following unnecessary files from the "Downloads" section? http://forum.combatace.com/index.php?app=downloads&showfile=10472 http://forum.combatace.com/index.php?app=downloads&showfile=10466 http://forum.combatace.com/index.php?app=downloads&showfile=10312 As mentioned above, these updated core files do contain some updates to both the North & South Vietnam terrains. Those who have previously applied all the updates through the "Feb. 2010 Refresh" can download a small 6 mb update to bring your installations current here: For SF2V Expansion Pack https://netfiles.uiuc.edu/ehowes/www/sf2v/SF2V_TerrUpd.7z For WOV Expansion Pack https://netfiles.uiuc.edu/ehowes/www/sf2v/WOV_TerrUpd.7z What follows is a list of the target areas added or updated: Added ----- An Bo POL Storage Depot * Xuan Bo Supply Depot * Mu Gia Transshipment Point * Ban Karai Transshipment Point * Ban Raving Transshipment Point * Lang Mo Transshipment Point * Haiphong Rail Yard Hanoi Rail Yard Thai Nguyen Rail Yard Yen Bai Rail Yard Thach Son Xa * Revised ------- Bai Thuong Cat Bi Dong Hoi * Hai Duong Haiphong Hong Gai Nam Dinh Nam Phong RTAFB * Ninh Binh Phu Tho Quon Lang * Son Tay Thai Nguyen Thai Nguyen Steel & Iron Works Uong Bi Vinh Son * * = both North & South Vietnam terrains Thanks, Eric Howes

Stingray77: Starting in late '65 or early '66, the Navy began retrofitting some of its aircraft with ECM jamming equipment and chaff dispensers under Operation Shoehorn. In SF2V and the Expansion Pack later Navy aircraft models have jammers and, in some cases, chaff. None have flares. No USAF fighters or attack aircraft have chaff or flares. No MiGs are configured to use chaff. I did read that a few pilots reported seeing MiG-21s dump flares during Linebacker, so I configured the MiG-21MF (which appears in 1971) for flares. None of the other MiG-21 models have flares. Eric Howes

Bob: By default there is no folder called "Mods." If you found a folder in the ThirdWire directory with the sub-directories you listed (Controls, Missions, Objects, Pilot Data, & Screenshots), then THAT is your "Mod Folder." We call it the "Mod Folder" because that's where third-party mods go, but it's not named "Mods" (unless you re-name it as FastCargo describes). From the Expansion Pack ReadMe: By default your Mod Folder should be located here: Windows XP: \Documents and Settings\[username]\My Documents\ThirdWire\StrikeFighters2 Vietnam\ Windows Vista: \Users\[username]\Saved Games\ThirdWire\StrikeFighters2 Vietnam\ Windows 7: \Users\[username]\Saved Games\ThirdWire\StrikeFighters2 Vietnam\ The "StrikeFighters2 Vietnam" in either \SavedGames or \My Documents is your "Mod Folder" by default. Eric Howes

Boostjunky: What AAA types are appearing improperly? Eric Howes

Boostjunky: You wrote: Ahh, then what you're seeing is mobile AAA, which the game mixes in with ground units in campaign. The WOV Expansion Pack GroundObject directory includes a number of mobile AAA types: 51CalPit BTR-ZPU BTR-ZU-23 KS-12 KS-19 KS-30 M-42 M163 M1939 M35_Quad nv_dshk S-60 Zil-157_ZPU-1 ZPU-2 ZSU-23 ZSU-57 If you'd like to make them stop appearing along with regular infantry and tanks, open the DATA.INI for each and change the GroundObjectRole to STATIC_AAA. Eric Howes

BoostJunky: Which campaign were you playing? Are the AAA showing up for both sides or only Enemy units? Eric Howes

stingray77: That should work. Eric Howes

Jomni: You asked: No, because the only thing that I've seen so far that might affect users is the cockpit position on the A-6A/B and the F-5B. And the solution there is simply to revert to the default COCKPIT.INI files that are already included in the Expansion Pack (if, that is, you were on the Dec2009 patch and applied the COCKPIT.INI files for those aircraft from the Jan2010 or Feb2010 Update packages). When I produce updated versions of the four base Expansion Pack files I will update the ReadMe to reference the Feb2010 patch instead of the Dec2009 patch. Maybe something new will emerge that needs attention, but so far I haven't seen it. Feb2010 patch level users should treat it like the Dec2009 patch level and apply the custom Dec2009 files, with the exception of the COCKPIT.INI files for the Intruders and the F-5B. Eric Howes

RichardG: There is no "new gold update." The four base install files for the SF2V Expansion Pack have not changed. TK released a Feb. 2010 patch for all SF2 titles. I released a "Feb. 2010 Refresh" for the Expansion Pack a week or two earlier, but that is not the same as the ThirdWire Feb. 2010 patch. If you already have the "Jan. 2010 Update" for the Expansion Pack installed, I would suggest applying the Feb. 2010 patch from ThirdWire. Start the game once to verify that it was applied properly. Then install the "Feb. 2010 Refresh" for the Expansion Pack. FWIW, I will be rolling all the various updates and refreshes for the Expansion Pack into an updated set of base install files, but I haven't done that yet. Eric Howes

Jomni: Oh, yes. I've encountered it. Without naming names, here's what I've dealt with after purchasing some of the payware I've bought over the years: - Poor flight models, which I had to either tweak myself (with what limited skills I have) or even replace entirely with working flight models from other, similar aircraft; - Packages that un-rared or un-zipped into a holy mess of files, with items misplaced or even missing, folders improperly embedded in other folders, etc., etc. Straightening out the mess to get working aircraft took some time. - Poor documentation, which is inexcusable. If I'm paying for it, it better come with a decent ReadMe at the very least. The lack of good documentation simply sends the message, "We don't care." - Poor design: with one model I purchased, an external underwing pod was built into the aircraft model itself, meaning that no alternate ordnance could be loaded on that pylon; - Configuration errors: with another model I purchased the developer had not only neglected to include the proper drop tanks for the aircraft, but worse (so I discovered after being told that the developer figured his paying customers could find suitable ones themselves on one or another download site) the DATA.INI and LOADOUT.INI weapon station numbering was mismatched, meaning that you couldn't even use third-party tanks without hacking the .INI files first. Again, if I'm paying you for it, it better work "out of the box." - Abysmal support: one payware developer I've encountered is notorious for telling his paying customers to go pound sand when they report issues he doesn't feel like fixing. In my favorite support "incident" of all time, he told another customer who reported a bug on a public forum, "There's a fix out there for this some place. Go find it." Absolutely stunning. - Abysmal QA: that same developer suffers from comically atrocious QA -- it seems that testing before release is haphazard or minimal in some areas. At the very least, he has a version control problem -- he often doesn't know what is in (or isn't in) the packages he released and is regularly surprised when customers report this, that, or the other is missing (or ask "what is THIS doing in here"). Now, I work for a software company myself. If it's software you're dealing with, you can expect bugs (and I do). But some of the payware developers I've encountered need to rethink their approach as well as their commitment to their paying customers. And, btw, there is plenty of payware out there of high quality, so please don't let the above lead you to believe that all payware developers are alike -- they're not. As one other poster noted, there are varying levels of quality in both the freeware and payware camps. Eric Howes

Folks: You may have noticed that TK has released a Feb. 2010 patch for SF2. I have done some quick testing with the SF2V Expansion Pack -- see my post here: http://forum.combatace.com/topic/53093-just-when-you-thought-you-had-caught-up/page__view__findpost__p__387780 I'll tell you right up front, though, the answer to the question is: no, the trees/clouds issue is not fixed. Eric Howes

Folks: You may have noticed that TK has released a Feb. 2010 patch for SF2. I have done some quick testing with the SF2V Expansion Pack -- see my post here: http://forum.combatace.com/topic/53093-just-when-you-thought-you-had-caught-up/page__view__findpost__p__387780 I'll tell you right up front, though, the answer to the question is: no, the trees/clouds issue is not fixed. Eric Howes

Folks: And the answer to the question amongst SF2V Expansion Pack users is: no, this update does not fix the dreaded trees/clouds rendering issue that reared its ugly head in the Dec2009 patch, so users upgrading to Feb2010 will need to continue using the Dec2009 "disappeared trees" workaround (found in the "Feb. 2010 Refresh" package for the Expansion Pack). It does, however, look like TK has backed out the changes made in Dec2009 to cockpit positioning (as he said he would). So, if you run into cockpit position problems with the A-6A/B and the F-5B, revert to the original COCKPIT.INIs for the those aircraft, which you can find in the 3rd and 4th .7z files of the base SF2V Expansion Pack download. In the quick testing I just did, I noticed no other issues or problems -- that's with the Dec2009 files from the "Feb. 2010 Refresh" package applied. I'm sure there are other subtle changes that will emerge over time, though. Eric Howes

Badfrank: Thanks for the info. Then it looks like SF2V standalone users have two options: 1) Delete the the A-4B and A-4B_65 from the \Objects\Aircraft dir in their Mod Folders 2) Reinstall SF2V as part of a merged install (SF2 first, then SF2V) There are three units in the Rolling Thunder campaign that use the A-4B_65, but all three have the A-4C_65 listed as Alternate Types. In the mean time I will add the A-4B and A-4B_65 to the "Optional" installs folder with appropriate instructions in the ReadMe. Best, Eric Howes

Badfrank: Is your installation also a standalone SF2V install? RichardG: I tested all A-4B variants on my various test installs of the two Expansion Packs last night and encountered no problems. In fact, we make almost no changes to the A-4B or the _65 variant in SF2V. So, my best guess is that the A-4B & A-4B_65 are not part of a default SF2V standalone install. You can test this by temporarily renaming your SF2V Mod Folder to something else, then starting the game and letting the game generate a fresh new Mod Folder. Does that Mod Folder contain an A-4B and A-4B_65? Eric Howes

Richard: Which version of the Expansion Pack -- SF2V or WoV? Which patch level of the game are you playing at? And which specific model of the A-4B? Eric Howes

File Name: WOV Air & Ground War Expansion Pack Gold - Terrain Update File Submitter: eburger68 File Submitted: 19 January 2010 File Category: User Made Campaigns ------------------------------------------ WoV A&G Expansion Pack: New Terrain Items for Older Expansion Pack Installations ------------------------------------------ This package contains an updated set of terrain files for users of the WoV Expansion Pack who installed the original Expansion Pack distribution from December 2009 and all the subsequent updates through the "Feb. 2010 Refresh." It was created to bring older Expansion Pack installations current with the "updated" Expansion Pack files that were released early March 2010 without forcing users to download the complete set of "updated" installation files. - If you downloaded and installed the Dec. 2009 version of the Expansion Pack and also installed the "Feb. 2010 Refresh," then this update package is for you. - If you downloaded and installed the Dec. 2009 version of the Expansion Pack but did NOT install the "Feb. 2010 Refresh," then you can upgrade to the most current version of the Expansion Pack *only* by downloading the complete, updated set of installation files. You can find the three part set of updated Expansion Pack installation files here: Part 1: http://forum.combatace.com/index.php?app=downloads&showfile=10281 Part 2: http://forum.combatace.com/index.php?app=downloads&showfile=10282 Part 3: http://forum.combatace.com/index.php?app=downloads&showfile=10300 - If you downloaded and installed the WoV Expansion Pack on or after 3 March 2010, then this update package is NOT for you -- the "updated" Expansion Pack files from March 2010 already contain all the files from this update. ~~~~~~~~~~~~ Installation ~~~~~~~~~~~~ To install this update, simply copy the contents of the \To_Install_Dir directory to your WoV Installation Directory. In other words, drag and drop the \Terrain folder to your WoV Installation Directory, overwriting as prompted. That's it. You should be good to go. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Target Areas Added & Updated ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Added ----- An Bo POL Storage Depot * Xuan Bo Supply Depot * Mu Gia Transshipment Point * Ban Karai Transshipment Point * Ban Raving Transshipment Point * Lang Mo Transshipment Point * Haiphong Rail Yard Hanoi Rail Yard Thai Nguyen Rail Yard Yen Bai Rail Yard Thach Son Xa * Updated ------- Bai Thuong Cat Bi Dong Hoi * Hai Duong Haiphong Hong Gai Nam Dinh Nam Phong RTAFB * Ninh Binh Phu Tho Quon Lang * Son Tay Thai Nguyen Thai Nguyen Steel & Iron Works Uong Bi Vinh Son * * = both North & South Vietnam terrains ------------- Eric Howes 4 March 2010 Click here to download this file