H-J-P

@Tony Your *.ikarus file is important to you. There are your settings included. For an update, please replace it with your version.

Or ask Jat. I would be glad if you help each other. That's actually the purpose.

@Coolhand, nice cockpit. Actually, that should not be a problem, that both works. This is more a question for McMicha. It just has to be entered correctly in the Export.lua. Unfortunately, no French understand.

I did not think it would be possible to freeze DCS with a UDP Data Packet.

Ray you very helpful to us. It is now important for us to know which button you can use to create this DCS behavior. Please report it.

Ray, you do not have to do more.

I made it today, DCS is frozen ... Interesting ... I'm not here to say what I think ... (****)

@Ray, so you know what makes sense, the following information: The *.Ikarus is only responsible for the layout and the parameters to be sent. The *.xml file contains all the DCS IDs we have defined there. You can then use it in the *.Ikarus file. If you do not want to use something, delete it in the *.Ikarus file or in Ikarus itself. It will not be used anymore. It will not be sent anymore. The data that comes then from DCS, have no effect. They are simply discarded. Thanks for your support.

There are no dumb questions. Only stupid answers. Ikarus does not normally affect your controllers. Unless you are using the wrong DCS - IDs somewhere. You created your own Ikarus profile?

That is interesting. Ray, are you sure? Of course, Ikarus is not working anymore. This is normal with this configuration. Maybe McMicha has an idea what it's all about. He develops the lua - scripts.

Thanks Ray. The button with the pink square is the one that is stuck.

Ray, that has nothing to do with Ikarus or the export - scripts. You are using your F16 frame now. But it's nice to see it happen with it. There is a way to change those behaviors. Unfortunately you have to change the clickabledata.lua of the A-10C. -- Left MFCDI elements["PNT-BTN-MFD-L-01"] = {class = {class_type.BTN}, hint = _("OSB 1"), device = devices.MFCD_LEFT, action = {device_commands.Button_1}, stop_action = {device_commands.Button_1}, arg = {300}, arg_value = {1.0}, arg_lim = {{0.0, 1.0}}, use_release_message = {true} } ..... Change true to false for all MFCD - buttons. Or just press the clamping button a second time.

Everything looks good. :thumbup:

I saw in DCS.log that you use F16 MFCDs. With the next crash also the export.log would be important. Otherwise nothing remarkable was to be seen.

Ray, thanks for the video. How can you press OSDB 19 in the Ikaus cockpit, if you have deleted all? I did not understand that yet.

What does not fit ?

I still look at it in the cockpit. The corrections I have made on the basis of clickabledata.lua. Actually, it should work. Step by Step ...

I can actually fly everything. Of course, I can not work so deeply into any system. Your support is important for that. Thanks to Ray and Yat. :thumbup:

I upload Developer Version 1.4.5.3r A-10C Ray

@Ray - TACAN and ILS external ring knob <-- solved. - CDU FPM if you chose a flitgh plan then their is gargage in the window. (if you do not understand , I could make a little video) <-- Please upload a video. - CDU: page up-down inverted <-- I took that over. Thanks.

Actually, it is messy. I do not like it.

I think for one that no one knows how complex that has become. That does not make it easy. Each team makes it different. So it's not easy to just answer some simple questions. The corresponding clickabledata.lua defines how switches work with which value. That can be significantly different for the same switch.

Ray, step by step ... Tacan and ILS is the next ... That's more important.

I upload Developer Version 1.4.5.3q M-2000C / A-10C

Tomorrow there will be an update again. I have solved the reported bugs until then.