Fubar512

You didn't really kill the language...I mean, it wasn't that bad.....

You mean you want them to slow down, to release Bond movies at the same pace they did back in the 1960s? Dr. No = 1962. From Russia with Love = 1963. Goldfinger = 1964 Thunderball = 1965

One dozen Communist Revolutions, coming up:

Out of the "megapack", that I released over 3 years ago.

Sounds as if it's an issue with the glossiness of the 3D model, itself.

What video card are you using....a Radeon? That issue was prevelant with older ATI drivers.

The bitmap used by the fuel tank is called out in its .lod file. You have two choices: 1) create a new skin to match the aircraft's, rename it, and then live with the fact that the same tank texture will be used with ALL your other skin textures for that aircraft. 2) create a new skin, name it anything you want, other than the name used on an existing texture, copy and rename the tank.lod to whatever you like, make a new entry for it in the weapondata.ini that matches the new name, and finally, using a hex-editor, edit the bitmap callouts to match your new texture name. Of course, choice #2 requires that you proceed carefully, and having a little knowledge and previous experience doing this, is advisable.

The "tiles" aren't missing. What would be required is for someone to create a flat, horizontal .lod with a corresponding bitmap or tga, to simulate the connecting service paths to and from the launchers, radars, and service/command vehicles. The latter two types would have to be added. Kesselbrut already has SA-2s mounted on transport trailers, so we could use those.

NetworkType=AAA as would the Firecan. You can sub using the Barlock by adding the appropriate lines to its data.ini. And, all the fixed SAM sites in a default install are already in a 'Star-of-David' deployment.

No, it's not that simple, as a large, single terrain bitmap would then be hundreds of megabytes (if not a few gigabytes) in size. It probably would not even load on any machine, and even if it managed to, it would run at a frame rate even slower than that of a Power Point presentation.

No, it does not exist as a default emitter. All that using a non-existent emitter will do is give you no effect whatsoever. The available default emitters are: CleanExuastEmitter, DirtyExhaustEmitter, and HarrierExhaustEmitter.

If you understand how pulse Doppler radar works, it is less likely to be flummoxed by a maneuver like that, then conventional radar. All it would do at range, is significantly increase the target's RCS for the duration of the maneuver, and rob the aircraft of precious airspeed that it needs to maneuver. The Cobra maneuver in of itself is overrated, and is of dubious value in a combat engagement. The ability of an aircraft to bypass its alpha limiters and maintain controlled flight while engaged in a close-quarters lag pursuit, however, is advantageous. In theory, a pilot can momentarily pull lead and hose his opponent, almost at will.

System-generated single missions will pick airfields at random, as long as they meet the runway-length and mission radius criteria for the specific aircraft and mission type that one chooses. Campaigns are different, as the author can specify where to begin the campaign from, as one does in a user-created (scripted) mission.

Mobile_SAM as a ground object role does not work. Reclassify them as Mobile_AAA, and they'll work just fine.

A disturbing development......

The only reason that would happen, is if you specified an attachment type. For SAMs, that box should be left unchecked in the weapons editor.

I would, but I only know just enough Portuguese to get myself in trouble.....

Well, stealth now appears to be working the way it's supposed to. I've just set the F-117's RCS to a real-world value, and overflew SA-2 & SA-6 batteries with no detection, but got picked up at close range by an SA-10, and was promptly shot down for my efforts.

I'm using the SF desert terrain set (in WoE). I've added SAM batteries on three of the offshore islands, and they can "see" you down to 500 feet 10 nm out, and out to 40-60 miles at altitude. The farthest the SA-10 has engaged me, was at 47 nm. What sucks, is that the SA-10 radar will steer missiles down at you. I've made one concession for gameplay's sake, and that was to allow the missiles to show a contrail, even after sustainer burn-out, so you can spot them as they approach and hopefully outmaneuver them. One of the beta testers lost his entire flight of 8 in just a few minutes. Dave, OTH, is a firm believer in scorched earth policy, and launches nuke-tipped ARMs at them outside of the SAM battery's engagement envelope

Desert Storm without an F-117A? Now that would be a crime....

I just reinstalled it in WoE....flies surprisingly well in SP5 (that is, for an FM made SP4 standards). Know what? I'm going to update it and twist Marcelo's arm to release it...lol

I find the best tactic to be......

From 18 months ago. Marc took a break for a while, I'm sure he'll get back to it soon enough.

Notice that FC did not say: "Not that I would know anything about inverted high speed low level flight" Yes, the one they threw at him....