Fubar512

MaxLoadFactor=X.X (X-value represents G-level)

The average SF aircraft model poly-count today hovers around 10,000.

Actually, it does.

And that's where you're stuck. As I explained above, to the best of my knowledge, that's not what the SF flight engine "wants" to see. You simply have to stop and think. Is Lift effected by velocity (Mach level)? Is it effected by angle of attack? Is it effected by the wing area, sweep angle, tip chord, and root chord (in other words, by wing geometry)?

Density is more or less a given. That one's easy to figure out As I stated before, you've inputted geometry data into the required fields to help calculate a constant, which is represented by CLa. Since lift (represented CL), is effected by mach level, we have tables that tell the flight engine what multiplication factor to use at a set mach level.

CL was calculated when you introduced the required values into the application. The output was a set CLa value at the Mach value you've inputed. That is what the game needs to read in order to interpret the data. Lift varies with Mach level. Do you understand now?

Perhaps he prefers five-legged tables....

LOL.....are you serious? Think of the statement you've just made, and you'll find the answer.

CD is the coefficient of drag. CDa is the Coefficient of Drag as determined by alpha , and is not to be confused with CD0, which is at zero lift. For the most part, CDa is a seldom used variable.

If you're referring to Kreelin's AeroConvert, I'd assume it to be an average of several airfoils. If you try several airfoil types in JavaFoil, you'll see that while CL0 may change appreciably among various airfoils, CLa seems to be more dependent on the wing's geometry itself.

Typhoid, you funny man, you: Apophis

Kevin, The RWR threat icons are from the F-15C model that we released almost two years ago. If you want, I'll send then to you, and you can release them with instructions on how to install and use them.

Another site that hosts some neat freeware apps: http://www.gylesaero.com/index.shtml

The Mean Area Chord (mac) value, is applied as the "ReferenceChord" , under the AircraftData header. like so: [AircraftData] ReferenceChord=2.39 The CLa value is generally divided by the number of main wing panels. If we simply have a left and right wing, we would divide the value by 2, the result being a "CLa=2.002" statement for each wing. As most models have four wing panels (left and right inner & outer), we need to divide this value by 4. I personally (and arbitrarily) apply 60% to the inner wing panels, and 40% to the outer panels, so 2.002 x 0.60 = 1.2012 inner, 2.002 x 0.40 = 0.8008 outer The Ymac value (2.28 in this case) is ideally applied whole for each wing, locating it on the "Y" axis by denoting a negative value for the left wing (Ymac=-2.28), and a positive for the right (Ymac=2.28). Since most models have four wing panels, this poses a bit of a quandary, should we divide the Ymac value between them? The answer is a resounding "No". One solution would be to recalculate using the original Croot value for for the inner panels, and then substituting the mac value (2.39), in place of the original Ctip value. You would then redefine the wingspan as the span from mac to mac on the model. A similar operation would be performed on the outer wings, substituting the mac measurement for the Croot, and utilizing the original Ctip values, and then creating a span value as if the roots of the resultant mess were connected. It's probably best to simply use the Ymac value for the inners as originally calculated, and fudge the outer wing values somewhat.

Close enough for government work! Ctip=1.684 Croot=2.98 mac=2.39 Ymac=2.28 Cla=4.004153 Next step (when I get a chance) applying these figures to an FM.

Now, for your first assignment, I want the you to find the CLa, mac, and Ymac values for this aircraft. I will give you two freebies, the wingspan is 10.06 meters...you should be able to calculate the other values off that. 35 degrees is the leading edge sweep value.

First, lets start out with the CLa calculation. On the input side (Geometry/Speed), we need to input the following data in the appropriate fields. If you cannot find hard data online, measurements taken off a true-to-scale 3 view will work. Geometry/Speed Surface = Total wing surface Area in square meters Ctip = Chord at wing tip LE angle = Leading edge sweep angle, in degrees Span = Wingspan (obviously) Croot = Chord at wing root Mach = use 0.4, the SF "standard" Results: mac = Mean Area Chord, output figure is used as reference chord Ymac = Mean Area Chord offset to "Y" axis, figure is for left surface is a negative (-) value, for right, a positive one CLa = Coefficiant of lift/alpha CLa DeltaW = Coefficiant of lift/alpha for delta-winged models

Mustang, If you're looking for a tool that will perform most of the number crunching for you (CLa, mac, Ymac), I suggest you that download Kreelin's AeroConvert, a neat little app with a simple interface: http://forum.combatace.com/index.php?autom...p;showfile=4932

which aircraft in particular? Some sources are really gold, others are, well, next to worthless.

One word: GOOGLE

From the MegaSoundPack, released in May of 2005 (which is where that particular sound effect came from, BTW) :yes: Gun Sounds: Unique Gun sounds (that is other then the default names, such as cannon, Vulcan, tankgun, 50cal) MUST be added to the Soundlist.ini, and added to the weapon's entry in the Gundata.ini, under the “Gun Fire Sound Name” parameter. It’s best if you use the gun editor to accomplish this. Don’t forget to save your changes. Unique gun sounds include: Lmg, for small bore automatic weapons (under 12mm). Hmg, for heavy machine guns (12mm, 14.5mm, etc.) Gsh, for the Soviet Gsh series revolver cannon (Gsh-23mm and 30mm Gsh-301) 37MM. for all 37, 40, and 57 mm auto cannon NavalGun, for large bore weapons, 100mm and up. M39Cannon: Used on the A-1, F-100, F-101, and F-5.

In the pit, all eye candy on, over active water & clouds: External view, Marcelo's Su-27, which IMHO has the best shadows of any third-party model:

It's actually rather mediocre. It's an Athlon XP-M 3000+ running at 2300 MHz core speed on a 210 MHz (420 MHz DDR) bus, which would yield an XP rating of 3400+, if you're into that sort of thing. I'm running two 512 mb sticks of Mushkin RAM in dual-channel mode, have an ATI X800XT 256 mb AGP video card, and a seven year old Turtle Beach Santa Cruz sound card. As I said, it's mediocre, at best.