Fubar512

The range-gate is the vertical bar that appears to the left side of the Mig-23's HUD in that video. As Crusader states, we can "project" a digital range readout on the HUD, but not a working range-gate.

We can display a radar and IR target box (once a target is aquired). But, the range gate and target return we saw in that video won't appear, or rather, won't work, as it cannot be projected onto the HUD glass due to the limitations of the avionics code (avionics60-70.dll). The gunsight is easy to do, though.

The problem is that you cannot project radar data onto the HUD glass in this series. No range gates, target symbols, etc.

In this series, guns that are mounted on aircraft, and that are designated as "flexguns", are for defensive purposes only. As such, they cannot be controlled by the pilot, and will only target other aircraft. Conversely, weapons mounted on ground objects can be designated as having "Air_and_Ground" capabilities. Hence, they will be used against any enemy aircraft or ground object that is within that weapon's (and its tracking and targeting system's) range.

Assuming that you've added 3rd party gun entries: If you have no guns showing in the gundata.ini, then it is hosed. If you do have guns listed in the gundata.ini,ini, but do not have them in-game, delete the gundata.dat (not the gundata.ini) file, open the gundata.ini using the gun editor, save it with the gun editor, and all should be fine. BTW, a thought just occurred to me...you do realize that the gundata.ini and .dat files do not belong in the weapons folder, right?

LOL.... It's going to be at least a week, as I'll be away on business until at least Friday night.

Yes, it's WoV with Brain32's hi-res tiles.

The subject of my next FM project, by request: VIDEO

That figure of 50,000 feet per minute is the initial climb rate, and not to be confused with the Lightning's actual time from sea level to 50,000 feet.

Hawker, This is waaay out of character for you, man. Relax.

This video was made using the default Strike Fighters desert terrain, and various third part add ons, with the exception of the carrier, which is a WoV model. http://forum.combatace.com/index.php?autom...si&img=4306

Dude, that's way too much of a stretch, even for a bungie cord.

While that might sound reasonable, keep in mind that canrads are both lift and control surfaces, and as the latter, they should be animated, something that'd probably be impossible as a loadout. A better solution would be to (respectfully) ask the Mirage Factory to add the desired features to their D-model, as they have the original source files.

Hey Bob..................

It's not that's its cheesey or bad looking. It's absolutely pointless, until TK fixes pitch-linked TVC, as it only works backwards (pitch down), at present. That being said, the MiG-29 OVT FM should be of guidance. Keep in mind that the Active prototype also sports canards, something that you cannot add unless you have access to the original 3D model source files.

Sure you could do it, if you wanted TVC that either worked only in pitch down, or was rigged to pitch up only when you wanted to pitch down. Kind of silly, as far as I'm concerned.

Domino's sugar daddy Just make sure that you're not told to put your Vulcan down anywhere near a place called the "Golden Grotto".

In five years of modding the SF series, not once have I seen an AI jet run out of fuel.

So, are you implying that my 1977 Oldsmobile Delta 88 was paying homage to Adolph Hitler? I think not.

Perhaps it is not true of AI prop aircraft, but Kodiak is absolutly correct in his assesment regarding jets, they will not flameout when out of fuel, and can even engage afterburner with empty tanks. In the image below, notice that #12 (my wingman) is out of fuel, coasting down from a Mach 1+ dash, and that despite reading zero fuel, there is exhaust pluming out both engine nozzles.

Sounds as if the data.ini for that particular MiG-21 is an older, outdated version. The Thirdwire MiG-21 series went through an update a couple of patches ago, and certain coordinates within that model have changed, hence using an older .ini would cause the anomalies that you're experiencing. The fix is to either edit the entries manually, or to use a more recent data.ini file.

Nope. It's hardcoded and therefore not moddable by any .ini tweak.