Jump to content

Ironhand

Members
  • Posts

    5892
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by Ironhand

  1. Out of curiosity, should we take this to mean that it will not carry the ER variants of this missile?
  2. The primary difference will be in the systems modelling. We will not be getting a more modern version of this MiG. So, if you consider the FV3 version not worth flying, this one won't be either.
  3. Never mind. When I checked the mission, I didn’t realize there were multiple S-300 sites scattered around the periphery of the Caucasus map. I only saw the units in the Crimea. I thought those were the units I was watching in F8. It was another set of units. It may just be that, in the simplified world of the DCS SAM environment, the 76N6 Clam Shell can’t stand on its own. For that matter, since it’s a specialized low altitude search radar, I doubt it’d ever be fielded on its own without a Tin Shield or similar search radar along.
  4. The mission is bugged. There was an issue with the F-16 (?). There was something weird going on with it when I highlighted it. Anyway, I removed it and the SAMs launched. I had also coincidentally moved the two remaining aircraft further out. Not sure if that also had something to do with it but I doubt it.
  5. I think one of the FC3 aircraft requires you to start one engine at a time. Not sure which because I always start them in sequence. Can’t check which because, at present, my computer is very broken.
  6. No auto start because it’s really not needed. RShift + L turns on electrical power to all systems. RShift + Home starts both engines at once or, if you prefer, RAlt + Home for left engine start RCtrl + Home for right engine start.
  7. The first thing to do, when you’re experiencing something few others are, is to uninstall any mods you have, whether they are aircraft specific or not. If you’ve already done that, well… The next thing would be to rename (not delete) your DCS folder in Saved Games so that DCS can create a new one in case there was something in there not mod related. Also try doing a slow repair. Anytime I’ve had issues, one of those solved the issue. In the case of the first two, you’ll then have to spend additional time experimenting to see which item is creating the problem. But at that point, at least you know where to look.
  8. The latter. It’s a full fidelity module, not an improved FC3 one.
  9. That’s Sharkshook “blockletter regular”, isn’t it? https://www.dafont.com/blockletter.font
  10. I think I should probably stop participating in discussions. I’m more often wrong than right these days it seems.
  11. Spent a bit more time this morning and finally got the target lock designation (AC) but not until after I had already received permission and launched the missile which is the reverse of how things should work.
  12. You can start the engines and get everything set for taxi. You just can't move the aircraft until the alignment is complete or you'll have an issue.
  13. What I noticed, when I took a second look at the flight, was that KC never chanced to AC indicating a target lock. I just suddenly had launch authorization.
  14. It's max range is 10-12 km which doesn't mean that its range is always 10-12 km. The range will depend on altitude and other factors. About 9.5 here I had just launched the first and was about to launch the second.
  15. Thanks all, for the explanation. @Seaeagle, that all makes sense now that I understand the reasoning behind it all.
  16. I’m not clear on something and, hopefully, you can explain it. “Field of regard” is the total area that can be captured by the sensor. “Field of view” is the angular cone that can be perceived at a particular moment in time. What is the “targeting angle” and why is it different from the “field of regard”? Or is the targeting angle simply how far the sensor can slew? In which case there’s no problem covering the 75* field that it can cover. Sorry. It’s been a rough few days and my brain’s a bit fuzzy.
  17. So does your original post reflect a powered glide (idle engines) or a non-powered glide? Just curious.
  18. Since asking the question, I made a few experiments of my own. I assume my engines are out due to having run out of fuel. That seems more likely than losing both due to battle damage since, when that’s the case I’m usually missing a wing or two as well. At any rate, assuming empty tanks and nothing hanging off my wings, best glide speed for distance seems to be right around 400 km/hr. 300 km/hr, on the other hand gives significantly more glide time, if you’re searching for somewhere nearby (field, road, etc) to touch down.
  19. That’s because I wrote that without checking to make sure that the “old” clouds were still being used. At one point they were. That is no longer the case. So, until ED reworks fog to work with the new clouds, the result will be what you’re seeing.
  20. My assumption was that it was “0” wind. As for the rest? Well… IIRC the best speed for glide distance in an empty Flanker was around 400 km/hr. So I was wondering what he found. I don’t think I ever bothered to check speed for glide time.
  21. Out of curiosity, what airspeed and/or sink rate did you use to achieve that 10:1 glide ratio?
  22. In that case, I would be wrong. I was basing my comment on the Su-27 manual which made it sound like a 3-position switch. EDIT: Though I do wonder why you would need a “Medium” position marker, if there weren’t discrete stops. All you’d need is small/large.
  23. 3 position rotator: Small-Medium-Large EDIT: Used to set the target base size when using the cannon in “predicted target” mode but it’s also used with A2A missiles. Just don’t remember why for the latter, at the moment. It may have to do with the proximity fuse.
×
×
  • Create New...