Jump to content

MavenRaven

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Thank youuu, tried it with a couple of modules, all worked! Edit: Thanks, that AI option could be useful in the future! Now that I re-read it my question was unclear in that regard. I was specifically looking for that one trigger condition for the Player. Works like a charm, problem solved . You guys dropped this:
  2. I want to keep a Mi-8 at a certain radar altitude range. I saw this done in Gazelle missions with the RADARALT parameter, but for the Mi-8 this doesn't seem to work. Does the Mi-8 have a comparable parameter? Or is it because the radar altimeter on the Mi-8 can just...stop working sometimes? I know there are ways of exporting this list through third party software, but I had no luck getting that to work...also I just need this one parameter, not building a huge campaign here Hope somebody can help Or maybe there's another way to check if an aircraft is X meters above ground?
  3. OK, so I tried to reproduce this myself and no luck?! The engine just restarts with no problems -_-' Well, topic closed until I can actually reliably reproduce this state. Now I'm really curious what the hell was I doing wrong
  4. Element not found This link seems to work though: https://www.digitalcombatsimulator.com/upload/iblock/3a2/DCS-Mi-8MTV2_FlightManual_EN.pdf
  5. So was just playing around with the Mi-8 startup procedure and ran into a simple problem: If at any point during the engine startup procedure I shut the overhead fuel valve to that engine, the startup procedure fails. So far so good, as expected. But, then I can't figure out how to re-start that engine. Trying the normal procedure results in the engine warming up to about 20% and then dying again. Any tips how to recover from a failed engine startup?
  6. Really feels like a bug to me. If it's not a bug then at least it's bad player experience. Still present in 2024. (Latest Open Beta) - The APU turn off makes you wait like 3mins (maybe for engines warming up? IDK) and highlighting PRESS THE TURN OFF BUTTON, even after you pressed it. It would be better if it reacted to the button press and told the player "now wait until X happens" at the very least. - Same with RADAR ALTIMETER power. Makes you wait for like 5 miniutes after that step with no reason given. If this is correct behavior at least give explanation what the wait is about. Other than that I think the startup tutorial was pretty solid. Really hope this gets fixed in the next ten years or so Edit, for posterity, more bugs found: Doppler radar tutorial also mistakenly lists the [AFT] distance key as "H" which it definitely isn't by default. </necromancy>
  7. I'm going to bump/necromancy this since I wanted to update the P51 gauges for myself and ran into similar issues. I wonder if the green bars are somehow a separate part of the 3D model and thus their texture could be like 3 green pixels on any of the texture sheets...that would be a bummer. BTW, bonus question: Is there a way to make a proper mod out of this? I mean one that installs into %userprofile% like liveries, rather than having to replace the original mods .zip file? Thanks for the help
  8. Seconded the Heli question: Is the Apache a possibility? (And Hind, if that makes sense, I'm new to these things ;)).
×
×
  • Create New...