Sinclair_76

A 130% dual engine overtorque with the collective in that position? I guess the flight model needs some work.

Would it be possible to implement the bookmarks in kneeboard builder? The amount of pages in the CL is growing steadily and it would awesome to have bookmarks preset in stead of doing in it during the startup.

I would suggest tabs as permanent pins , which can be named. And then the labels we have now as temporary ones.

IZLID's have been mounted to the 30mm to enhance coordination between air-ground units. It's only visible with NVG and not FLIR. The lasers have been used a lot to point targets out for aircraft The other way around an IZLID mounted on the gun can be used to point out feature/subjects of interest to ground forces in a visual manner.

I know it's a lot to ask. But the amount of information you can feed into the system is a lot more than currently used by fw assets. There needs to be a way to feed all that info to the aircraft besides fat fingering for the better part of 30min with the amount of entry errors to boot. data Comms VHF/UHF/FMx2/HF for every unit Waypoints/TGT/coordinating measures/Route's/Maps Laser codes Default modes for systems

Something that would help, is boresight targets akin used for the AH-64 outfront boresight as a static item. These targets can than be placed wherever and used to expedite the procedure. The boresight itself can be done quite fast, it's the search for a good target to boresight from that is the problem.

You can dump the rack in the viper as well. Once in the S-J page tap the station once for the load and twice for the rack and station.

Because it's supposed to be a simulator?

I had the oscillation yesterday. Of course I forgot to save the track file. So reproducing observations from memory. Winter conditions in Caucasus. CAVOK so no icing conditions encountered. Hot start with at least a couple of minutes (5?) to taxi prior depature. Because of hot start skipped the usual checks. I was in flight for about 30 min. Oscillation began after transition from 30.000' in a high speed dive to low level. It started roughly at 25.000. Began mild but with increasing speed became more violent. HUD CAS was at 250, the analog speed was at 0. The Viper was producing contrails. I did a quick panel scan but noticed nothing wrong, no abnormal indications, mc or advisory lights. Because of the strange speed indications I suspected icing. I checked the probe heat but I think it showed on. After that I checked ENG ANTI ICE and it was in AUTO. I turned it to on. A couple of seconds after that the analog speed indicator came to life, HUD speed increased and oscillation disappeared. Resumed mission profile. Further observations. In the manual it states that probe heat should be turned on as late as possible due to prevent overheat (would an overheat trigger master caution panel?). It was on +/-5min prior departure. In the manual it also states the ENG ANTI ICE prevents ice build up on the probes and engine. Are the mentioned probes responsible for standby/analog airspeed indications? Is the FLCS coupled to those probes? I will to recreate.

Honestly the AH-64D is a ton more intuitive than any platform currently offered on DCS, with maybe the exception of the JF-17, which I know almost nothing about. Sight provides a direction (a vector if you will) and a sensor can provide imagery of the assigned sight.

The position of the sensors (PNVS/TADS) in relation to yourself also takes some getting used to. Furthermore NVG's are able to pick up IR lasers like the AN/PEQ-2 or IZLID. And that makes an additional item for the wishlist. Mounting IZLID on the gun for air-ground tgt handoffs and/or coordination. Not sure if you can find it in the -10 or if it was common as early as 2002.

1988 or maybe early 1989. I was a huge fan of microprose.

Controls, as in plural. For MPD pushbuttons, I suppose, you only need to let go of the collective.

3rd fastest way to die, a PF use the cursor while flying NOE. Just behind letting go of the controls (without any hold modes of course) and low speed IIMC.

If we're playing this game...

Internal and external boresight are needed to correctly allign the laser, DTV and FLIR. For the outfront boresight an outfront boresight target would be really helpful.

There's a euro defense manufacturer which has missile approach warning sensors on F-16 rated TER's. Apparantly all EPAF countries have added them to the inventory. https://www.terma.com/press/news-2017/missile-warning-and-3d-audioanr-for-belgian-defence-f-16/

As in the AAR refueling door?

Wow talk about a flash form the past. I was lucky to fly with Richard in his online group in 1998. Can you confirm he's involved with this project? That would be awesome.

Trying to recreate the pull up profile in the F-16C manual (p 285). I followed the steps but I can't get it to work. In A-G master mode using a CCIP (mk-84) in 1 profile. I can fill in the DED information but when I want to M-SEL (0) the TGT-to-PUP line it won't revert to inverse colors (black letters / yellow background) as in the manual, and the PUP symbology is missing. Am I missing something?

Furthermore AMASE was introduced in 2004. Two years later than planned reference.

The ORT has a old style display in front which can show video of the DVO. The heads down display is there mainly to use the DVO without any electronics (in case of EMI) and in color. You could bypass the ORT (int and ext) altogether by using either MFD.

I vaguely remember turning down the radio 2 volume all the way down for fm to work.

On the SA-18 is IR guided, the SA-19 missile however is SARH. It does have CLOS feature as backup or in emcon conditions. If and when the radar is turned on the SA-19 shows up as 19 on the RWR as well as the HARM WPN pages (table 2).

JSTARS are able to communicate directly to block 1 and 2 -64D via the IDM. Not sure if the 2002 block 2 already has Link16.