Kang

The whole 'hiding behind trees' thing has actually improved vastly over time. It used to be much, much worse than that, basically AI units literally saw through everything but solid ground. It has gotten better and generally buildings and trees do prevent the AI from seeing you now, but there are a few caveats: - If a part of your plane or helicopter sticks out from your concealment, they do see you. This is a thing in DCS as much as it is in almost every other game there is. Getting AI to decide realistically on how much of something they need to be seeing in order to recognise it is just a classic issue. «Saw a tip of a shoe poke out from a shrubbery some 150 yards away. Definitely an enemy soldier there!» - If they see you diving into that cover, they can keep on 'seeing' you for a short while, despite no line of sight. This serves two purposes really. One is to simulate how a crew would try to estimate your position at least somewhat. The other, probably more important one, is to prevent ground units from completely forgetting you are there every time you fly past behind a single tree or street lamp. Both of these things do get a little worse by the fact that the AI in DCS has a 360° field of view. While some aircraft can be snuck up at from their definite blind spots, the rule is that anything that can possibly be seen by the crew, is seen by the crew. There is no chance to zoom past and get lucky because the tank commander happened to look at something else in that instance. Ranges, speed of reaction and - I believe - duration of the 'memory guesstimate' are affected by skill level.

That only works with the easy comms option, in which the radio isn't simulated.

Same way we learn everything else... we read the manual.

And I always thought it's Iceman and his pals...

Nice parking job.

Bunch of sissies, I personally black out at around 16G! More seriously, I have sincere doubts that there is a legitimate claim of that. If getting to the point in flying, I would assume having an eye on the ol' G-meter is probably not a priority, and for the centrifuge runs it is no secret that there are plenty of tricks to optimise G-loc performance for those, which mostly require you to have a fixed appointment on when you are supposed to do that.

One thing I can agree on, though, is that it would be a good idea to make a decent bundle pack with the WW2 asset pack. Perhaps that has been a thing when Normandy got released, I really don't know, but it would be a good idea for sure. 'P-47 + Normandy + WW2 Assets'. It's a little weird right now with the almost all-encompassing 50% off sale going on, but generally it would be a good thing, I believe.

Also, to be honest, DCS shines best in the simulation of systems, not in the seat-of-the-pants flying, at least in my opinion.

So... this thread then? As far as I can see this very thread is literally the only thing there is about this. Sir, I'm afraid that I cannot let that stand without letting you know that I am indeed likely to steal that statement somewhere down the line.

If that is the issue I wonder what the logic behind it is.

Decision time is looming ever closer now.

The radio selector (the PVT INT 1 2 3 4 knob) only selects which of the various radios is used to transmit when you use the push-to-talk trigger on the cyclic stick. In other words, turning that has no influence on what reception you hear.

Without having tried it at all: It might simply do nothing if your airfields are set to unlimited supplies to begin with.

I would much appreciate if ship wakes, along with smoke, would get a slight improvement across the board. As in, change how these are generated instead of fixing them one vessel at a time.

Usually this message relates to downloadable content that is actually available at the time of purchase, as in 'you cannot download this and then refund it'. I wouldn't know much about the legal side of things, but anecdotal evidence has it that talking to ED's support usually leads to some sort of solution.

That has been going on here for ages now, so the short answer is: There are two separate planes that are both designated AV-8B. There is AV-8B Harrier N/A (Night Attack, the one we got here) and there is AV-8B Harrier Plus, which carries a radar and thus is capable of AIM-120ing around.

Voice recording isn't a problem at all. Just record your voice by your preferred means, put the sound file in the mission as a radio transmission from some random nearby unit. Done.

I think I've heard the glidepath line once in the days of FC2. But it's been years and I might be mistaken.

Happy VE Day I guess, pending the 1.15.

I've had that last issue as well earlier this week, but I haven't been able to perfectly trace it to this.

I'm not overly surprised considering how well just regular 'review your own mission' tracks tend to work.

Perhaps give it a try with another module you feel more confident in with the radios (or a FC3 one). That'll tell you whether this is a UH-1 radio setting problem or a trigger transmission problem.

I'm not so sure about that. Having the two properly separate, at least for now, seems like a good idea if you want to avoid borking up quite a lot of module's functionality while working out the kinks in a new FLIR implementation. Throw the ol' Litening II at the masses, keep work up on the all-new system that everyone can easily recognise by the usage of ATFLIR, then, one day, spread the properly working interface to more applicable places.

Guess they just generally suffer from the same issues that the AI flights do as well. My favourite is always the SEAD flights who ditch their ARMs upon being painted by a search radar. Gotta keep up that manoeuvrability when dodging missiles, mind you. Some things work alright and some don't very well. Remember to tell your flight to engage whatever you are facing as soon as possible and they might do an okay job.

If I'm not mistaken, and I very well might be, you can include such files into your mission and they will be downloaded along. Just gives you a very, very long loading time the first time around is all.