GrEaSeLiTeNiN

On the ATTK RDR page, I do SCS depress-release then right all under 1 sec. If you have the AZ/EL page up on the next DDI, you can see the scan action - the momentary 2 vertical lines. (It's still SCS to the right even if the ATTK RDR is on the left DDI.) SCS in the direction of your ATTK RDR DDI that is currently SOI gives you AACQ-STT.

I don't think ED will budge on this if they believe it is not in their F16 modelled. But perhaps as an option under Special options? Or is it possible for someone to mod this?

This was some time ago. IIRC, I think what I was trying to say is that if you try designating a fast moving vehicle say at 49knts in an F-18 with the litening, the LGB will likely miss. Though your bomb fall line/release cue is continuously being updated and the litening is nicely tracking the vehicle, the whole setup is only accurate at time of pickle for the moving target's current location (at time of pickle). There is no lead added or calculated in the sim to account for the fact that the fast vehicle would have travelled quite a distance between pickle and bomb impact. (I don't know how it is done in the real litening pod.) The bomb will try its best to follow the laser reflected on the moving vehicle and usually has enough energy to still hit slow targets like tanks but not fast vehicles. That's how I currently understand it.

Please fix this broken mission option. We need it for practice.

I have this question: While diving away, do you not need to keep the AIM120 within a certain cone region from your nose radar so it gets the updates from you before it goes active/autonomous? Or are we just hoping the missile's own trajectory was enough if fired well within the ASE circle so that the target would be within the missile's own radar scan when it goes active? (That said, with labels on and as a last resort, I've often had success using maddog.)

v0.4.1 has been around since Oct 2023. I don't think it's a beta thing like a module. It's working just that it's a bare bones campaign generator. Along the way, they will add more features as they might have planned or if they take on suggestions by users. Being able to change your loadout should hopefully be added soon.

Did some internet searching. I'm no pilot but this (DOPPLER pg 118 which references Fig. 4.1.10 on pg 131) seems to describe what DCS Gazelle's ADI is doing in DOP (Doppler) mode. If correct, then the grey vertical line represents the L/R velocity while the horizontal line represents fore/aft velocity. They seem to work that way in the sim such that when the lines form a cross in the ADI's center, I am in a hover with zero GS (as mentioned above). Chuck's Guide mentions Doppler Sensor, Doppler Radar with regard to the NADIR. I think turning the ADI dial to DOP uses the NADIR's Doppler system?

Ah ok, I learned something new today. So I turned the ADI dial to DOP (Update: English pit erroneously labels it as WPT. When mouse cursor hovers over knob, tooltip shows DOP.) and the ADI vert and horiz grey bars needed to form a cross at the center, then I am in perfect hover position with 0 knts GS (though a slight roll might be required as can be seen in slip ball indicator). But what is DOP? Doppler? The English pit and Chuck's Guide translates it to NADIR Waypoint. However, even if I am pointed away from my current selected waypoint (as shown in HSI), how is it that I am still able to get those grey lines to form a cross in the center of the ADI (when I want to be in a perfect hover). Should not the grey vertical line be off to one side if I am not pointed at my current waypoint? (Update: As indicated here, I believe the English pit and Chuck's Guide should make the correction to Doppler instead of Waypoint.)

Thanks. I tried the NADIR but not sure what indicated slipping forward/backwards. That said, I went back to looking at the ADI and paid attention to the slip ball and roll arrows. That helped with the side slip. I still look at the tablet GS to gauge forward/backwards slip. I just try to bring the GS down to about 5knts. I can roughly tell if it's slipping forward or backwards from the way the GS increases or decreases when I pitch forward or backwards though I could never get the GS to reach or pass zero. I thought at some point between slipping forward and backwards, the GS would pass through zero. I guess there was still some side slip.

Thanks! That solved it. (Caution warnings go away when I push the fuel lever fully forward again. Just have to flip the AP switch back up.) Seems the 3-position starter switch is an old issue discussed here and elsewhere. Not sure if they ever found the right answer. But as far as the sim is concerned, as you mentioned, the switch should remain in the up position. I find it strange still that a combo of fuel lever back slightly momentarily with the starter switch in the Off or Vent position could end the Gazelle in mid flight.

It's more work to set up the bindings now but I think one advantage is that you can map the same button or switch to do one thing as pilot and another as copilot without using a modifier (similar to the Apache). But it can be a bit confusing too in that many bindings are still shared and repeated between pilot/copilot, ie, you bind them in the pilot tab only but they will also work when you are copilot, which is useful for solo play.

When in a higher altitude manual hover with a bit of ground speed (I usually check the GS shown on the 'iPad'), is looking out the window at the ground the only way to tell if you are sliding forward or backwards? (There's the artificial horizon indicator but I find it's not that helpful when the GS is slow.)

But if we can simply put back our backup config input folder or reload the saved profiles, I don’t get why it needed to be changed in the update in the first place. In the Gazelle, seems you can load up your old profile but there are some amendments and tweaks to be done as they split (yet shared some) bindings between pilot and copilot. A heads-up on the change to bindings on modules affected in the update would be helpful. Apache seems ok for me, no change, laser still works as mapped.

It was set as a slider with deadzone and reduced Y sat to make sure it goes betw 0-100 but that warthog lever of mine is a bit finicky and requires recalibration after some time. It wouldn't have been an issue if the Gazelle didn't die from 1-2 secs of just a slight fuel lever movement. Not sure why that is though. Yeah I know what you mean, lol

Ok I found the problem! The fuel flow lever was bound to my warthog throttle grey slider for both pilot and copilot. Even though it was fully forward in the sim pit, the axis was a bit jittery (hardware issue) and any reduction in fuel flow caused the engine problems. So I removed the binding for the pilot first and everything was ok when in the pilot seat. But I could still move the sim lever as pilot (using the grey warthog lever) because it was still bound in the copilot bindings and that caused the engine to fail again. (I understand this is inherent in the pilot/copilot bindings - some pilot bindings will work when you are copilot even when they aren't bound in the copilot settings and vice versa.) So I removed the fuel lever binding for the copilot as well and now the problem is gone. But I am curious. Why does a momentary short move backwards of the fuel lever cause these engine problems? And even if I promptly return the lever fully forward, I cannot recover from it though the AI is able to (when I jump into another Gazelle).

Yes I did bind the fuel lever to a small slider. So I did check and the fuel lever in the sim is fully forward as can be seen in the track.

The rotor brake is forward (released). Fuel flow lever is also forward (opened). Mission starts in the air.

In this attached track of a custom made mission, I enter the M (and later L) versions of the Gazelle in air starts. But very soon, the engine just quits, various cautionary lights come on, and the Gazelle loses power and falls out of the sky. Really puzzled. What am I missing here? For info: Hotas throttle pushes forward to increase collective. Engine failure option turned off in the Special options (made no difference on or off). Sand filter was turned on after entering pit (made no difference on or off. I have set 40% fuel in both M and L Gazelles to make it lighter at 89% weight. South Atlantic map 10deg C. Unlimited weapons set. SA342 Falling Out of Sky.trk

On a side note if you are interested, you can check out JTAC automatic targeting and lasing using MIST and CTLD scripts. Great for testing or practising LSS/LST weapons in various modules w/o having to do a 9-line.

There was not a long list of updates to it, mostly exterior textures, athos, liveries and AI gunner. Granted that might be a lot of work still. But the main issue to me has been the broken AP which can mess up the FM. That was not listed in the update.

In the vid, the first set of sounds were the photographer's camera clicks? Then there was some other sound as it pulled nose up followed by a 'drum beat' sound. Couldn't tell if it was the gun.

As far as I can tell, AP altitude and AP speed are not working. AP hover and AP auto slave (does not work for Athos) kind of work in that the Gazelle is stable for a while, then for reasons unknown to me, it just goes crazy on its own with pitch and roll oscillation (but might still hold its position in the air) or you might find your Gazelle upside down esp after using auto slave too much. In all, I feel it's much worse than what we had to go through with the Apache.

When you map to your hotas the auto hover and auto slave commands available only in the pilot bindings page, those buttons mapped will also work when you are copilot in solo play. Just leave those same buttons unmapped in the copilot page. For control of TV/periscope, I mapped it to a 4-way hat on the stick.

Same here, unlimited HOT3 does not work.

Yeah I found too that the gunner's aim is often near the target but just off, even with stationary targets. Active pause and he could still miss.