eburger68

Wilches: Thanks for the fix. Eric Howes

Wrench: Unfortunately, that doesn't change the visual appearance. As JSF_Aggie noted, what you're seeing is a side effect of the water shader being used: http://combatace.com...post__p__566148 The easy fix is simply to remove these two files from the the DS terrain folder: WaterNormal.dds TERWATEREFFECT2.FX The terrain will then revert to using the stock water effect and the custom WATERNORMAL.bmp that's in the folder. If one prefers the stock 3W water appearance, then remove the WATERNORMAL.bmp. Also, the specified minimum requirements for the mod are SF2E Mar2012, nothing else. Folks should change the CAT pointer only if they are running an install that includes SF2. Eric Howes

Talez: The default DATA.INI uses a catapult configuration that's a bit tricky, esp. with heavy loadouts. There's an alternate LHA-1 DATA.INI in the \GroundObject\LHA folder: LHA_DATA_alt.INI. That one uses a different catapult configuration. Rename the existing LHA_DATA.INI to something else, then rename the LHA_DATA_alt.INI to just plain LHA_DATA.INI. You should an easier time with the alternate DATA.INI. Eric Howes

Talez: You posted the following bugs: Frankly, I don't know that there's much we're going to be able to do about these -- at least not immediately. To address your points: 1. F-117 cockpit -- someone will have to take a look at this, should be fixable. 2. Ground terrain -- probably not fixable, as Wrench can't get the terrain to load in the Terrain Editor for further revisions. 3. Which AV-8 mission? 4. F-117 flights -- limitation of the game. 5-7. MiG-23 cockpits -- this should be fixable, but someone experienced with cockpits will have to do it. 8. Game bug -- happens with a number of aircraft with bomb bays; also you might see aircraft RTB with gear down. In other words, a lot of what you've pointed out is either not fixable by us, not easily fixable, or possibly fixable if someone with the right knowledge steps up to tackle the job. Eric Howes

Guys: The third hotfix for SF2E ODS has been posted -- see here: http://combatace.com/topic/71944-hotfix-3-for-sf2e-ods/ As before, this hotfix is cumulative, meaning that it contains all the fixes and updates from the previous hotfix packages. Eric Howes

Guys: The third hotfix for SF2E ODS has been posted -- see the first post of this thread. As before, this hotfix is cumulative, meaning that it contains all the fixes and updates from the previous hotfix packages. Eric Howes

CavtankerKyle: That would really be a separate project. No plans to expand the ODS mod, which is huge as it is, to take in another war entirely. Eric Howes

Ice Man: The A-10_78 uses the stock pit from SF2E: CockpitDataFile=A-10A_78_cockpit.ini If you have SF2E installed, you should have it. Paul, looks like the S-3B is having the same problem with the JPG skins as some of the C-130s. The fix is easy enough. Toro, from what I understand the bug you've encountered is a bug in the SF2NA code itself -- nothing we can do anything about. Eric Howes

Kokiak: WeaponDataTye=7 is the new cruise missile weapon type. We didn't convert the Harpoons, primarily because we weren't sure that weapon type supported targets other than ships. Eric Howes

Brennus: Does that mean the fix I suggested works? Eric Howes

Guys: The Hotfix package available for this mod has been updated to incorporate additional fixes and updates. See: http://combatace.com/topic/71944-hotfix-4-for-sf2e-ods/ This updated package includes all the fixes and updates from the first hotfix. Eric Howes

Guys: The Hotfix package in the first post of this thread has been updated to include more fixes and updates. It includes all the fixes and updates from the first hotfix. Eric Howes

Brennus: Try replacing the Campaign section of your Options.INI with this data: [Campaign] CampaignName=19910117 Desert Storm PlayerService=USAF PlayerUnit=336th TFS AircraftType=F-15E Difficulty=NORMAL Length=NORMAL AircraftSupply=NORMAL WeaponSupply=NORMAL LoadCampaign=FALSE CampaignSavename=DefaultCampaignSave The Options.INI is located in the root of your Mods folder. Eric Howes

Chauve: I just tested several squadrons off the Saratoga in the campaign. In all cases the carrier showed up just fine and I started without incident from the deck, not in the water. I should note that there's nothing special about the Saratoga. It uses the same carrier model as two of the other four carriers. Barring a config problem in the campaign DATA.INI or the ship's NAMES.INI (both of which I just checked), the only causes for your problem that I can come up with are these: 1) Installation error of some sort on your box. 2) Your PC having problems loading all the objects in the campaign, which loads a lot more than a typical Single Mission. It's also interesting that you had similar problems with other aircraft and carriers with the Mar2012 patch level. Most of our testing with the carrier battle groups was done on the Mar2012 patch level, though, and we never saw anything like you're reporting. Whatever the cause, it seems to be peculiar to your box or install. My recommendation would be to try a fresh reinstall of the mod itself. Eric Howes

Chauve: PureBlue is referring to another small issue that was resolved with the hotfix. What aircraft/squadron were you flying? Did you test this campaign before applying the hotfix? Eric Howes

Wrench: If you do manage to get the terrain loaded in the TE, add the rivers and other goodies, we would be more than happy incorporate it into the mod as part of an update. And, yes, you would get another shout-out in the ReadMe for the updated terrain. Best, Eric Howes

Wrench: The ReadMe clearly specifies that the credits in the new ReadMe cover only the new mods/updates/additions: The Mod includes the all the documentation for the original version, where you are credited, and explicitly points readers to it: Finally, the list in the new ReadMe does give you credit for something new that was incorporated. You are named there and are not, contrary to what you say, "conspicuously absent." Eric Howes

Jarhead0331: Try replacing the Campaign section of your Options.INI with this data: [Campaign] CampaignName=19910117 Desert Storm PlayerService=USAF PlayerUnit=336th TFS AircraftType=F-15E Difficulty=NORMAL Length=NORMAL AircraftSupply=NORMAL WeaponSupply=NORMAL LoadCampaign=FALSE CampaignSavename=DefaultCampaignSave Eric Howes

Folks: There is a quickie hotfix package available now to address the issues we are aware of: http://combatace.com/topic/71944-hotfix-4-for-sf2e-ods/ Eric Howes

Pfunk: Glad to hear you're enjoying it. Note that I just posted a hotfix package to address the issues we're aware of so far: http://combatace.com/topic/71944-hotfix-for-sf2e-ods/ Eric Howes

Paul: The problem with the transports is a known problem. We've got a fix that will be part of the HotFix we release. Eric Howes

Dave: You are a decadent man, my friend... ELH

dsawan: Product version for Apr2012 is 12.4.2.30. Product version for Nov2011 is 11.11.2.28. Don't know what the version is for Mar2012,but it must be higher than what you have for that .EXE. Note that patching with ThirdWire's update installers will not update/patch any custom .EXEs you've created. You have to manually recreate those from the latest stock .EXEs that get dropped in the patching process. Eric Howes

Dave: I'll take the strippers. You can have the penguins. I suppose we can split the beer with the rest of the team. Eric Howes

dsawan: The first thing that strikes me is that error message looks like the kind of crash you get when there's a mismatch between the version of the .EXE you're running and the underlying patch level. If I forget to re-generate a custom .EXE after applying a new update from ThirdWire, that non-updated .EXE bombs out with the kind of error message you're seeing. The second thing that catches my attention is the .EXE name, which has a hyphen and several spaces. Although Windows should be able to handle that file name (and the associated folder name for your Mods folder), I still occasionally see problems with those kinds of file and folder names. That's why I always avoid spaces in such names. Somewhere, somehow, that EXE is not finding what it needs or is finding the wrong thing when it runs. Eric Howes