Jump to content

GrEaSeLiTeNiN

Members
  • Posts

    1230
  • Joined

  • Last visited

About GrEaSeLiTeNiN

  • Birthday 01/01/1968

Personal Information

  • Flight Simulators
    DCS FA-18C | F-16C | JF-17 | F-14A/B | AH-64D | UH-1H | Supercarrier

    BMS 4.3X
  • Occupation
    Engineer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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?
  3. Ah ok, I learned something new today. So I turned the ADI dial to 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?
  4. 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.
  5. 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.
  6. 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.
  7. 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.)
  8. 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.
  9. 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
  10. 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).
  11. 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.
  12. The rotor brake is forward (released). Fuel flow lever is also forward (opened). Mission starts in the air.
  13. 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
  14. 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.
  15. 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.
×
×
  • Create New...