ST0RM

I was just going to post a similiar thread. Seems that TTools is not directly FSX compatable. You have to use FS9 to decompile and it's a risky operation. You most likely will lose much of your FSX AI. I'm looking for the best (and easiest) way to add AI flights/flightplans. Especially military. I've got WoAI, but I'd like to add specific aircraft/bases. -S

Well, we were told today that if the stoppage happens, they'll pay us for only 8 days. However, we're expected to show up at work and work for no pay. I plan on showing on Monday and letting them know where I'll be. And it won't be at work. Most likely looking for a side job to help pay for my bills. UCMJ be damned. They broke the faith... The guys and girls out on deployment are really screwed. They have no options. Way to go Barry!

Cool, I'll start working on putting it all together. -Jeff Kevin: Gotcha!

I've edited this to fit the SF2 A-4F_74 model so that you won't need the SF1 LODS. Shall I release as a co-project? -S

I've only found the HTS to be listed as Nav Pods. The other pods (LiteningIII, Sniper, etc...) are LP. Glad it worked. -Jeff

With Preview Dx10 mode, I'm limited to a few 3rd party add-on aircraft as they are all still using bmp textures, plus I lose some aircraft lights, plus some other additional textures. But in Dx9, I get all that back, but the look isn't as real as in Dx10. So, what are your thoughts on this? Sucks MS ditched the FS department. Maybe we could have gotten a decent patch to bring FSX up to Win7 standards. Finally when comps can run it all out, MS bails. -Jeff

Kind of limited, but some Cruz Campo Gran Reserva and pizza went down really nice. -S

Its because the station has the wrong allowed weapon class. The HTS is listed as an NP in the Wep Editor. Change the HTS_Mount station AllowedWeaponClass=EP to: AllowedWeaponClass=NP Should work fine after that. -S

There was a typo in the EA-18G_Cockpit.ini file Change this: [CockpitSeat001] ModelName=Cock_F18C To this: [CockpitSeat001] ModelName=Cock_F18 And in the EA-18G.ini file Change this: AvionicsDataFilename=FA-18E_avionicsnoforn.ini To this: AvionicsDataFilename=EA-18G_AVIONICS.INI Should be good to go after that. -S

Bad Moon Rising "Leads off..." In the break

Add this line to the RafaleB.ini [shadow] CastShadow=TRUE ShadowCastDist=10000 MaxVisibleDistance=400 I got my Rafale to fly reasonably well also. Just needs an updated pit/avionics. I'm using the MF Mirage 2K as a placeholder. What was your landing gear settings? -S

Zur, First off thanks. This thing is a blast to fly. The VTOL is rock solid and I love the pit. During night strikes, it's the prefect balance. -S

Hawk 11 cleared for takeoff Rolling in and dropping a CBU Hawk 21 "Rifle" Engaged!

Ok, I've read all of the KB stuff on this. Do I need to add the carrier to the .types.ini also? Or when using the ExP2 mission editor do I need to be over the carrier station in order to get the CV be allowed to be used? -S

Some unedited screenies A pair of Rafales inbound a target over Libya: And returning to Sigonella after a successful mission. Mt. Etna looms in the background: -Storm

I'm on Win7 with a 1Gb Nvidia 485. Its not a show stopper, but looks odd.

Stary, I'm getting a weird effect with the flares. They seem to get a trail from one effect to another. Even more so when the opposing aircraft is popping them after I shoot an IR missile. Check out the screenshot. Any ideas? -S

Justified.

Awesome skinning Eric. Nice to see some color on the NSAWC and training Supers. -Jeff

Thanks Stary. The combined pack is much easier than separate packs. -Jeff

Thanks Ghost. That fixed my issues with the cfg files. Now I'll try and figure out why I get errors trying to install the WoAI packs. -Jeff