Swordsman422

Wrench, the decals folder is in the objects/decals/A3D-1/skinname/d folder. So the pathway checks out. When I install a jet from SFP1 into SF2, I take exactly those steps to install the skins and decals. It works every other time but this one. Even if I use default decals such as USNAttacknum, nationname, insigniafusel, etc, nothing shows up on this bird. And it obviously does for everyone else or there would already ave been a topic. It's a shame, too, because it's such a well done model and I use it a lot in campaigns. Edit: Just tested it in SF1 and the decals show up fine, but not in SF2. I have NEVER had problems with skins translating between titles before.

My understanding of the Mission Success thing is this: you are awarded a mission success but NOT the full points for it if you don't kill the target yourself. It isn't that you will fail, you just won't get all the points for killing it. No big in my book. I actually would like to get promoted less quickly. Being able to command your whole flight to kill a target, now that's a command I've needed for a long time.

Hey, guys I just bought the entire SF2 series and am in the process of learning the new modding system. However, I'm having one small problem with the terrain [AllowedDates] entries. I know there is a sticky on this already, written by Wrench, and it's really good... but it's not working for me at all. I've tried it on both stock and 3rd-party terrains to no effect. The date selection is locked at 1982, which means I'm stuck with aircraft intro years for anything afterwards. I can usually figure this out but I'm stumped. Here's an example of my Desert.ini [Terrain] TerrainFullName=Desert DataFile=desert_data.ini TargetFile=desert_targets.ini TargetTypeFile=desert_types.ini MovementFile=desert_movement.ini NationsFile=desert_nations.ini LocationMap=desert_Location.bmp WaterMap=desert_Water.bmp BriefingText=desert_briefing.ini DogfightFile=desert_dogfight.ini DogfightOnly=FALSE GroundObjectTexture=tan [Map] FilenameFormat=PlanningMap%d.bmp Width=1000000.0 Height=1000000.0 NumZoomLevels=3 [WeatherChance] ScatteredChance=50 BrokenChance=25 OvercastChance=4 InclementChance=2 [AllowedDates] StartDate=1948 EndDate=2050 Anything wrong with that? I'm using Win7 and have the entire Sf2 series plus both expansions merged. The only game MODs I've installed aside aircraft thus far are the SF2V Ground War expansion to the most current update and GreenHell3. Knowing my luck, I'm the only person with this issue, but I figured I'd take a shot. Thanks.

Awesome! That trick worked. Thanks!

Fingers crossed here!

Okay, weird thing. Lately when flying in SFP1, I've noticed that there are few if any air defense systems even with the air defense settings at heavy. There might be a few guns here and there, but there are NO sams to speak of at all. And there are occassions when I'll fly a SEAD mission, get to the target area, to find no air defenses present. This primarily occurs over the stock terrain. I have checked the service dates of the various SAM and AAA units to make sure I'm not flying out of date. I've made sure that the Target_types and Targets .inis allow for these units and have them placed. I have made sure that the SAM_LAUNCHERs are called to in the types file and that the units I would like to show up are thusly labled. But unless an object is specifically named in the target types file, especially a SAM launcher, it will not show up on the terrain and will not be targetable unless it is a primary target. This happened suddenly without me altering any files or installing any MODs. I REALLY would like to not have to reinstall, patch up, then toss my MODs back in one at a time to see who is the problem child, so if anyone has any ideas, I'd really love the help.

Semi-resolved this problem. I realized that I'm used to flying user-made terrains where there are large numbers of air defense batteries. The basic SFP1 Desert terrain was never widely populated. I altered some of the operational dates of the air defense weapons and then just added several new SAM sites and AAA pieces in the various terrain areas. Aircraft flying on the wrong side of the boarder are now liable to get a facefull off unhappiness in the way of flak and SAMs.

Modern period. Mainly the late 80s onward. I have SAM systems that see service until 2040. I was so certain that this was the problem, that I modified the basic SA-2s even to serve that late. The object files and so on are all intact, too. My old computer had a bad habit of just eating data out of the objects folders, but this new one doesn't. I haven't tested it in the 60s and 70s yet and won't until this evening, but I think it will persist into the earlier time periods.

I say run. Run like hell. Very fast. In the opposite direction.

I don't think we're looking at an Iran-Iraq conflict because it falls outside the timeframe TK likes to play in. Plus, he gave a major hint on the Thirdwire Facebook that while the pictures of the Tomcat (wearing US gull grey-over-white) was on the SF2:I terrain, the campaign in the next game would take place further north. I think we're looking at a potential North Cape situation that is a stand-alone expansion of the campaigns we get in SF2:E. Either way, there's a Tomcat in that box. I'm buying on day 1.

Okay, so I kinda already announced these on the Southern Watch Campaign thread in the campaigns forum, but I suppose I'll post them here, too. These are WIP skins for the Mirage Factory's awesome F-14A. Markings are for VF-41, the Black Aces, during their final deployment including Operation Enduring Freedom and VF-211, the Checkmates, for their final deployment in the tomcat supporting Operation Iraqi Freedom Phase 2 and Operation Enduring Freedom Phase 2. Full markings including CAG and CO birds will be included in each set based on Paul Nortness's excellent decal layout. BuNo's and Modex numbers will be accurate thanks to Osprey Publishings F-14 Tomcat Units of Operation Enduring Freedom and F-14 Tomcat Units of Operation Iraqi Freedom, bot by Peter Davies (excellent books, BTW). There will be two sets of Modex numbers, one in numerical order and another in random order for campaign use. VF-41 VF-211 Still a few kinks to be worked out, but they are 99% ready for prime time. Thanks for looking.

Glad to help any way I can. 1st reference for carrier deployments for me has always been the Navysite.de website. From here, you can look at carriers by clas and read a list of their deployments and what CVW was carried along with. I do believe OSW was kicked off by USS Kitty Hawk and CVW-15 in late 1992 or early 1993. Any Tomcat squadrons you want skins for that don't exist yet, I can do them, but I'm limited to Tomcat squadrons. Other tacjets will have to be covered by someone else. Just let me know what you need.

This would be very interesting. I can see it as a low intensity campaign stretching from around 1993 to early 2001. The DS map would have to be modified so that the mobile air defense units and SAM traps would be active for a while and then gone, while a new one was active somewhere else. Also, ground transport routes would be limited to below the 33rd. The map would only be usable for this campaign and MAYBE a Desert Fox mini-campaign in 1998 and/or slightly intensified OSW with Response Options post 9/11 and before invasion in 2003. Carrier wings and ships would also be frequently cycled through and replaced, with very little overlap. I can offer assistance in 2 ways; 1) I can tell you on the Navy side what carriers were there when, for how long, and what air wings and squadrons were aboard for the whole run of OSW and 2) I can skin nearly any Tomcat squadron you want. May I submit my resume with these two WIP images: VF211 Checkmates Last Tomcat Cruise VF-41 Black Aces Last Tomcat Cruise

Had a problem similar back in September. PC had a nasty bug come on it. In the process of fixing it one day, the motherboard went arcs and sparks. Harddrives were okay, though. Went out that week and bought a brand new box. I wasn't comfortable with the idea of Win7 and wasn't sure all my stuff would work on it. You can imagine I was delighted that for the most part, Win7 is XP on steroids. It's got all the pretty features of a Mac OS with the functionality and compatibility of Windows. I have WOV and SFP1 working flawlessly on 7, so at least you should have zero probs there.

I haven't tried that terrain, but some of the add-on terrains have trouble with certain aircraft carriers. You might try a different carrier. Another option is that you might have something wrong in your text entry that has the aircraft launching from the ship. Post that entry here as well.

Before we proceed, I need some information: What version of what game are you using? What terrain are you using? Post the squadron and aircraft carrier entries from your campaigndata.ini and also post the carrier station entry from your terrain_targets.ini Once we have that information, it'll be far easier to pin down the problem and walk you through fixing it.

Okay, so after a prolonged absence I've finally come to my senses and am getting back into the TW sims. Never one to be satisfied with campaigns as they are, I'm always finding excuses to add carriers to them. Anyway, I'm having some extremely abnormal issues with the ships in SFP1; the player aircraft based in them will all spawn in a lump on the deck and explode. One would think this is uniform for all carriers on all terrains, but it is not. On some terrains, some carriers will work fine and others will not. Example: In the Taiwan terrain, DO's CVN-75 and Beer's Forestall will be okay, but the problem occurs with every other carrier, even the stock ones. And in the Madagascar terrain, the Forestall will be troublesome while the Kitty Hawk is not. Generally the CVN-75 model is the only one that tends to be universally compatible. The only terrains not giving me migraines are the stock Desert terrain, Iraq, and Vietnam. I thought I was just going to have to be choosy about which units are in a terrain map... until I met Cuba. No carrier of any class will function for me in this terrain. Jets blow up on it no matter what I do it seems. I've not ever seen this complaint before (search function rendered nothing) so it MUST be something I'm doing wrong. I've read the knowledge base entries on the subject and followed them to the letter (plus I've been doing this for long enough that I'm not a stranger to the process) and have had no success. Here are my data entries: From the campaign.ini air unit data omitting weapons entries [AirUnit004] AircraftType=F-14A UnitName=VF-41 Black Aces StartDate=08/28/1999 ForceID=1 Nation=USN CarrierBased=TRUE CarrierNumber=71 DefaultTexture=USNVF41 StartNumber=4 BaseArea=Delta Station RandomChance=100 MaxAircraft=11 StartAircraft=11 MaxPilots=19 StartPilots=19 Experience=100 Morale=100 Supply=50 UpgradeType=NEVER MissionChance[sWEEP]=50 MissionChance[CAP]=50 MissionChance[iNTERCEPT]=30 MissionChance[ESCORT]=50 MissionChance=60 MissionChance[CAS]=60 MissionChance[sEAD]=10 MissionChance[ARMED_RECON]=60 MissionChance[ANTI_SHIP]=05 MissionChance[RECON]=20 Carrier unit data [CarrierUnit001] CarrierType=CVN75 CarrierNumber=71 UnitName=USS Theodore Roosevelt (CVN-71) DefaultTexture=CVN-71 ForceID=1 Nation=USN BaseArea=Delta Station NumSquadron=10 BaseSize=MEDIUM Experience=100 Morale=100 Supply=100 Intelligence=100 UpgradeType=NEVER Terrain targets.ini entry for this station [TargetArea094] Name=Delta Station Position=368282,453825 Radius=5657 ActiveYear=0 Location=1 Alignment=FRIENDLY CarrierStation=TRUE I'm having the same problem in the OTC campaign as well, and I cannot figure out where I may be going wrong. I am secure in the knowledge that these MODs are quality and that the creators would not have released them without knowing they work, so this is MY fault, I just cannot figure where I've gone wrong. In a word: help?

Userlist.ini? I'm willing to try anything once. Where might I find that and what does it do?

Ah, so I'm not the only one who is having this problem. I was absolutely certain that I was at fault. Shame that it isn't just me. Could it be the terrains aren't compatible with the latest patches and that is the root of the issue? I doubt this would be the case though.

Any player navy aircraft assigned to the carriers, though I'm a tomcat addict by nature. All aircraft that may be in question have the CarrierBased=TRUE in the aircraft_data.ini. And to be sure, the carrier ground object names all match properly. ALL of the carriers and aircraft function correctly in the stock terrains under all patches, it's the add-on terrains that are being troublesome and Cuba in particular.

DAVE! Awesome to be back. I've been okay. I spent some time cheating on my beloved Thirdwire games. I've been pretty good so far. Women have changed, computers have changed, and I'm generally in a better spot than I was. How have you been? Anyway, I'm current on my patches for SFP1. Sorry that I forgot to mention that. My bad.

Figured this one out. Here's the strike load that I wrote and they work fine. An entry for the TER was absent. This is based of a harrier picture I saw. Copy and paste it over the strike set on your loadout.ini for the jet. You'll need to modify the centerline rack in the data.ini to use a DLP. Or you can just take what you need from this. Either way, the jet needs a designator on it to use the GBUs anyway. Loadout[01].WeaponType=AIM-9L Loadout[01].Quantity=1 Loadout[02].WeaponType=AIM-9L Loadout[02].Quantity=1 Loadout[03].WeaponType=AGM-65D Loadout[03].Quantity=1 Loadout[04].WeaponType=AGM-65D Loadout[04].Quantity=1 Loadout[05].WeaponType=AV8_Tank300 Loadout[05].Quantity=1 Loadout[06].WeaponType=GBU-12 Loadout[06].Quantity=3 Loadout[06].RackType=TER Loadout[07].WeaponType=AAQ-14 Loadout[07].Quantity=1

Man, I can't wait til we have a D model to put these on. Lookin' good!

Ah, okay. I had heard unfortunate rumors about the a2g capabilities of the F-22. I actually like the F/A designator. it may be a bit of a mouthful but I like that the designator indicates it can kill something anywhere.

The F/A doesn't sound too Navy, but by dropping the A I guess Lockheed is also admitting it doesn't have realistic a2g expectations. No bombs to ruin the radar return. Which, isn't mud-moving one of the roles of the -35 anyway? BTW, I've been taking a look at the Joint Helmet Mounted Cuing System and it's "look at it/shoot at it capabilities". Like something out of Firefox. Kinda scary stuff, considering that we're just now getting that and other countries have had it for a while.