SupGen

No, What's on second.

I hope you don't mind if I add to this, Eric. MURc, the NATO Fighters mods have always focused on the straight up, WARPAC armored forces pouring through the Fulda Gap, Germany/Central Europe scenario. When you consider that the Red Storm Rising campaign is probably occurring concurrently with something similar to the stock Northern Sabre campaign, (Clancy's book wasn't that much of a leap; NATO planners had long suspected that the Soviets had plans to contest the GIUK gap one way or another, with the aim of a breakout into the North Atlantic in order to halt, or at least delay, American reinforcement convoys.) The U.S. Navy would have more than had it's hands full countering this threat, and for this reason it is unrealistic to expect to see F-14s over mainland Europe in a conflict of this scope. I love the Tomcat, and it would have been involved in the conflict, but there is a 90+% percent chance that it's involvement would've been in the struggle for control of the seas, in this case the North Atlantic, the mission it was built for.

Somewhere, in a secret laboratory on a small island off the west coast of the United States, there is a door that says Do Not Disturb!...you're too late, occupant is already disturbed!

You know, for future reference.

F24A, a question. Did it work?

That's exactly what I meant above. F24A, my Options .ini looked fine too, problem was it was pointing to an earlier .exe of the same name (I think). And all my SF2 stuff is on my F: drive, too.

As Foghorn Leghorn would say, "Now hold on just a minute, there!" What I said before was predicated on the assumption that you actually were carrying the tanks. They will not show in the in-game loadout screen in any case, however if they are not showing in an exterior screenshot, they are not there and you don't have the gas. Try flying a mission without touching the loadout; with the weapons given. I know if you touch those unsymetrical loadouts it can pooch things, so don't even go to the loadout screen; fly the mission and see if the tanks are there. If you do that and the tanks aren't there, I would have to think there's a screw loose in your install somewhere. Take a look at the aircrafts' loadout .ini. As far as flying the mission goes, I meant only fly high when it's safe to do so, not to get shot down trying to save gas.

At the risk of looking like a dumbass (which don't scare me no more, lol) have you guys tried replacing your Options .ini? I'm not sure why I think this would work, but if you cut and paste your present Options .ini to a safe location, you could try it with no harm done. Replacing the Options .ini solved some problems for me recently.

Anyone know where to find Edward's Solomons Campaign mentioned here: http://combatace.com/topic/75291-solomons-campaign-planes-stacked-on-top-of-one-another/ ? I looked in the Ist Gen download section and saw his KAW mod mentioned in that thread, but no Solomons.

Count me in, I guess.

These shots are from Nato Fighters 5, Red Storm Rising, Phase Two. I've definitely got tanks. GR 1, SEAD mission.

Yup sorry, I was looking at Ian's version. Edit: The plot thickens!

Hey Crazy Jow, if you look in the data .ini, you'll see that only two pylons can carry fuel tanks, in the loadout .ini, those two are tanked in every loadout, they don't show in the in-game loadout screen because their StationGroup also covers two pylons carrying electronics pods, so the game leaves the window blank. You've got the maximum number of tanks in every loadout, if you're runnin' out of gas, you need to fly a more fuel conserving flight profile, i.e., if you're not in a threat area, fly high.

The above is from post #3 in this same thread. In the aircraft's .ini file, change AvionicsDLL=AvionicsF14A.dll to read AvionicsDLL=Avionics70.dll and the radar will work; you just won't have the ability to target six targets at once. There are instructions in the Superpack on how to do it for the F-14D, just apply those to the other aircraft as well. That being said, the best solution is to get SF2NA and enjoy multiple targetting.

Anytime, glad I could help! It's not perfect, you could probably tweak it a little.

Ian, this is working for me: First, some changes to RPM settings in the Data ini: IdleThrottle=0.10 IdleRPM=0.68 IdleNozzle=0.0 CruiseThrottle=0.37 CruiseRPM=0.82 CruiseNozzle=0.0 MilThrottle=0.65 MilRPM=0.95 MilNozzle=1.0 MaxThrottle=0.78 MaxRPM=1.00 MaxNozzle=1.0 FullABThrottle=1.12 FullABRPM=1.05 FullABNozzle=1.0 Then this in the Cockpit ini: [Tachometer] Type=TACHOMETER NodeName=pil_rpm ItemNumber=1 MovementType=ROTATION_Z Set[01].Position=0.00 Set[01].Value=0.00 Set[02].Position=90.00 Set[02].Value=0.60 Set[03].Position=180.00 Set[03].Value=0.90 Set[04].Position=260.00 Set[04].Value=1.00 Set[05].Position=270.00 Set[05].Value=1.05 [RPMdigits] Type=TACHOMETER CounterNodeFormat=RPM_dig%d MovementType=ANALOG_COUNTER ItemNumber=1 Scale=100 //Set[01].Position=0.0 //Set[01].Value=0.0 //Set[02].Position=360.0 //Set[02].Value=100.0 Obviously, you can delete the entries I commented out, but try this, as I said, it's working in my install.

Remember what happened with me and BoB. That advice from Migbuster was perfect. You might want to try removing folders one at a time and see if the campaign starts. If you remember, the game was trying to start Kadesh without any modern aircraft, with predictable results. If you want to try that, copy your aircraft folder to a safe location, or just rename it, start the game and hit the campaign button. If any other campaign is in the selection window but the Philippines, you've got the same problem I had. If so, select the Philippines campaign and exit the game. Delete the aircraft folder that the game generated and rename/return to it's rightful place the WWll aircraft folder. Start the game and see what happens. As far as any progress, I've been a little sidetracked lately; I'm eyeing the Philippines mod with a jaundiced eye, looks like a lot of work! Also, and I don't want to sound like an ingrate here, but the Solomons folder you sent was the Terrain, not the campaign. No biggie.

ndicki, I had the same problem and it was what Migbuster said, see this thread: http://combatace.com/topic/77715-modern-planes-returning/ . Also check the link in post #3 of that thread. Good luck!

The "rail on the right wing"?

Well,I'm glad arthur got me to take another look at these; delete the DisplayLimit statements from all the A-6E Avionics inis or the camera won't work properly. [TVDisplayData] UseRadarTexture=FALSE DisplayLimitLeft=8---This DisplayLimitRight=119---This DisplayLimitTop=6---This DisplayLimitBottom=121---and This ApplyFilter=TRUE FilterMaterial=DTVFilterMaterial OverlayTexture=Cockpit\A-6E_DTV.tga Add this line to the Data inis right under CameraPosition. CameraAngles=0.0,0.0,0.0 The middle number will let you pitch the camera up and down.

That was MMMmmmm as in MMMmmmm...ice cream!

Ya know, I just took an A-6E for a spin just to see and... well, most of the good stuff is already animated. The rest of the good stuff (Weapons switches, etc.) is over on the BN's side of the cockpit. I'm not sure if it's really worth doing. Edit: One thing you can do is in the Cockpit ini, under SAMLight change Type=Master_Caution_Light to Type=THREAT_LAUNCH_WARNING_LIGHT. This came from Fubar, to give credit where it's due. Thank you, sir! Now you'll Know when the Kiev is about to put one up your tailpipe! The other thing I did was to lower the AoA Indexer values fairly drastically; they seem to work better. Good luck! [AoAIndexerSlowLeft] Type=ANGLE_OF_ATTACK_INDEXER NodeName=indexer_slow_left MovementType=LIGHT //Set[01].Value=16.00 //Set[02].Value=30.00 //Slow (19.50 - 30.00) Set[01].Value=10.14 Set[02].Value=23.53 [AoAIndexerOnSpeedLeft] Type=ANGLE_OF_ATTACK_INDEXER NodeName=indexer_on_speed_left MovementType=LIGHT //Set[01].Value=13.87 //Set[02].Value=16.80 //OnSpeed (18.00 - 20.00) Set[01].Value=9.16 Set[02].Value=10.47 [AoAIndexerFastLeft] Type=ANGLE_OF_ATTACK_INDEXER NodeName=indexer_fast_left MovementType=LIGHT //Set[01].Value=-10.0 //Set[02].Value=14.67 //Fast (0.0 - 18.50) Set[01].Value=-5.00 Set[02].Value=9.49 [AoAIndexerSlowRight] Type=ANGLE_OF_ATTACK_INDEXER NodeName=indexer_slow_right MovementType=LIGHT //Set[01].Value=16.00 //Set[02].Value=30.00 //Slow (19.50 - 30.00) Set[01].Value=10.14 Set[02].Value=23.53 [AoAIndexerOnSpeedRight] Type=ANGLE_OF_ATTACK_INDEXER NodeName=indexer_on_speed_right MovementType=LIGHT //Set[01].Value=13.87 //Set[02].Value=16.80 //OnSpeed (18.00 - 20.00) Set[01].Value=9.16 Set[02].Value=10.47 [AoAIndexerFastRight] Type=ANGLE_OF_ATTACK_INDEXER NodeName=indexer_fast_right MovementType=LIGHT //Set[01].Value=-10.0 //Set[02].Value=14.67 //Fast (0.0 - 18.50) Set[01].Value=-5.00 Set[02].Value=9.49

How's it goin', arthur666? The fuel guage can be fixed in the Cockpit ini. The stock value of 10000 LBs is incorrect, change it to 15770 LBs and it should work fine. Unfortunately, the Range and Course counters are not fixable as far as I know. While they are mentioned in the ini, they aren't mentioned in the Lod and therefore don't exist in the model. As far as giving the pit the F-102 treatment, what you'd have to do is go through the Lod, find the mames of the buttons, switches, lights, etc. that you want to make animated and give them each an entry in both the instrument list; e.g. Instrument[xxx]=Attack_switch or whatever, and an entry below that, either an animation statement linking it to an action or a statement defining it as a Weapons_Selector_Switch or what have you. As there is no out file, just finding the names of things is kind of mind-boggling. I've been thinking about looking into this myself but I'm still recovering from the F-102. Hey, Fubar. Beat me to the post! Yeah, the guage works, the value in the cockpit ini is wrong. You can get the correct amount by adding up all the tanks in the data ini (converting from KGs to LBs) or (the really easy way) check the loadout screen in-game: 15770 LBs.

All this time I thought I knew everything I needed to know about gunsights and then... While perusing the manual (in search of something else) I see this line under using the PhantomII's LCOSS: In A/G (Air-to-Ground) mode, the sight is manually depressible to 245 mil below the fuselage line. It's not really, is it? In a similar vein, if you set default depression to 245 mils, will it? (In AG mode).

So, were all those tables I was expecting in the manual Ravenclaw sent me there? Oh yes they were.: Thing is, the manual is password protected, so I had to print the pages I wanted and scan them back into my computer; this took a little while. Tomorrow I will upload a detailed analysis of those pages; stay tuned. Or not, you might want to run for the hills!