Stretch

Still a full plane ... a weekend to learn, a lifetime to master.

So, Area 51 Sims is different from Fighter Ops's Area 51 product.

I've either owned and liked, or heard good things, about the following aircraft addon makers, in terms of their realism: PMDG RealAir ASA + AccuSim VR Simulations IRIS Pro series Definitely find and use a config tweaker. Even if you bought your computer yesterday.

Hotel Sierra could just as easily be "HOT SH*T" which is equally acceptable.

Hey Headspace - Any recommendations for how to bind this stuff to the joystick? It seems like we got a bunch of keys to worry about now: In-game UHF menu In-game VHF AM menu In-game VHF FM menu TeamSpeak select radio 1 TeamSpeak select radio 2 TeamSpeak select radio 3 TeamSpeak PTT Any way to combine these functions smartly?

First picture: Radio callsign plaque, and the NVIS light that illuminates it. The inset cylinder is probably related to mounting the cockpit to the frame, since there is an identical one on the opposite side. Second picture: Camera controls. The A-10 has a HUD and EO camera I think? Above picture: Mission recorder. (Google the name of the thing, it's printed right on the box: http://www.zds-us.com/21_enertecvs1500.htm )

Check the video: http://arenalogic.eu/default.aspx Some good shots of the HSD, FCR, and TGP pages in the MLU M3/M4 jets, with Link16 symbology and SNIPER video. But it looks sort of vaguely Falcon 4-ish. Wondering if anyone knows if this is a from-scratch project or if it has some heritage in common with F4?

Huh, yeah small world (the world of hyper-realistic flight sims). I should probably remove it from my sig, I'm inactive reserves right now.

In this video you can see that there is HUD symbology in the upper left that appears while the gun is firing, that has been removed from the video.

IIRC the LGB tutorial has you do auto-lasing only (where the jet will fire the laser for you), though I could be mis-remembering. In any case, manual lasing isn't hard. Just point the TGP at the thing you want to lase and hit the pinky button. You'll see the TGP range change to show the lase range rather than the trigonometric range.

Of course I can't say for certain, but here's some stuff I've read or strongly suspect: - A-10Cs nowadays use a slightly more modern avionics suite and CDU software version. Detailed info is unavailable. - A-10Cs now use the SNIPER XR targeting pod as opposed to the LITENING II. The SNIPER supports a lot of features not found in the game's TGP: Tracking multiple targets, datalinking images to JTAC units, e.g., for identification, and of course higher resolution FLIR and CCD images. Details on how much better the images are, and how the new features are implemented, are unknown. - I strongly suspect that the countermeasures system has been simplified, especially the jammer. I've seen photos of the CMDS on other aircraft, and the jammer modes are never as simple as "AIR", "SAM1", "SAM2", and "AAA". I've seen, e.g., a jammer program(?) of "XT3", and modes like "REC" (receive only?) "SSS", "SST", "INH" (inhibit?). (These are from photos of the CMDS on an F-16 and F-15 with the ALQ-132(?).) - KY-58 secure voice is unimplemented in-game. Operation of the KY-58 is well-known, it's just the actual encryption method and keys used that are unpublished. - IFF (in particular, mode-4) is unimplemented. Again, the operation of the IFF panel is well-known, but the actual mode-4 encryption method and keys are unpublished.

Yes. Instead of using the HUD, use the TGP to designate your target, then lase it by hitting the HOTAS pinky button. The laser will provide a much greater ranging accuracy. If you do still want to use the HUD to designate targets, consider this approach: 1. Place the HUD TDC over the target. 2. TMS up long to set SPI 3. China hat forward long to slave all to SOI 4. Set TGP as SOI 5. Fine-tune target acquisition 6. TMS up short to aquire target 7. Pinky switch to lase and get more accurate distance 8. TMS up long to set new SPI

Nice to see some people bother to do a little searching before posting a thread. OH WAIT!

You will generally have to do quite a bit of diving for CCIP with no consent-to-release (CR) mode selected. If you select 5mil or 3/9 CR modes, you can do level or nearly level CCIP deliveries. The difference between 5mil and 3/9 is the amount of tolerance allowed in your deviation from the PIBL. If you select 5mil, you have to have the PIBL within the 5-mil time-to-go dot at the moment of weapons release. If you select 3/9, the PIBL only has to be within the pipper. If the PIBL is in the wrong place, you get an X. For CCIP, you'd generally select 5-mil when you want to hit a precision target like a specific bunker or vehicle, and fly the PIBL very accurately down to release. You'd choose 3/9 if you're dropping area weapons like CBUs, or if you're ripple-bombing for area effect. I'm not sure about CCRP; I think it might be 5-mil automatically. Other reasons why the "X" could appear include busting your minimum escape altitude. Note the staple on the PIBL ... that staple marches down the PIBL as you approach your min safe altitude. If it passes the pipper, you're too low to get out of the way with a standard 4-g escape maneuver. So you want to adjust your bombing parameters to keep the time-to-go circle between the staple and the pipper. This may be impossible if you start your run too low or your dive angle is too steep to allow a pullout in time. The escape maneuver is used to calculate error tolerance for the safe escape altitude. a climbing (CLB) maneuver will require more altitude to execute than a level turn (TLT) maneuver, so the aircraft will require you to pickle and come off target sooner.

Unlike ol' Mower, combat isn't everything for me. I'm happy to take on the challenge of being master of my aircraft, which people can spend an entire lifetime attempting and never fire a single round.

I've never seen an accelerometer whose button did anything BUT reset the needles. We've got a Citabria at my flying club and the purpose of the button is to reset the needles so that the guy who booked the plane after you doesn't know you exceeded the 5.5-g structural limit when performing your split-S. (Oops.) I imagine that similarly the purpose of the reset button in military aircraft was to save you the embarrassment of having your crew chief know that you over-g'd the airplane on your last sortie, but nowadays with flight data recorders on all these aircraft there are no secrets.

OK Vega, you seem to be missing out on a few important facts here. Let me help. Firstly, part of the reason you're seeing very low frame rates is because DCS: Warthog is not yet a finished product. Beta 4 introduces some optimizations but the work is not over yet. Frame rates will go upward as we near release. Secondly, and this is very important ... you seem to be under the impression that graphics are handled entirely by the GPU, and flight dynamics entirely by the CPU. This is a simplistic and entirely untrue impression of how video games work. Rendering realistic graphics and complex terrain requires both CPU and GPU cycles. All the GPU does is take a 3D representation of your view and turn it into pixels on the screen. In doing so it can add a bunch of really cool features like haze or motion blur or anisotropic filtering, but that's not the whole story. You need a CPU to generate that 3D representation in the first place. GPUs do not process terrain meshes. GPUs do not populate the world with auto-gen buildings and trees. GPUs do not modify the A-10C model to correctly position the flaps, gear, speed brakes, ailerons, elevator, refueling door, lights, etc. CPUs do all of these things ... and they are a part of graphics rendering. And let's talk about the level of terrain detail in these Hawx images. I'm guessing that the vast majority of your impression that Hawx has excellent graphics is the satellite imagery used to make the textures (whereas DCS: Warthog uses generic land tiles). Good news! The Nevada terrain also uses texture-mapped satellite images, so it's a fair bet that you'll be seeing more of that in future DCS releases.

http://forums.eagle.ru/showthread.php?p=1027128#post1027128

The manual gives an example of a use for 3D nav: In an IFR landing with no ILS, you can set a precision waypoint to the end of the runway, and use 3D navigation to get your glideslope bars to indicate a GPS-guided approach to the runway at a 3.5° glideslope. My question is ... how is this done? The manual talks about how to use the 3D nav features of the EGI but never gives a step-by-step. My guess is: 1) create a waypoint at 0 AGL over the runway; 2) create a waypoint some distance back at an altitude corresponding to a 3.5° GS; 3) set the WP attributes of the touchdown waypoint to be 3D nav and approach precision. Is that all there is to it?

If your "ground crew" consists of men in light, dense desert pattern BDUs carrying M-16s ... better exit the jet niiiiice and slooooow.

Just a quick question; found the manual unhelpful in this matter ... if I have a waypoint with a manual elevation, how do I set it back to coordinate ranging? Or, asked another way, if I have a waypoint up in the sky, how do I snap it to 0 ft AGL?

64-bit Win7 and the driver version is actually 6.8.0.52, not 49. Think that means they shuffled the axes around in the registry? I'm testing it using DCS: Black Shark, not the Saitek program.

I've tried both your original reg files and I've tried changing them. I run the uninstall reg file between each change.

Axis #7 (the new axis added by the reg file) works, but the axis I replace does not. I can do this a hundred different ways and it all comes out the same: Add a ministick axis, it works. Replace an axis with a ministick axis, it does not.

Questions... Do I need a certain profile activated in order for the axes to work? Should the ministick axes be set to "Fall Back" or "Unprogrammed" or just left as the default? Do I need to re-plug the X65F after applying the registry changes? Or should it work immediately?