Jump to content

Ironhand

Members
  • Posts

    6210
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by Ironhand

  1. Yes, the increment is in 2km units.
  2. This was something I was working on years ago. I had uploaded it to YT to see what the start looked like. But life overtook me and I never finished it. There are no arrows pointing to what I’m referring to but you’ll know where to look. It might be somewhat helpful.
  3. Just checked your TRK. The closing rate is much to fast to be playing around like you were at that range. By the time you set yourself up with what you thought was the right elevation, the range was down to something like 8 km. So they were now well under your setting. I took control of your TRK at the start and flew it without changing the expected target range. Take a look. That's a pretty intense scenario and I was more concerned with surviving than making kills. But picking them up wasn't a problem. TRK attached. Ironhand-n001 no track.trk
  4. I never bother with the expected target range setting because it makes your life more difficult than it needs to be. If you leave it alone, unless there’s a huge altitude differential, the most you’ll need is +1 for the target elevation…+2 if they’re right on top of you. In your scenario, if you want to use “expected target range”, increase the target elevation +1 for each kilometer the targets are above you. +4, +5, means that they are 4000 or 5000 meters above you at 20 km distance. If they’re 2000 m above you, it’d be +2.
  5. Piece of cake. Can do it every time, even with my eyes closed.
  6. Patch delayed again? Guess I’ll just go and fly. Beats hell out of not flying for 3 or 4 days while the patch downloads.
  7. Yes. It’s quite elegant being able to get those views in F1 rather than having to rely on F4, etc.
  8. Like CommandT, I was trying to understand what was different in your example because it’s never worked that way in any other pit I’ve sat in. After trying several variations on a theme, I concluded that it had to be the aircraft itself. So I installed it and voilà. Gotta love “free to try”.
  9. It's an F-16 thing. Just installed the F-16 to check and it works in that pit. But not in any other that I've tried, as soon as you hit those view keys in F1 view, you have taken control of the view and the pilot responds to your inputs. In the F-16, that doesn't happen.
  10. Yes, ED is aware.
  11. The only solution I’ve found is to fly with no clouds.
  12. Remove the clickable cockpit mod. And, if you're not running that, then remove whatever mods you do have installed because one of them is causing the pipper issue at least.
  13. Never tried to do what you’re attempting but, in F1 view, holding down the CTRL and SHIFT shift keys, while pressing the NumPad direction keys will allow you to move the camera position within the cockpit. Then, maybe, CTRL and NumPad “/“ to pull back? EDIT: Forgot to mention that, what you see will depend on what’s in the F1 cockpit. Not all pits have the body modeled. And some have the body but no head.
  14. Glad you figured it out. Enjoy.
  15. Works fine for me: Default: Barthek Basic: Barthek Snowless Added: In your screenshots, it looks like "snowless winter" somehow got added to Barthek base install. You're showing Snowless Winter in the bottom image but I don't see it listed in GME.
  16. And here’s what I get for the Su-25: I don’t have much of anything for the Su-25T. Just “смотри табло” “watch/check the panel” above the AoA/ G-meter, when a panel light comes on. And “пожар” “FIRE” for an engine fire—one of the four panel lights under the HUD. If you see a specific light come on that I don’t have labeled, please ask about it.
  17. Here's a start for the Su-27 and MiG-29 respectively: Haven't paid much attention to the Su-25/-25T. If I get a chance, I'll take a look. BTW, not every one of those lights is used in FC3.
  18. According to the announcement on the DCS website:
  19. Dumbed down in the sense of simpler systems handling. What’s the alternative? Paying for the same FF version again?
  20. As do I. BTW, have you tried redownloading the mod?
  21. Does this mean that you did a slow repair? If not, then that needs to be done.
×
×
  • Create New...