ams999

What's your DCS folder in Saved Games called?

I get a Mig-19P folder with 20 pictures and a kif demo.avi so it looks like it works.

Aber jetzt mit Schriftzug :megalol:

Korrekt.

Auch die Base ist die gleiche geblieben, jetzt mit einem hübschen Namen.

Depends whether this still applies and I'm afraid it does: Developer confirms Littlebird AH-6/MH-6 will never come to DCS due to classification.

You're welcome, glad if it helps!

For anyone who wants to remove the tint here is a small description.lua - simply extract and drop the folder Cockpit_F-16C into your SavedGames/DCS/Liveries. No other changes are needed and it passes IC. I also hope there will be a special option between 'tint' and 'no tint', that would be the easiest...

A quick and dirty test shows it does work - but there still seems to be a slight tint.

It seems to me the old textures are still in the F-16C-CPT-TEXTURES.zip: I see f16c_glass_canopy_dif.dds and f16c_glass_canopy_gold_dif.dds f16c_glass_canopy_refl.dds and f16c_glass_canopy_gold_refl.dds and f16c_glass_canopy_refl_RoughMet.dds and f16c_glass_canopy_gold_refl_RoughMet.dds So maybe only a description.lua is needed.

I bought a replacement grip October 2017 for € 114 shipped to Germany- guess the price hike (+50%!) took place some time between those dates, maybe because they already knew what they were planning :megalol:

Ein Paar ging bei mir automatisch (hilft jetzt natürlich nicht), aber spätestens beim dritten MFD hatte ich dann ähnliche Probleme... Bei mir hat es geholfen, das Unified Drivers Package - 2018.FFD.2 zu installieren https://support.thrustmaster.com/en/product/mdfcougar-en/ Das hakt sich bei 'Devices and Printers' (bzw im deutschen Äquivalent) ein und man kann dann die MFDs nummerieren, wie es einem passt (bei Game Controllers - Properties) und auch die LEDs einstellen. Vielleicht hilft das.

Here are a few vids which nicely show why the F-16 has a hook: and F-15:

Here you go with a 7.1 channel crash - HTH! Fresh repair, no mods, new SavedGames folder (with your autoexec.cfg) with the only changes being voicechat activation and selecting my headset where possible.

Do you know whether the non-bluetooth version only works with the R3L or also with the R3?

I'm having the same problem with my headphones (Sennheiser 3D G4ME). These headphones can be set to 7.1 channels and then voicechat doesn't give me the "Voice Chat output" and "Voice Chat input" options (only 'default') and DCS crashes when trying to connect to a voicechat enabled server. When setting the headphones to 2 channels I can then choose the "Voice Chat output" and "Voice Chat input" options and it works. This is the only case where I ever had problems with the 7.1 channels - so far, all games, teamspeak, SRS, discord, and even DCS itself (other than voicechat) didn't mind...

Sometimes I have the feeling DCS has a lot of 'solvable-in-5-minutes'-problems but someone has to get around to actually fixing them. I'm just glad that this specific one can be 'user-fixed' and that berk.kp found the file responsible all those months ago...

Yes, that's much better - thank you! :thumbup:

One thing I find distracting with the new in-cockpit sound is that there is a 2-second loop for me, especially noticeable when in full rpm and full boost. It seems to be the file ExIn4.wav which is 8 seconds long but has a little variation roughly every 2 seconds...

If you want to choose the IR pointer press TMS right 2x short.

It's good to see that the Gazelle is getting some love again - I really appreciate it! I'm looking forward to your future updates! :thumbup:

Doch, das klappt glücklicherweise durchaus: https://forums.eagle.ru/showpost.php?p=3763706&postcount=5

Die Funktion des AWACS gibt es in der Tat noch nicht, ist auch bereits bekannt: https://forums.eagle.ru/showthread.php?t=250797 AWACS Declare not available

epoch, do the buttons work for you like that in the air in normal level flight, too? Because for me they don't unfortunately - only on the ground or in flight with gear down and/or in high AOA. AFAICT that is because in those situations the autopilot doesn't actually engage - in level flight it then doesn't go back to center as it has engaged. I had to mod the default.lua for the intended behavior:

Does this help? For example at 09:36.