Fubar512

Would you settle for an aviation cruiser?

Yes it does. The desert terrain is the default terrainset for all versions of SF:P1.

Try adding 10 until you get the results you desire (Cmdc=0.015, =0.025, etc.)

Sounds as if the flaps are too effective in the pitch axis. Back up your original F-15A_Data.ini, and try this value under flaps (remember to adjust both sides) Cmdc=0.005<----replace the original Cmdc value with this one.

Is it Mars, or is it SF's desert terrain with no fog and a 238 km horizon distance?

Applying these settings to your flightengine.ini should correct the problem [GraphicsSettings] ZBufferDepth=24 MaxVertexCount=8192 MaxIndexCount=16384 MaxTextureCount=8192 MaxModelType=2048 MaxMeshPerScene=1024 MaxModelPerScene=2048 MaxLightPerScene=512 AspectRatio=1.333333 MinPixelSize=1.0

The only way to eliminate that effect is to edit the following value in the flightengine.ini file: [HighDetailOption] HorizonDistance=X Changing HorizonDistance to 238000.0 will give you a clear 238 KM horizon, about right for SF's average cruising altitude, that is, assuming one were flying in a vacuum . Oh, and you'd have to play with the sky panel and horizon color entries in the environmentsystem.ini to correct the "deep blue sky to the horizon" effect that would result from such a high horizon distance.

Flaps work by essentially: 1) increasing lift 2) forcing the nose down Are you taking off on auto or manually? Are you retracting the flaps and gear as you pass 180 KIAS?

No offense, but even no aircraft ever built can attain Mach 2.35 at sea level. The record at 300 meters (about 900 feet) was held by an F-4 Phantom (named "Sageburner") for over 16 years, from 1961 until 1977. And that was 902 MPH, or 785 KIAS (1,452 kph). As incredible as it may seem, the current record is a scant 85 knots faster.

OK, This is will be first and last time that I will post this. Following JSF_Aggies instructions to the letter (his instructions for adding terrains are posted on the knowledge base here at CombatACE), I then copied the Desert Folder from SFP1 into WoE, minus the Desert.Cat. Next, I installed Pollock's upgraded Desert Tiles (a must, IMNSHO). I did NOTHING else out of the ordinary, other then installing my concrete desert runway tiles That means NO airfiled.inis were carried over. I then edited the Desert.ini file by adding the following line: [Terrain] CatFile=..\GermanyCE\GermanyCE.cat Next. I started WoE and verified that the terrain was available: Then I started a mission and....OMG, how can this be....it actually works!!!!! (note green Euro-pattern tents from WoE in the second and third images) This also means that all campaigns will work ACROSS THE BOARD with nothing more than a few judicious edits and the installation of the necessary objects and aircraft.

Unfortunately, that will not help, as there currently is no provision (parameter) for angling the pilot model. As stated earlier, a new pilot model must be created which is reclined at the proper angle.

I suggest that you read the excellent radar tutorial by Streakeagle in our knowledge base. It explains the workings of the F-4 radar, which you'll need to learn in order to effectively use any radar-guided missile.

Bienenbaer, One must keep in mind that all the default MiGs in this series were intended to be AI-controlled adversary aircraft, and their flight models were optimized to that end. That being said, there are a few third-party FMs available for the default MiGs. Kreelin and I made one of the MIG-21MF, and I made one for MiG-17F some time ago. Both compare favorably with published data. The '17F in particular displays the handling quirks that are unique to that aircraft (loss of pitch and roll authority at speed). I was in the process of working on an FM for the '19, but put it aside to work on other projects. There's a decided lack of published data on that bird, that is, data that would be useful in producing an accurate flight model.

JP, Try this: Place SFP1E's executable file (.exe), in your Windows/System32 folder, and create a shortcut to the desktop for it. Then either logoff/logon to Windows again, or restart your computer, and then try opening up a .Cat file. I've found that little trick to work more often then not.

Hellcat, place all the files in your WoV/Terrain/VietnamSEA folder. Saywhat, I've not noticed any impact on framerates, even when flying at tree-top level, and my present system isn't exactly state of the art.

Weapon availabilty depends on two factors. The first is nation (USAF, USMC, SOVIET, etc.), the second, service date. I find the latter to be the culprit in the vast majority of weapons availabilty issues.

Nele, This is exactly what we SF fanatics look for. While we could argue that some of the aerodyanic values you've used are questionable when one applies the accepted formulas to them (such as the wing Cla), the overall effect is quite convincing. Please send me a private message (PM). Cheers, Fubar512

Deuces ( http://www.sfmods.com/ ) has an upgraded SEA terrain set, that's just recently been updated. He also released a tree pack some time ago. Let me know if you cannot find it.

The '105s were updated with a LORAN-A based system, but the data I dug up points to that system not being used at all in SEA. In fact, it states that all Thuds so-equipped where sent stateside to ANG units! The TISEO set was contolled by the WSO, as I mentioned before. I remember reading somewhere that Sony manufactured the display heads for it, and even went as far as mentioning that in their domestic (Japanese) ads, which caused quite a stir at the time. Also, one forum member (Crab02) was creating a TISEO-equipped F-4E until he discovered that it was a back-seat only system.

TISEO was operated solely by the WSO, there was no display in the pilot's cockpit. There are a few A-7 'pits that have been edited to use CCIP. In fact, I believe I saw someone posting that mod, here at Combat Ace.

I'm sure you know the answer, Brian. None of the aircraft represented in the default SF planeset had CCIP in RL. In WoV, only the A-7 featured it, and it wasn't introduced until the D-model. TK has expressed interest about the DIANE system in the past, so, who can say?

As long as the SAM sites are defined on the terrain map and target_types.ini, the game engine will place any suitable (for that nation and period) "static_sam" , "sam_radar", and "ew_radar" unit on those coordinates. By defining a "networktype" entry in the unit's data.ini, you can ensure that the individual units are matched by type. For example, both the StraightFlush and its attendant SA-6 SAM launchers should all have "NetworkType = SA-6" under the "DetectSystem" section of their data.ini files. As far as having too many SAMs, just set the enemy air defenses to "normal", instead of 'heavy" If you're having issues with the SA-3 series, rest easy. Crusader and I are working on a fix that prevents them from salvoing all their missiles at once.

Is this in a user created, or game generated mission? If it's the former, that behavior is due to a lack of defined waypoints.

It sounds as if you have a nested folder issue. Open up the Objects/Aircraft/A-6A folder and make sure that there isn't another folder named "A-6A" within that. If so, cut and paste that one into your aircraft folder and delete the original.