Fubar512

Hahahahaha!

Nope.....the Moon! The Moon!

We have faith in you. Here's your asignment for the day. Find the Catfile path statement in the appropriate *.ini file and edit it like so: CatFile=..\VietnamSEA\VietnamSEA.cat Post the results so we can grade you Next, we'll have Colonel Rhumbas test your ability to handle elevated body temperature. You will not have to exert yourself at all.....

hklhkl

You must either be ending your missions quickly, or are warping to and from the objective. The left gauge only registers once the internal tanks dip below 9000 lbs. Fly a mission from the runway, punch off the drop tanks right after takeoff, select afterburner, and watch the left gauge start dropping after a few minutes.

The two fuel gauges work fine on the F-100Ds in both my WoV & SF installs. They are in fact, displaying both external and internal fuel quantity, somethings that's lacking on a few other aircraft.

Yes its possible, but only if you're friends with the developer To the best of my knowledge, what you want to do would require editing the cockpit (or radar screen's) lod to include the necessary tga files, something only the original developer is capable of.

Using SF as an example, extract the file "Desert_Types.INI" from the Terrain/Desert/Desert.CAT. Open it in Windows Notepad, and you'll see this (the first entry): [TargetType001] Name=barrack1 FullName=Barrack ModelName=barrack1.lod TargetType=MISC ActiveYear=0 TargetValue=20 UseGroundObject=FALSE DamagePoint=10.0 ArmorValue=0.0 ArmorType=0 RepairRate=0.150 StartDetectChance=0 StartIdentifiedChance=0 IncreaseDetectChanceKey=0 MaxVisibleDist=8000.0 DamagedModel= DestroyedEffect=MediumShortStructureCollapse DestroyedModel=barrack1_destroyed SecondaryChance=25 SecondaryEffect=SmallExplosionEffect Compare it to the following entry, and note the differences: [TargetType046] Name=CityBuilding4 FullName=City Building ModelName=citybldg4.lod TargetType=CITY_BUILDING ActiveYear=0 TargetValue=0 UseGroundObject=FALSE DamagePoint=100.0 ArmorValue=300000.0 ArmorType=1 RepairRate=0.150 StartDetectChance=20 StartIdentifiedChance=0 IncreaseDetectChanceKey=0 MaxVisibleDist=12000.0 DamagedModel= DestroyedEffect=LargeTallStructureCollapse DestroyedModel= SecondaryEffect=MediumExplosionEffect SecondaryChance=100 By reading through the other entries in the Desert_Types, I see a whole slew of opportunities to cause mischeif...Runways, towers, cranes, (etc.). the list is almost endless... :D

That's because the structures themselves have no damage modeling. There is no destroyed, damaged, or secondary effects associated with them. They have no structural limits, in other words, no "armor" type defined (wood, steel, aluminum, etc) in their data files. That's why you can adjust the explosive force to 100 megatons, and still not "flatten" an airfield or a city. It can be fixed, however. I'd love to see "burning" trees, as well....

Patch 1 is for the original Strategy First release.

My suggestion is that you apply for membership at www.column5.us. The majority of the modelers hang out there, and you'll find them more than willing to help you out.

That's really cool! A genuine "Frisbee", just what we needed for a "Red Storm Rising" campaign. If you want some pointers on creating the FM for it, let me know, and I'll hook you up with the guys from AirTevRon 5.

Your display driver is most likely the culprit. First, make sure that you have DirectX 9.0C installed, and then make sure that your display driver is compatble with it (DX9.0C).

You forgot to mention how Kerry's affair with Jane Fonda so preoccupied Ted Kennedy (He allegedly became quite aroused when he heard about Fonda's penis), that he drove off the bridge in Chappaquiddick in a fit of jealousy, forgetting that Mary Jo Kopechne was still in the car!

Come on, Column 5, you failed to mention the real reason the war ended: It ended after Colonel Kurtz and Colonel Kilgore mined the entrance to the Nung River at Vinh Drin Bac, and then rescued the Playboy Bunnies that were being held by the Viet Cong Air Force in Hau Phat.

Yeah. Just imagine what would have happened if the war hadn't ended when the crew of the Mayaguez invaded Phenom Phen, or when the B-17 carrying Jane Fondle crashed into Supreme Commie HQ in Hanoi, or better yet, when John Wayne and Chuck Norris snatched Ho Chi Minh and trussed him up in a balloon rig so he could be snared by a C-130. Yeah, just imagine if none of that had happened

It's a question of airfield size. There are no large VPAF airfields modeled in WoV, so one must edit the "MinBaseSize=LARGE" entry in the MiG-25PD_Data.ini to read "MinBaseSize=MEDIUM".

The fix is: Extract the FlightEngine.ini from the FlightData.Cat (using the SFP1E extraction tool). The file will be extracted into the Flight folder by default. It must reside there in order for the following edit (fix) to work. Open the FlightEngine.ini with Notepad, then scroll down to where it says "[GraphicsSettings]", and edit the values there to match the following example: [GraphicsSettings] ZBufferDepth=24 MaxVertexCount=8192 MaxIndexCount=16384 MaxTextureCount=8192 MaxModelType=2048 MaxMeshPerScene=1024 MaxModelPerScene=2048 MaxLightPerScene=512 AspectRatio=1.333333 MinPixelSize=1.0 Accept the changes, make sure, once again, that the (edited) FlightEngine.ini is in the flight folder, and you should be good to go.

SF & WoV are rougly similar, with WoV being a bit more demanding due to the density of the North Vietnamese air defenses. The biggest frame-rate killers in both sims (assuming a default install) are shadows & mirrors. I recomend the following settings on your system, at 1024x768x32bpp resolution: 1) Shadows. turn them off unless you have at least an Athlon 64 3400+ and a GeForce 6800 GT. 2) Mirrors. turn them off also, unless you have at least a P4 3.0 or Athlon XP 3200 and a GeForce 6600 GT. 3) Cockpit Reflections. You're just at the point (CPU-wise), where you can safely run them assuming your GFX card is at least a GeForce Ti4200 or better. 4) Horizon distance. Set this to "Normal" on your system. 5)Set everything else to "High".

Assign them within WoV itself under Options/Control/Customize Keyboard Map.

The afterburner effects files should reside in the effects folder, not the flight folder. I'll bet the reason you're not seeing the AIM-54 is due to the fact that its nation name is listed as "USN" instead of "Iran", in the weapondata.ini. You'll have to use the Weapon Editor to correct this and to save your changes. There's a sticky topic on the Weapon Editor at the top of this forum.

It works fine on my 6600 GT in both WoV and SF. What are you setting it at? Whatever you do, do not set the AF at "application controlled" because it will be disabled.

Change the "7Z" file extension to "RAR" amd it should open with no problems.

CMs are global. The only other alternative is to eliminate flares & chaff from the data.ini files of all the other aircraft, and then have the player fly a "unique" aircraft.

Such as adding a height value to the light positions? :excl: Hook up with Saganuay....he'll show you.