unknown

What Mustang25 said is your "problem". I opened the VFR landing training mission you mentioned in the ME and the temperature is set to minus 10°C, with your engine off = heating for the cockpit off = your pilot is getting a little cold in his plane. Overheating is also modeled in the Jeff, so sitting in the cockpit at high ambient temperatures without your AC running is also a bad idea.

You have to open the button cover before you can use the button. Your key binding will also only work if you open that cover before trying to use it - make it part of your start-up? This is also true for other modules to be able to use buttons with covers(WW2, Gazelle, Viggen...).

Did you lift the cover of the cut drag chute button before trying to cut it? It worked for me last weekend in the latest OB but i used the in cockpit button and not a keybinding.

Interesting, never thought of that myself because of a dual stage trigger. With that you will always unsafe before weapon release. But without it i agree, a toggle function would be great like the master arm toggle in other modules.

Their 3d Artist(the only one?) was in hospital for a long(don't know exactly) time this year. Two months ago Deka answered a question of mine stating that their 3d artist is back in hospital....... I don't know if he still is in hospital but i think this caused a major delay in finishing the artwork. I still wish him all the best.

What are you talking about? I don't understand you: Your questions were clearly answered You: 1. Does the damage model extend to Korean planes? Sabre, Mig 15? Answer: 1. Only WW2 planes have the new DM yet. He never said yes So obvious no, only WW2 planes atm. You: 2. Is it planned to extend to modern? Answer: 2. Yes, but no ETA yet So Sabre, Mig15 and anything else will get it in the next xx years. EDIT: I'm just confused by your confusion about the answers

I already tried different settings for the decoders but none worked. The strange thing is, like said in the first posting, that the binding for: - Mode select - turn clockwise - Mode select - turn counterclockwise works on all of my 3 encoders of my throttle. If i try to assign Weapon selector turn clockwise/Weapon selector turn counterclockwise or Radar MKR Gain increase/Radar MKR Gain decrease to any of my 3 encoders none is working. I use all 3 encoders in other modules(F/A-18 for example) and never had trouble there with them and i remember that it worked at some point in the past for the Viggen too. My novice "solution" to this problem would be just to copy/paste the implementation of the Mode select cw/ccw function to the other two.

It is part of the "new" ED copyright protection introduced a couple monthes ago as far as i know. If you search for anti virus or false positive you will find a lot of comments from users with different AV software getting false positives for many different .dll(from modules and core files).

Bump Any update/news on this? @SGT Coyle I was not often at the forums the last 2 months, missed your post. Before the Forum software update i had all my system/controllers in my sig, but it seems that isn't working anymore(EDIT: i found the setting to see them again). I use the a Virpil Stick/throttle hotas and the decoders work for every key binding in every other module.

For the RB-15, you use your radar. It is designed to find ship targets in the first place. You fly to your initial waypoint where the ships should be(if you have none just search on your own), after finding the ship/ships on your radar you just adjust the necessary Bx points on the radar screen to your liking for planing the attack and go for it. There is also a "quick fire and forget" mode for the RB-15 without the need to adjust Bx points, like you said you "aim" with the plane in the general direction. The missile seeker covers +/- 35° (70° total cone) in front of the missile and it will go for the very first ship it detects, enemy, allied, neutral it doesn't matter. Check the manual pages 329 to 341 for the RB-15. If you have further questions feel free to ask.

Which module? Works for me in the MI-8 Edit: Morpheus was faster :)

Yes, that would make total sense if i would use any other mod but i don't. :cry:

:thumbup: Line of sight is modeled for all radio equipment in DCS, if the transmitter is behind a hill and you're not high enough....nothing. :beer:

Bump Any chance ED will fix this? It is getting tiring to to aply the user made fix every time DCS updates....

ED Shop sale and Steam sale rarely fall on the same days. The video description of the ED autumn sale trailer on YT says: "Dear DCS Pilots! We are pleased to announce that our 2020 Autumn DCS World Sale will begin at 15:00GMT on 20 November 2020 and last until 15:00GMT on the 7 December 2020! Get up to 50% off on most DCS World modules! We will also be participating in the Steam Autumn Sale at the same discount rates." So, google the date of the next steam autumn sale and you know what you want to know :beer:

Works fine for me in SP(OB). (should be 1440p after YT processing) ARK-UD-Test.miz

From what i read it said the MI-24 suffers from vibration while hovering because of the big wings interfering with the downwash of the rotor, later versions with the smaler wings (MI-35M) doesn't have that problem anymore.

Can you describe your setup a little more? (headphone/USB?...) I fly in VR and have headphones connected to my Rift S and hear all DCS sounds(sound/warnings/RWR...) fine. :dunno:

Why? That is not the point of this poll! For the OP there is no difference of latest OB or stable because both are on the DCS 2.5.6 branch and use the same lighting system. All he wanted to know is if people use these versions(stable/beta no difference in that matter) or an older version because of the lighting changes introduced with 2.5.5/6(?). The question of this poll is not how many people use OB/stable....

WIP = Work In Progress The feature is implemented partly and odd behaviour like we see is possible/likely. So we just have to wait until Deka has finished this. Atleast that is my interpretation. :beer:

+1 This is also the case in the "old" A-10C. It feels really odd sitting that close to the front panel and having half a meter space to the chair rest...

After todays OB update it looks like Deka has changed something in the stick shaking behaviour. With todays OB update the shaking lasts only for ~15 seconds. So, is this behaviour wanted by Deka or an unintentionally interaction between pilot freezing effect and the de-fog function? Track, latest OB, caucasus, default DCS weather. @VC If you change the YT link from: [url]https://www.youtube.com/watch?v=orBTXLNG-iA[/url] to: ["YOUTUBE"]orBTXLNG-iA["/YOUTUBE"] without the " marks you can embed the video directly. shaking_stick_after_defog_on_caucasus_update.trk

Go ahead, prbably the fastest way to get an answer from Deka. If you want to include the video also, just click on quote of my post with the video and copy the [Youtube....row, should work.

Ah stupid ME, i did the test on the Syria map. So if you don't own that map you can't replay that track. :doh: I will do another on caucasus. No, it doesn't stop shaking. After i turn the temperature knob to 35 degrees the track replays for another ~40 seconds and in that time the shaking still exists. Considering the shaking starts instantly after pressing the de-fog switch i don't think this is a "pilot is freezing" situation or the ECS just sucks to get the cockpit back to "normal". :P EDIT: Track showing the shaking, this time on the caucasus map(default DCS weather). shaking_stick_after_defog_on_caucasus.trk

Yes, i cycled ECS and put the temperature to 35 degrees. Also note that the track playes a little longer than the video, so it was set to 35 degrees for a longer time periode than the video shows(not for minutes, but still longer ;) )