Fubar512

CL0 Lift coefficient at zero angle of attack (AOA) CLa Lift coefficient due to AOA CD0 Zero-lift drag coefficient CDL Drag coefficient due to lift (induced drag effect) Cmq Pitching moment due to pitch rate (pitch damping) Cmad Pitching moment due to AOA rate (aero interaction between wings and horiz tail) Cyb Side force due to sideslip Cyp Side force due to roll rate Cyr Side force due to yaw rate Clb Roll moment due to sideslip Clp Roll moment due to roll rate (roll damping) Clr Roll moment due to yaw rate Cnb Yaw moment due to sideslip Cnp Yaw moment due to roll rate Cnr Yaw moment due to yaw rate (yaw damping) CLiftdc Lift due to control surface deflection CDdc Drag due to control surface deflection Cydc Side force due to control surface deflection Cldc Roll moment due to control surface deflection Cmdc Pitch moment due to control surface deflection Cndc Yaw moment due to control surface deflection DeltaStallAlpha Increase in max angle-of-attack before stall Xac X-location of aerodynamic center Ymac=Mean Area Chord at "Y" axis

LOL..... that's not cheating, that's called using your head.

A hi-rez planning map is quite doable, and (at least in theory) any object with a fixed position, such as a SAM site, search RADAR, or AAA emplacement, can have an icon assigned to it that will show on the planning (and in-flight) map. However, that last feature may not yet be fully implemented, as we've recently discovered when trying to pinpoint RADAR sites. Unfortunately, according to the developer (TK), a system such as DIANE is currently beyond the capabilities of the existing avionics code, or the scope of the sim. Yes, that's doable, and it's already been accomplished with other terrains. It's a bit of work, though, as you'd have to relocate every object, town, and airfield, to match the full-sized terrain map.

If you were to install WoE, it would give you an option to install it over WOV. You would then have access to all the WoE mission types, including intercept.

Sounds as if you're trying to use an earlier version (pre SP4) of the Weapon Editor. You need to use the one that ships with the latest weapons pack.

You must have WoV. WoV does not have "intercept" coded in as a mission choice in system-generated missions, so you'll have to script your own. You can always add WoE and choose the merge option when you install it.

Yes, it's a pity that AMC had such poor build quality. Their designs were a bit more European in styling (the first generation AMX and Javelin were penned by the Italian designer Viginale), and they were a tad more civilized, with reclining seats and better suspension geometry than their Ford,GM, and MOPAR counterparts. I eventually modified the '70 AMX's suspension by adding Koni shocks, aftermarket anti-sway bars, and V-rated Pirelli CN36 tires (225/60-15s). It proved quite successful as an auto-crosser, and made it a much more enjoyable road car, to boot.

My first muscle-car (04/76 to 08/77) was a 1968 SS Chevelle with a 350 HP 396, backed by a Muncie 4-speed. It had four wheel drum brakes (made for exciting stops from highway speeds), and manual steering. My next (08/77 to 06/78), was a 1969 Dodge Charger R/T, with a 375 HP 440 and a New-Process 4-speed (a pretty, albeit, thirsty beast). I then owned a couple of AMC two-seater AMXs ( a 1969 and a '70), with 390 cubic inch V-8s and Borg Warner T-10 4-speeds. I even owned a 1969 Mustang rag top with the GT package, though it was powered by a 351 Windsor 2V and backed by an FMX auto tranny...pretty but not a muscle car. Here are the only remaining snaps I have of my cars... The '69 AMX (taken back in August of 1978, sporting Firestone drag slicks) And the '70 AMX, circa March of 1980

Wow, a '69 Cobra-Jet Mustang (complete with a shaker scoop), and a '69 Camaro. That harkens me back to my late teens (during the mid to late 1970s), when it was still possible to buy those cars second-hand, often for less than $1,000 US!

Try "revalidating" the weapondata.ini, by first deleting the weapondata.dat file (not the weapondata.ini). Next, open the weapondata.ini with the Weapon Editor, and hit the SAVE button. This will create a new weapondata.dat file, and your weapons should now be available.

Brain, I have a few snaps taken by my older brother when he was there, in '69 and '70. Now, he was in Chu Lai, so that would only be representative of what the area just inland of the coast would have looked like back then. Here's the scan:

Craig, Canards should be given an aerodynamic surface entry under [AircraftData], like so: [AircraftData] Component[008]=LeftCanard Component[009]=RightCanard They would then require the appropriate entries, as would any lifting surface: [LeftCanard] ParentComponentName=Fuselage ModelNodeName=Line01 DestroyedNodeName= ShowFromCockpit=TRUE DetachWhenDestroyed=TRUE StructuralFactor=1.25 DamageRating=DISABLED MassFraction=0.007 HasAeroCoefficients=TRUE LiftSurface=TRUE CLa=0.261 CD0=0.0004 CDL=0.0012 Cmq=-1.7825 Cmad=-0.8818 Cyb=-0.0109 Clp=-0.0025 Cnb=0.0055 CL0MachTableNumData=5 CL0MachTableDeltaX=0.40 CL0MachTableStartX=0.00 CL0MachTableData=0.986,1.000,1.037,1.020,1.051 CLaMachTableNumData=5 CLaMachTableDeltaX=0.40 CLaMachTableStartX=0.00 CLaMachTableData=1.001,1.000,0.979,0.910,0.938 CD0MachTableNumData=5 CD0MachTableDeltaX=0.40 CD0MachTableStartX=0.00 CD0MachTableData=1.825,1.000,1.028,2.494,2.773 CmqMachTableNumData=5 CmqMachTableDeltaX=0.40 CmqMachTableStartX=0.00 CmqMachTableData=0.971,1.000,1.107,1.261,0.873 ClpAlphaTableNumData=15 ClpAlphaTableDeltaX=4.00 ClpAlphaTableStartX=-28.00 ClpAlphaTableData=1.474,1.361,1.264,1.182,1.115,1.063,1.027,1.006,1.000,1.009,1.034,1.074,1.129,1.200,1.285 XacMachTableNumData=5 XacMachTableDeltaX=0.40 XacMachTableStartX=0.00 XacMachTableData=3.856,3.724,3.585,3.476,3.236 Ymac=-1.19 MovingSurface=TRUE ControlSystemID=1 StructuralFactor=1.00 MinExtentPosition= -1.2907,-1.6681,0.0000 MaxExtentPosition= 1.2907, 1.6681,0.2600 CollisionPoint[001]= CollisionPoint[002]= SystemName[001]=LeftCanard [RightCanard] ParentComponentName=Fuselage ModelNodeName=Line30 DestroyedNodeName= ShowFromCockpit=TRUE DetachWhenDestroyed=TRUE StructuralFactor=1.25 DamageRating=DISABLED MassFraction=0.007 HasAeroCoefficients=TRUE LiftSurface=TRUE CLa=0.261 CD0=0.0004 CDL=0.0012 Cmq=-1.7825 Cmad=-0.8818 Cyb=-0.0109 Clp=-0.0025 Cnb=0.0055 CL0MachTableNumData=5 CL0MachTableDeltaX=0.40 CL0MachTableStartX=0.00 CL0MachTableData=0.986,1.000,1.037,1.020,1.051 CLaMachTableNumData=5 CLaMachTableDeltaX=0.40 CLaMachTableStartX=0.00 CLaMachTableData=1.001,1.000,0.979,0.910,0.938 CD0MachTableNumData=5 CD0MachTableDeltaX=0.40 CD0MachTableStartX=0.00 CD0MachTableData=1.825,1.000,1.028,2.494,2.773 CmqMachTableNumData=5 CmqMachTableDeltaX=0.40 CmqMachTableStartX=0.00 CmqMachTableData=0.971,1.000,1.107,1.261,0.873 ClpAlphaTableNumData=15 ClpAlphaTableDeltaX=4.00 ClpAlphaTableStartX=-28.00 ClpAlphaTableData=1.474,1.361,1.264,1.182,1.115,1.063,1.027,1.006,1.000,1.009,1.034,1.074,1.129,1.200,1.285 XacMachTableNumData=5 XacMachTableDeltaX=0.40 XacMachTableStartX=0.00 XacMachTableData=XacMachTableData=3.856,3.724,3.585,3.476,3.236 Ymac=1.19 MovingSurface=TRUE ControlSystemID=1 StructuralFactor=1.00 MinExtentPosition= MaxExtentPosition= CollisionPoint[001]= CollisionPoint[002]= SystemName[001]=RightCanard Finally, set them up as control surfaces: [LeftCanard] SystemType=CONTROL_SURFACE InputName=PITCH_CONTROL RotationAxis=X-AXIS MovingSurface=TRUE MaxDeflection=-10.0 MinDeflection=3.5 ControlRate=0.5 MaxControlSpeed= 255.0 ModelNodeName=05 [RightCanard] SystemType=CONTROL_SURFACE InputName=PITCH_CONTROL RotationAxis=X-AXIS MovingSurface=TRUE MaxDeflection=-10.0 MinDeflection=3.5 ControlRate=0.5 MaxControlSpeed= 255.0 ModelNodeName=06 ReverseModelOrientation=TRUE These values are from an as yet unreleased model, so you'll want to recalculate for your purposes. The pitch axis I've set here opposes the models elevator pitch, as the real-life aircraft uses an FBW system that pulls the nose down at low speed, high AoA (as would be the case during a carrier landing). If you want the canards to pitch up with the elevators, just add the following line to the last two data fields: ReverseInput=True

Comment out this header, like so (using a semi-colon): ;[LensFlareMaterial5]. You can also delete it and all the data under the header.

Well, gee, thanks Rugg....I guess.... I actually got to go fishing on my birthday. That means that I ran the boat all day Tuesday, rigged trolling baits, stood radar watch all night Tuesday into Wednesday morning (It's not good to get run down by a 60,000 ton container ship thats making twenty knots at night, while you're drifting 100 nm offshore, you know). I then managed to catch a couple of hours sleep while my boss ran the boat the 90 some odd nautical miles back to shore on Wednesday. He managed to hit every bump in the road on the way back Once we were back at the dock, I had the privilege of cleaning the boat, the tackle, and the fish, bestowed upon me. Wow...what a great birthday present from my boss!!

Diomede Island is part of the Aleutians, but is Kolvcinskaja in Soviet territory? Don't currently have that terrain installed, so I cannot tell you for certain. One thing that I've run into (in a similar vain), was attempting to fly a Soviet aircraft tasked for SEAD, when there were no allied SAM sites defined. The mission would be abruptly cut short, while I was still inside of "Soviet" controlled airspace, and I'd be credited with a successful mission. Because (again) there were no allied SAM sites to attack. This all changed when I located a few Hawk batteries on the map. That is what leads me to the conclusion that you had no shipping routes defined inside of allied territory.

What I think is that you've really created something worth sharing. A bit of a friendly critique.....the hills (karst ridges) might look a tad more realistic if you had a few rock faces showing through, with a bit of vegatation on them.

Are there allied shipping routes set up in either of those terrains that you've mentioned?

Do you think the fact that you've declared it to weigh over 500,000 lbs might have something to do with it?

Stealth in Strike Fighters is currently an all or nothing sort of affair, and TK was made aware of it almost a year ago. A similar issue exits with chaff, and the workaround is to to modify SAHMs and AHMs so they have almost (unrealistically) perfect CS rejection values. There is also an undeclared setting for eliminating a model's heat signature (another workaround), that results in an aircraft turning into a "thermal black hole". I discovered it quite by accident, when I forgot to add a certain line to model's data.ini, and thus accidentally rendered it invisible to IRMs. The latter works almost too well....right USAFMTL? BTW, if and when TK repairs the RCS issue, here are the (accurate) values to use: B-52 H: 100 m2 * 2.12 = 212 km A-10: 25 m2 * 1.5 = 150 km F-4E: 25 m2 * 1.5 = 150 km MIG-25: 25 m2 * 1.5 = 150 km Mig-31: 25 m2 * 1.5 = 150 km B-1B: 10 m2 * 1.19 = 119 km F-14 D: 10 m2 * 1.19 = 119 km F-15C: 10 m2 * 1.19 = 119 km Su-27: 10 m2 * 1.19 = 119 km Tornado: 8 m2 * 1.13 = 113 km Mig-29: 5 m2 * 1 = 100 km Mirage2000C: 3.5 m2 * 0.92 = 92 km F-5E: 3 m2 * 0.88 = 88 km Mig-21: 3 m2 * 0.88 = 88 km AV-8B+: 2.5 m2 * 0.84 = 84 km Av-8B: 2.0 m2 * 0.80 = 80 km F-16C: 1.2 m2 * 0.70 = 70 km F-18C: 1.2 m2 * 0.70 = 70 km Gripen: 1.0 - 1.2 m2 * 0.67 - 0.70 = 67 - 70 km F-18E: 0.75 m2 * 0.62 = 62 km Rafale: 0.75 m2 * 0.62 = 62 km Eurofighter: 0.5-0.75 m2 * 0.56 - 0.62 = 56 - 62 km B-2: 0.01 m2 * 0.21 = 21 km F-35: 0.01 - 0.005 m2 * 0.21 - 0.18 = 21 - 18 km F/A-22: 0.01 - 0.001 m2 * 0.21 - 0.12 = 21 - 12 km F-117: 0.001 -? m2 * below 0.12 = 12 km.

That would require both new 3D models, and revised Data.ini files as aircraft weights, CGs, Min/Max extents, Xmac tables, (etc.) would all be effected. Oh yeah, the cockpit.ini would require a bit of an adjustment too, otherwise (from the pilot's pov) you might find yourself sitting in front of the aircraft

By the thrust of two RD-20s

BTW, the declaration is "BaseRCSModifier", not "RCSModifier".

There are no "large" bases for the reds in WoV, and the Tu-16 has a large base declaration in its data.ini file. You might try resetting it to "medium".

How many apps do you have running in the background? Tell us what's under Programs/Startup on your system.

:yes: