Fubar512

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:

That's caused by what is known as a "gross error in basic switchology"

The solution to your problem lies in the knowledge base.

F-86F, power to idle, pushed through stall at onset, ignored extreme wing rock, started to spin, extended flaps and air brakes, lowered and raised gear to disturb airflow, applied opposite rudder and pushed down on stick to recover: http://forum.combatace.com/uploads/1186108..._43_5652939.wmv

Spins have been possible since the initial release of the series (SF in 2002), if one is willing to spend 3-4x the normal time required to produce a basic flight model, and experiment with post-stall behavior. Edit & Update: Here's an example: http://forum.combatace.com/uploads/1186108..._43_2672101.wmv

The ECM (whether it's a pod or an integral unit), is always best left on, with one exception, which I'll cover, later. In short, its "working" as long as you toggle it on, although as you get closer to a radar unit, the active ECM's effectiveness is diminished, a phenomenon known as "burn through". What happens is that the signal strength of a radar in close proximity is such that it literally overwhelms any "noise" created by jamming. If you happen to get a radar missile launch warning, and notice that the missile is tracking you, no matter what, turn off the ECM unit. Chances are that the missile is set to "home on jam", and is using your ECM's jamming signal for guidance!

You either must create a scripted mission with those particular ships in mind, or you must redefine their object role as "Cargoship", so they randomly appear in system generated missions. It also helps if the weapons they're equipped with are in your weapondata and gundata.ini files. The Hawks and their supporting radars must be manually located on whichever terrain map you wish to use, as there are no fixed allied SAM sites in the default installations, other than in the OTC terrain map (AFAIK).

Really? http://www.crucial.com/store/listparts.asp...Notebook+nx6125

From past experience, I can attest to Marcelo's almost machine-like ability to multitask without sacrificing quality.

As long as you know someone who is willing to export your model into 3d Max (and then export it to lod), you can create the model in free-modeling programs, such as Blender.

I'll have to look that up, as I presently don't have an A-1 installed. I do recall that one sound event was specifically tailored to simulate the sound of an over-speeding prop, as one would hear when in a full-throttle dive from altitude, and was meant to be used as the cockpit "wind sound" for prop-driven aircraft.

That's a known isssue, caused by having an airfield listed as the first "TargetArea" entry in the targets.ini file. One fix is to renumber all the " TargetArea" entries, leaving the first entry blank, like so: [TargetArea001] [TargetArea002] Name=Elk Airfield Position=260500.000,345000.000 Radius=6000.000 ActiveYear=0 Location=1

That's barely enough RAM for Windows XP by itself, never mind while running it in conjunction with a sim. I'd say you'd want 512 mb of RAM ( at minimum), and preferably, at least 1024 mb. You can start by turning down the graphics options and view distances to minimum settings , and then bumping them up progressivly until you find a setting that you can live with.

The AI has not been programmed to jink. That simple maneuver, can help overcome a few issues...though at the cost of maintaining formation. It's something that bears looking into. The AI is not programmed to identify flex-guns as a danger, irregardless of whether they are ground-object or aircraft-based. However, the AI will use countermeasures (both active and passive) in an attempt to foil SAMs and AAMs, if they are so equipped. Both Crusader and I have experienced situations where we've witnessed AI aircraft, that were originally tasked with CAS or strike missions (A-10As on one occasion, AMXs on another) dump their a2g ordnance and engage enemy fighters. Unfortunately, this has happened only twice for me in hundred of flights, and literally weeks of tearing into the most obscure values or the most esoteric dll files afterwards, failed to provide a clue.

You mean, something like this? Video Link

The last patch added FX shaders to all the sims in the series. In short, the default terrains all have "water effects". In order to add it to third party terrains, you need to add the following lines to their repective data.ini files [WaterTextureMaterial] UseEffectShader=TRUE EffectShaderName=WaterEffect.fx [NormalTextureMaterial] UseEffectShader=TRUE EffectShaderName=TerrainEffect.fx

In the process of testing an upgraded FM, I saw something extraordinary in my cockpit mirror, and just had to snap an exterior screenie. I'm hot on a '15's tail (he's in front of me, so he's not in the image), his wingman is on mine, followed by my wingman, who in turn is being pursued by yet another '15. So much for the "ineffectual AI"

"Switches to Yoda voice" Listen to USAFMTL you will, or we'll bring down fire from the sky! CLICK ME

"Closes eyes, and uses Force vision" I can see inside your computer....you have an ATI card.....and you need to upgrade to the latest driver...or, you can turn off aircraft shadows

A flying SAM site?