ArturDCS

To my knowledge those are viewports(?) in DCS and thus not possible to have in DCS-BIOS.

Pilot SAI Cage Knob, command for adjusting reference symbol not working(LMB) Pull to cage /(MW) Adjust aircraft reference symbol A DCS-BIOS user reported a problem not being able to adjust the aircraft reference symbol. In DCS-BIOS this control is split up to two different controls, one for pulling the knob, the other for adjusting the reference symbol. "PLT_SAI_CAGE" & "PLT_SAI_PITCH_TRIM" In the AH-64D clickabledata.lua the command is listed as 3002. Changing this to 3004 made the command work again. I also tested this directly again DCS API and 3002 was dead whereas 3004 work. But looking at the -- Standby Attitude Indicator elements["pnt_619"] = default_button_axis(CREW.PLT, _("SAI Cage Knob, (LMB) Pull to cage /(MW) Adjust aircraft reference symbol"), devices.SAI, sai_commands.CageKnobPull, sai_commands.CageKnobRotate, 620, 619) it clearly states the command is 3002. (sai_commands in commands_def.lua) What am I missing? edit: Is the CageKnobRotate and CageKnobRotate_ITER doing the same thing?

Yes, you can communicate with the server's socket. Just follow the same routines as the client program does. It is json being passed on back and forth.

Big thanks!

I have added this API to dcs-insight together with all iCommands. I did some spot testing and couldn't get most commands to do anything. Is LoSetCommand() not supported anymore?

Bump. First off, I know almost nothing about LoSetCommand(). But I have added it together with the iCommands to dcs-insight. I would very much like to get some feedback whether it works as it should in dcs-insight. The idea was to make it easy to test different commands from a GUI.

Any progress on this?

Hi and thanks for answering! Short answer: You will find the behaviour using dcs-insight to execute these API. See signature. There is no need for a particular mission, just a vanilla runway mission. Longer answer: DCS-BIOS has been revamped, core has been completely re-written and with this new dcs-bios version radio controls have been introduced which uses these two APIs. DCSFP will move to use these APIs where possible since it is much simpler than dialing in the new frequency via the radio's dials. It was during DCSFP development I found this out.

Trying to set frequency using device(20):set_frequency(149975000) makes the VHF COMM radio default to 146.000 Mhz. Trying to set any value above 146.000 Mhz causes this. Setting the frequency to 149.975 Mhz in cockpit shows correctly when using device(20):get_frequency() Tested with DCS 2.9 Openbeta and 2.8.7.

Thanks, more functionality has been added. Possible to test an API over ranges.

Simple to use and contains the basics. Polling possible. Most DCS APIs Lua Console dcs-insight

Yes That is a tricky one, different games react differently. But a long press is essentially a long series of quick clicks. You can change the key API used under options. Read the wiki for more info. Link in signature. We handle questions and support via our Discord Server nowadays.

I suggest you head on over to the Discord server for help. And you need to be more specific than "I can't get it to work".

Please create an issue on Github and explain when this happens. Also post your profile.

Wrong post

I suggest you head on over to Discord too and ask F-14B pilots there.

Can you head on over to our Discord server? Easier to exchange info via chat.

OK so if you configure "A" it produces 2 A's? Is it when using VK_NULL? edit: I've been testing here and it does seem to work? What could it be, are anyone else having these problems?Check your profile, post the relevant part of the profile here. Fallen_Tyrael, you can test by opening Notepad and while clicking see how many letters are produced, for example letter A. I don't have a problem here so atm I don't know what is going on.

I did a release with a new key value named VK_NULL. This key doesn't do anything and with it you can do what you described. Of course you can use the OEM or what is was. Report if there are any problems using it. This is the easiest way for me, instead of having texts for single key stroke. That would mean more programming.

Thanks for the information! Had no idea about that aspect. Yes will change it so that the user will be asked whether to use pre-programmed radio or not.

Yes, I will do it. Curious on why though.

What I see is one (1) virtual key stroke. If you there would save and exit the key sequence window DCSFP would treat it as a single virtual keystroke, not a keysequence. Try adding 2 virtual keys to a sequence and save. Does it look the same then too?

If you start adding a key sequence but you end up with just one entry (change of mind), DCSFP will treat it as a simple virtual key stroke and there won't be any need for Break(s).

Right Click on the field only offers to change timing, and not to edit the sequence Break means the time it will wait before executing the virtual key press. Look at the screenshot for this sequence: RadioPanelKeyDialPos{LowerDME}\o/{1LowerCOM1}\o/OSKeyPress{INFORMATION=^Key press sequence^[FiftyMilliSec,VK_A,FiftyMilliSec][FiftyMilliSec,VK_B,FiftyMilliSec][FiftyMilliSec,VK_B,FiftyMilliSec]} This is how it is saved into the file.