Kid18120

Yeah, the team at ED itself should learn a thing or two from HB, especially when it comes to keeping the community informed and engaged

If you want to "try it out for yourself" you can always download (for free) the base DCS World, which includes a full fidelity TF-51 Mustang (basically an unarmed training variant for the P-51D) and a more "softly implemented" SU-25T (no clickable pit but all the basic functions are there via keyboard shortcuts), plus the base map. This is a good start if you want a taste of what DCS has to offer. Then you can buy whatever module you want. My suggested modules are: A10C, F/A18, F16 (when it will release!) and the UH1 for the rotaries

Yes! Finally, after years of noise about it, after a few "interesting" exchanges in a recent thread, it finally came!

The Phantom is coming. When? Whenever it's ready, but ED has confirmed it will come at some point through a 3rd party (iirc)

To fix the buggy textures for FLIR's saturation all you should need is to delete "fxo" and "metashaders2" folders in your DCS' Saved Games directory. The fact that the FLIR gets blinded can be worked around by just using visual mode insteal of FLIR and actually use the flare's illumination. I don't have this mission so i don't know exactly what the situation is like but that should do it

So basically the ME's altitude is simply the vertical axis position, or "radar altitude"

HB's F14 is the new benchmark for quite a few things, mainly - Turbulence simulation - Pilots animations - Mirrors, they are simply awesome - General airframe "feel"

Quickly i don't think but if you fancy playing with the CDU you could try setting a mark point on your current position (say it's 'A') and then use the OSET (OFFSET) page to make a second mark point exactly on the specified heading and distance from the mark 'A', but that's a lot of work for just a visual approach. I think you're best going off the TACAN readings or, if the base doesn't have any, just make a mark point in the middle of the runway using your TAD EXP modes and use the distance from there as reference

That would be awesome but if there'd be a map to go with the F16, i wouldn't expect it to be free. The free map will most likely be something that somewhat fits all the modules we have (more or less realistically). I'd be the 1st preordering a Balkans map if it would come following the F16

Yup, also strobes don't get your cockpit in disco-mode anymore! We can finally enjoy our flying at night!

Yeah being able to switch through different modes is super helpfull when it comes to keep everything decluttered. I've actually coupled Helios with a touchscreen monitor so i can interact with it without the need of a mouse it works wonders!

About 65Hs, you can force correlate to "kinda lock" to a point (won't track moving targets) and have an effective range of about 11nm if you fire from arount 17/18k ft.

Make sure you have no aicraft mods (A4, AC130 and such). In my virtual wing seems that the AC130 mod we were testing became the culprit after one of the OB updates

I can confirm almost 100% that the issue is with modded aircrafts. People here report the A4 mod but in my virtual wing we had it happening because of the AC130 mod. F18s were sinking whereas A10s were crashing as soon as wheels touched the ground on landing. Since we disabled the AC130 mod we haven't experienced any issue.

IRL you would "feel" the clicking trough the touch sense, something that cannot be achieved in a simulator (unless you have the actual hardware detent that is). The "click" workaround is good enough IMO. Those complaining it isn't realistic should complain more about the fact that you don't get fatigued after a prolonged dogfighting session, the airframes don't wear out, there's no random failures (real ones, not those we have in the ME) and so on, rather than complaining for a little "trick" that makes a big quality of life improvement

Gimme gimme! :pilotfly:

"Fixed" the issue. All i had to do was disable the Guardian function. Not sure why/how it would mess up the viewpoint in DCS but after doing so i've been flying for a few hours without any issue.

Best thread ever

i actually like the idea. It's a way to get the community together and involved in something more "intimate" with the sim, I doubt it will happen though, at least for the in-game menu background, simply because ED has it "local" to each computer and would require a patch download for it to change. Many games, especially the latest installments of known series (COD, BF, free stuff like WT and such) have part of their stuff streamed from a server, so they can alter things without the need of a download for clients (there's still a download but you don't see it anyway)

Sorry but i must ask... what part about "keep the in cockpit F1 view sounds and external F2 sounds volume separate" isn't clear ? I understand what you and your collegues have tried (and i must say managed) to achieve when it comes to have a realstic soundscap and we all thank you for this. What we are asking is to separate the F1 view from F2-F3-F4-F5 volumes. This implies that if you're on the ground and open your canopy, since you would still be in the F1 view, you would hear stuff as usual and as it is right now already. But as soon as you press any of the external view cameras buttons (at least the F2 one...) you'd get a reduction in the overall volume. I'm afraid we've stumbled in a bit of a language barrier issue here

I think we're not managing to be understood here. Let me try again. We are asking to separate WORLD volume from "external view volume". WORLD can keep operating as it is right now but give us the ability to set somewhere that external views should be quiet. QUIET not "fading", not "roll the camera away". External views are key for training in organized groups as they allow instructors to closely watch the other guy. Tell you what, how about you "lock" the external view sound level to 50% of whatever we set the WORLD slider ?... we don't want to hear MORE from INSIDE, we want to hear LESS from the damn OUTSIDE cameras

True, but you can't have split settings for external sounds while in cockpit view and external sounds while on external views. You either need to be deaf while in cockpit or blow your ears out while in external views. It can't be that hard to just add a simple function so that it reduces the volume of a set % amount when you switch to any of the external views, can it? Or even simpler add a multiplier setting for the "hear like in helmet" option. That way we can set a comfortable level on external views and just increase the multiplier for the helmet point of view. The fade in is a nice addition but once the time is passed you still get your ears blown out.

Probably not the best idea to defrag an SSD though :smilewink:

As others said above, the F18 we have is indeed working as intended, as it is pretty coherent with what we can see on the NATOPS. Also, there's a matter of "school of thought" when it comes to comparisons between Navy and Airforce integrated systems. The Airforce tends to have more "logic and streamlined" processes and HOTAS integration whereas the Navy seems to rely more on "manual MFD/DDI fiddling". As in everything military, different frames and related systems are tailored and "customized" for the end user. Navy and Airforce think a bit differently when it comes to stuff like this.

Are we sure it is an actual bug? I have no idea how it works in the real thing but i'd expect it to work as it is right now in the sim. Once you bank over X degress the R-ALT goes to 0, which is below the GCAS threshold. Once you go back to a more wing level state it resumes reading the altitude and raises from 0 to whatever you R-ALT is and triggers the warning because it does actually read that you're below the GCAS threshold. Anyone that has "their feet deeper" in the real thing can give an input here?