Fubar512

First, to run the shader effects, you need a video adapter that natively supports DX9.0. That would be at least an ATI Radeon 9500 or later, or a Geforce 6000 series or later (If I'm not mistaken, the GF 5FX series had issues with DX9 support). Second, you need to have the terrain and effects detail set to the highest levels. Now, the file in question is the WATEREFFECT.FX file. These are the settings that I'm currently using: const half3 CameraPos : CAMERA_GLOBAL_POSITION; const half3 SpecularColor : SPECULAR_LIGHT_COLOR = { 0.8, 0.8, 0.8 }; const half3 WindVelocity /*: WIND_VELOCITY */ = { 2.0, -4.0, 0.0 }; const half2 FogDistance : FOG_DISTANCE; const half StartFadeDist = 1500.0; const half EndFadeDist1 = 8000.0; const half EndFadeDist2 = 18000.0; const half SpeckleAmount = 0.7; const float NoiseScale = 0.0005; const float WaveCycleRate = 0.85; const float WaveMovementRate = 0.0003;

Well, it's a no-brainer (and it should have been obvious to me from the onset), but after playing with this, it appears as if the maximum effects rendering distance is still limited by pixel-size. :yes:

Terrain.FX in the "X_terrain".cat file. Thanks, Deuces...I knew you'd eventually chime in on this.

These lines do not presently apply to SF/WoV/WoE, as they are not present in the aircraftobject.dll, hence, the game engine does not "understand" them. MaxRollForGunAttack=180 CannonBurstLengthShort=0.25 CannonBurstLengthLong=0.5 MaxRudderForGunAttack=1.0 MaxRudderForManeuver=1.0 This will change when those titles are upgraded to SP5, after which they'll brought up to parity with WoI and FE.

Try using the search feature, it works well, and helps dig up lots of info http://forum.combatace.com/index.php?s=&am...st&p=149612

By editing the "MaxVisibleDistance" parameter in each aircraft's data.ini file (which you'll find under the "detect system" header), you will give AI aircraft what amounts to GCI or AWACS coverage, and all but force BVR engagements. . I generally add 10000 to the existing value. For example, if the default value is currently "8400.0", make it "18400.0". [DetectSystem] RadarType= VisualBlindArc=5,6,7 VisualRestrictedArc=4L,8L MaxVisibleDistance=8400.0 <---edit this to 18400.0 HasRWR=TRUE BaseRCSModifier=1.2 For bombers or similar large aircraft, a value of 40000.0 or even greater is not out of the question. In the case of low-observable (stealth) aircraft, I suggest cutting the distance by half or even by 75% (IE., 8400.0 to 4200.0 or even 2100.0), just to keep things somewhat realistic.

Also, I suggest that you try editing the "MaxVisibleDistance" parameter in each aircraft's data.ini file (you'll find it under the "detect system" header). I add 10000 to each value, for example, if it's currently "8400.0", make it "18400.0". This imbues the AI with what amounts to GCI or AWACS coverage, and forces BVR engagements. I suggest that you do the opposite for stealthy aircraft, cutting the distance by half or even by 75% (IE., 8400.0 to 4200.0 or even 2100.0), just to keep things somewhat realistic. Know what? I'm adding this to the Knowledge Base.

Until DS becomes available, just create an analog using one of the other radar models, and place them on the map where they would help provide coverage with as few "holes" as possible. FYI, I network some of my 37 mm guns, and all of the 57, 85, 100, and 130 mm AAA guns.

No, because flares are visually an effect, and globally, share the same values (entries) in the countermeasure.ini file. For reference these are the entries that I'm using: [FlareData] EffectName=FlareEffect MaxVisibleDistance=12000 HeatSignature=100.0 DragFactor=1.00 LifeTime=4.0 VelocityDeviation=0.3

Mach 1 at 100K feet is less than 200 knots indicated airspeed. This should prove interesting: The next year, Kittinger set two more records, which he still holds. On August 16, 1960, Kittinger surpassed the altitude record set by Major David Simons, who had climbed to 101,516 feet (30,942 meters) in 1957 in his Man-High II balloon. Kittinger floated to 102,800 feet (31,333 meters) in Excelsior III, an open gondola adorned with a paper license plate that his five-year-old son had cut out of a cereal box. Protected against the subzero temperatures by layers of clothes and a pressure suit--he experienced air temperatures as low as minus 94 degrees Fahrenheit (minus 70 degrees Celsius)--and loaded down with gear that almost doubled his weight, he climbed to his maximum altitude in one hour and 31 minutes even though at 43,000 feet (13,106 meters) he began experiencing severe pain in his right hand caused by a failure in his pressure glove and could have scrubbed the mission. He remained at peak altitude for about 12 minutes; then he stepped out of his gondola into the darkness of space. After falling for 13 seconds, his six-foot (1.8-meter) canopy parachute opened and stabilized his fall, preventing the flat spin that could have killed him. Only four minutes and 36 seconds more were needed to bring him down to about 17,500 feet (5,334 meters) where his regular 28-foot (8.5-meter) parachute opened, allowing him to float the rest of the way to Earth. His descent set another record for the longest parachute freefall. During his descent, he reached speeds up to 614 miles per hour, approaching the speed of sound without the protection of an aircraft or space vehicle. But, he said, he "had absolutely no sense of the speed." His flight and parachute jump demonstrated that, properly protected, it was possible to put a person into near-space and that airmen could exit their aircraft at extremely high altitudes and free fall back into the Earth's atmosphere without dangerous consequences. Source: http://www.centennialofflight.gov/essay/Ex...tinger/EX31.htm

Don't get too excited over Vista, as it is nothing more than the "WindowsMe" of the NT family. Its replacement is scheduled to be released sometime next year: http://www.vnunet.com/vnunet/news/2174703/...ement-scheduled

I have the S-300 system up and running as a proof of concept. It's waiting for the launcher-transporter and radar-van models to be completed.

Jedi, we have Alexandrite Lasers in our lab that are well over 1 KW. The potential from the capacitor-bank on one of those puppies is more than enough to seriously ruin someone's day.

81-83, Musically. By the mid-1980's, many groups were simply producing work, with the sole intention of it becoming MTV fodder.

Did you check the respective X_terrain.cat files for those two titles? That's where you'll find the movement.ini files.

Missiles of any type are not defined as targettable objects in this series, and there is no way to redefine them otherwise. It's hardcoded, most likely in the objectmanager.dll.

Yes, if someone decides they want to step up to the plate and record all the 1,728 possible responses.

Should be, could be...lol. The simple answer is NO. All sound events are hard-coded. While you can swap sound files (wav files) in and out for existing sound events, you cannot create an association that does not, as yet, exist.

The limiting factor in regards to seeing anything at a "vitual" distance is still pixel size. It is physically impossible to render anything smaller than 1 pixel. If you can arrange an HDR-bloom effect that renders on the order of 5X virtual size at a distance, then that would solve that issue.

The Su-30, Su-33, and the Su-34 have canards that work in unison with the AC's flight control computer to prevent the pilot from exceeding alpha limits, and to stabilize the aircraft while in level flight (an advantage when delivering weapons at low altitudes). On, the Su-33 in particular, you will often see the canards opposing the elevators during a carrier approach, helping the aircraft maintain the proper glide slope with as little interaction on the pilot's part, as possible.

Sounds must be associated to an event that's been already coded into the game. It is unfortunately, not something that's user moddable.

That would only work when applied to an individual missile in its weapondata entry. Also, it would share the same sound set with IRMs, as the track & lock sounds are global.

You cannot edit a .lod file (change its bitmap name association) with a text editor, such as notepad. A hex-editor is required to do this. Personally, I use HHD's hexeditor 3.0, which is available in a freeware version. I'm sure there are other free hex-editors out there.