Raffson

Interesting, thanks for pointing that out

A temporary solution adding copies of original weapons would be much appreciated. I’ve noticed the AI will fire off ED’s counterpart of the weapon, if it exists obviously. I’m hoping for the Kh-31 A/P at least, as that would allow me to create default payloads for the Su-30 for all different tasks. I need this for integrating the Flanker-H into Liberation, without having to nerf its capabilities. The MKI variant is an example of what I’m trying to explain, i.e. it has 2 versions of the Kh-31P, one custom and one original. I’ve tested both and the original seems to work with AI. So if that could be applied to other variants then SEAD is handled. Another thing I tried with was changing the CLSID of the Kh-35 to the original one, though I did that in my payload file so the pylon didn’t show up but aside from that it also worked. Of course the ideal solution would be the AI firing off the custom AG weapons as well, that would allow me to customize the payload accordingly, e.g. let the MKI variant use the Rudra-M1 instead for SEAD. But until then it would be of great help if I’d have access to original KH-31s, both A & P models. I can do this myself, but that’s not a valid solution for integrating the Su-30 in Liberation

I've been trying to get AI to do some SEAD and anti-ship strikes, however I'm having trouble with custom AG weapons. The AI doesn't seem to be able to use them, which I find really weird because custom AA weapons work fine. Any change I missed something?

Deadzones might help with that. Also, I’m trying to imagine in which situations you need this and what means you have at your disposal, i.e. what stick are you using etc. I’ve tried it out myself and find this to be more accurate than making corrections with the stick when it comes to finetuning. Even though I keep the default bindings on the keyboard cause in the situations that I’ve used this I’m already in a “controlled attitude” which allows me to take my hands of the stick for these tiny corrections.

Try out what’s already available, just map buttons for cyclic up, left, right and down. Depending on how sensitive you want the buttons to be, this could be your solution.

In that case you might as well fly exclusively with a human CP/G… imo, if you’re flying with george, you’re already messing up the realism part anyway.

+1 on a more detailed target list. Also, when there’s a lot of targets, the list can get pretty long, a “parent sub-menu” with categories would be handy, definitely speeding up the process of picking out specific targets.

+1

Now that sounds familiar Either way, the thought alone of having a DC keeps me excited

Right, is there an english version of that page cause unfortunately I don't speak, read or write russian :s EDIT: nvm, google translated it for me xD

I know i'm a little late, but has the C++ developer for avionics position been filled already? If not, I'm more than interested! Contact me in PM for more background info about myself.

That’s cause a new version of SRS hasn’t been released yet.. if you want, you can always download the file needed separately and replace it.. https://github.com/Raffson/DCS-SimpleRadioStandalone/blob/master/Scripts/DCS-SimpleRadioStandalone.lua I believe my version of DCS-SimpleRadioStandalone.lua is currently the most complete one, though i’m still missing dcs’ in-game ptt controls, but eventually it will be included.. Hope this helps meanwhile :) EDIT: Your may want to grab a copy from LazyBoot instead cause possibly my version has too much code in it. Just received work that the backup controls should work automatically, though I'm not sure if all the controls from the backup panel will work so I need to do some testing later today..

So I've forked the project to make some adjustments, mainly some code that will automatically detect the external ip for people who wish to host a temporary srs server of their own to fly with some friends.. Now I decided to take it a step further and incorporate the F16 (since it got released yesterday) so that it doesn't get recognized as a FC3 plane.. So first off, how do I allow dcs' cockpit controls for ptt cause currently only srs controls are recognized. Second, I'd like to confirm that both the AN/ARC-222 (VHF) and AN/ARC-164 (UHF) are using the KY58 for encryption cause I noticed in the code that the F18's VHF radio is not encrypted so I'm not sure what's correct here.. At last, I'm also wondering how I could read the frequency from the backup UHF, given that the C&I switch is set to backup instead of UFC.. The problem I'm dealing with is the fact that i don't see a separate device for the backup radio, so I'm not sure how to proceed on this one.. I've already figured out that it's possible to check whether the C&I switch is set to backup, but that's only half of the solution.. Any help would be much appreciated! EDIT: After looking at "clickabledata.lua" of the F16, I conclude that stuff is still missing in order to get the in-game controls to work with srs.. For the backup UHF I'm trying to get the frequency from "UHF_CONTROL_PANEL" since I'm assuming this must be the backup UHF cause there's no such panel for VHF, though I'm afraid this device does not have a "get_frequency()" method because it's not working.. Any thoughts on how to work around this? EDIT2: turns out ciribob already fixed the F16, except for the things i'm having trouble with... EDIT3: ok so seems like a misunderstood the backup radio.. turns out it's not a separate radio but rather backup controls for the UHF in case the UFC is down.. thus that last question no longer requires an answer :D EDIT4: Backup UHF controls are done, will ask for a pull-request once i figure out how to adjust the installer to copy-paste http.lua & url.lua (located in LuaSocket) into a folder called "socket", otherwise it won't the http module needed for retrieving your external ip.. ciribob, if you can I did this correct, that would be awesome ^^

Yeah well, I guess I just had to :p So I think I understand the issue though I can't help you out here since these "functions" are "hard-wired" into the code. The next best thing is probably to make a switch for the AGC/MGC button but since it's a toggle with 3 states it might not be ideal to have a switch. As for the Laser/Focus button, the Laser part is a toggle with 2 states so a switch could work, though I'm not sure about the Focus part...

Currently 2 options are available for PTT axis controls: -ICS Button ICS (Intercom) PTT (axis threshold) -ICS Button MIC (UHF) PTT (axis threshold) If you haven't tried those out I suggest you start there, if that doesn't suit your needs I can try some tricks but no guarantees it'll actually work...