Renko

BTW I just realised one thing that could make the solution more easy for you guys, but im not 100% sure. I cannot try because i dont have display export in DCS. Seeing the AMPCD from the thread i quoted it seems that the solution could be achieved with only working in the Luma channel. Because the map colours seems to be okay. So if you dont need to transform the colours and only need the luma, that makes things way easier. If thats the case you could achieve a solution by just adjusting with a custom curve or with gamma values. Here is an example with one of the OP screenshots and a quick custom curve i just did in some external software. I tried the same in Photoshop with a similar curve. And both make those two almost identical, the priamry display and the external one.

I would like to offer some advice on this matter, as I have some knowledge in this area. Maybe this will help the team get on track to resolve this issue. First of all i will make one assumption on those colour spaces, because those may deviate from the Rec.709 & Rec.2020 specs. We have some sort of HDR Color Space in the game primary display, lets call it HDR. And the export display is some sort of SDR Color Space, lets call that SDR. So if thats the case you will only need to transform from one Color Space to the other. In this case you will need to transform that SDR to HDR, in the values that DCS uses. This is nothing special. In the industry converting from one Color Space to another is a pretty common thing to use on daily basics. So the only thing ED will need to provide is a Trasnformation Matrix for that SDR to HDR color space. Probably should be pretty straight forward to do a custom LUT (Look-Up Table). Or use an existing one if it complies with Rec.709 and Rec.2020 specifications. And you could provide one. Where? Well just like you have that drop-down menu called "Color Grading" that are just LUTs ( a LUT is a Trasnformation Matrix). There you can have one at least that transforms from SDR to HDR values but it will only affect the export display you choose. So you will solve this issue with that. This user here has done a Colour Space Transform without knowing by using Reshade. And you can see that works well enough, and its is just that. Transform SDR values to a similar HDR ones from the primary display. So if DCS supports having some LUTs for "Color Grading". It should be able to give in the same manner a LUT that transforms SDR to HDR values and only affect export display. If the team wants to find more info on how this technical Colour Space Transforms works they can google "Color Space Transform HDR to SDR". They should be able to find good info. As I mentioned earlier, if DCS already supports LUT, this feature could be applied just to exports from a technical standpoint. Hope it helps

Now we have at least one entire single player campaign that needs you to have those lines in order to play. I wonder if a user who adds this will remember to remove after playing Still unclear to me, sorry i'm a bit clueless with all this, but if i leave that autoexec.cfg after playing a trustworthy mission/campaign it could be an issue for me as user. That I wouldn't have before this update? Sort of like leaving the door open

Can confirm this behaviour Easy to test for them. Just launch Instant Action Caucasus Refueling F16 Mission. Accelerate time and you will see the AI doing that refueling loop. The two-ship AI that are refueling when you arrive are doing what the OP has described. I had to gun down the F16 to practice refueling

As the title says, add an option on the Special tab of a module that will give the user the option to set a custom dtc file to be the new default for that module. You would have to include checkboxes where you can select which parts/sections of that file will be loaded for that new default. Otherwise, if all the data in the file is loaded, it will create conflicts with missions, campaigns and MP server missions. For example if i want only the countermeasures but it will load the default comms too, i will lost all those presets for comms. Or nav data I think this will be great to have and will serve the purpose most users will be using the DTC for. For example, if you are only going to use the DTC for stablising a new custom default CounterMeasuresSystem programs, and want that every time you sit in that module that data will be always the new default you set in the Special Tab.

Just saw a user posting this video on ED's discord, with some custom scripts and voice overs. I'm going to leave this here as a reference for the devs Because I think this kind of communications would be great to have for this CrewChief system. Better than the current ones for SlingLoad, as these are more accurate and frequent.

Thanks, but thats just a work around. As i said in my first post this behaviour is not how it should be. And i checked that with an active pilot of a Hook

This with the current patch (DCS 2.9.17.11733) it still have issues null

Yeah, good idea. It could work as a workaround for a two-way-switch in the Hotas

Thanks Bignewy I saw all those keybinds, in fact in my track i use too "move fwd" and "move backward as i sad in the first post. And its great to have all those options for sure. But for people with limited keys, you will still lose that OFF position logic. The only issue i see with this Switch is that you "jump" the OFF position without triggering the logic. I think with that image and my track is clear to see. If i pressed RESET and then ARM, and it triggers the OFF logic when passing through all will be fine. I know is a minor thing, but i noticed this issue while trying to map that switch into the Hotas. Regards!

@BIGNEWY sorry for the ping. but without a reply i dont know who tag this thread as "not a bug" Sorry but it is clearly a bug. I did not say that the logic of each position of the three-position-switch is wrong. That works fine. Im saying that i can pass from ARM to RESET position, without passing through OFF. Which is physically impossible looking at any three-position-switch, because you need to pass first through OFF to be able to reach RESET. And i think you can agree with me on that. And since it jumps the OFF position, it doesnt trigger any of the logic the OFF position does. nullnull

I noticed that in the Hoist/Cargo Hook Control Panel if i move the CARGO HOOK MSTR Switch from ARM position to RESET position susing keybinds for those two, it will not trigger the OFF position. Meaning that on a three position switch it will "jump" the central position if you use keybinds. If you dont trigger the OFF positionnull it will not do anything related to that switch, and it makes no sense physicaly. Here is a track that shows a copuple of times the behaviour using keybinds. First with only ARM to RESET. Where you can observe how the OFF position is "jumped" and it wont trigger nothing in the Hook systems. And then using the keybinds for moving up and down the switch for comparison. Regards Hook_Issue.trk

Thanks! So this its a 5min fix, they should take a quick look Syria - Mi-8 - Sling Load.miz

The speed showed in the DCS UI for all modules is incorrectly named as TS(TrueAirspeed), when is clearly GS (Ground Speed). You can see in the screenshot with an FA18 how the speed showed as GS in the HSI matches the one in the UI named as TS. But if that TS from the UI was in reality TrueAirspeed it should match the TAS from the HSI. nullThe name should be changed to GS. Which is the speed you enter in the Editor. And i guess in the Editor the speed is in GS.

I've experience this. Dont worry is easy fix. But its a bit weird setup they did. They added for the CH47 a separate section called "CH-47F Gunner Station", which is active when you are out of stations 1-2-3. So you have to map there those HOTAS keybinds. The weird part for me is that other HOTAS keybinds that are on the "CH-47F" section works, and others dont. You can for example fly it, press Trim, etc. But the binds for crew stations dont work, or at least most of the time. Which is weird. I think they should review all that to create something like the Gazelle or the Kiowa has for keybinds relations between Pilot/Co-Pilot stations. That will work so much better and wouldnt confuse users.