Ciribob

Post a screenshot of your C:\Users\USERNAME\Saved Games\DCS\scripts folder Post your Export.lua here Post a screenshot of the SRS Client window once you've connected to the server, you should see that there are other clients connected, shown at the bottom of the window. Double check that the IP you're connecting to is 5.189.162.17:5014 the port 5014 is important as there are two other SRS servers running on that machine, if you connect to them you wont hear anyone :) Always put it to the bottom now. It only went above when TacView was having issues with a DCS update which was fixed quickly :) Always best to remove all the lines from your Export.lua and just leave local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[scripts\DCS-SimpleRadioStandalone.lua]]); To make sure there are no conflicts, then add them back. Full troubleshooting guide linked in my signature Hope this helps and thanks to all for helping to sort it :)

No worries, language and tone on the internet are tricky! :) Thanks for the nice reply and hopefully I can solve this for you with some of the work I have planned :thumbup:

:D Deal :P Although i need to do a lot more work to it. Should be able to start work again on it soon. :thumbup: Thanks for being a great community and helping each other out with it, as I agree that is a shame that there is no built in comms, especially when the radios are modelled so well in game, hence this project. It is by no means perfect, but I do have exciting plans to more heavily integrate it into DCS, but first I need to sort out RL issues :)

The old overlay extra exe is no longer needed. Press show overlay on the main window and it should appear. The original video is a bit out of date :) If it doesnt there is a reset button in the settings panel for the overlay position (at the bottom?), press that and then try toggling the overlay again with button on the interface. I cant post screenshots as I've only got a mac at the moment so i can't run the radio and this is from memory :) Make sure you've got the right output device selected. If you can see Blue bars for input and output after pressing preview, turn preview off and try a different output device. It should work fine when you pick the right one :) I really do appreciate the help that you guys post each other here as that what makes a good community so a big thank you to those that help out and help others in other places :)

If everyone thinks like that, no one will use it... If you want to use it, use it, lead by example and convince others :) Sent from my ONEPLUS A3003 using Tapatalk

Sure, thats an easy one :) Just insert the newly spawned unit name into the ctld.transportPilotNames list table.insert(ctld.transportPilotNames,_someNewSpawnedGroup:getUnit(1):getName()) Doesnt care if they're inserted while its running for AI units or if the unit is even alive or exists.

Does the sample mission not work or just the one you are building based off the tutorial? I didnt want to enforce how it picked the order (instead using the hpriority etc) as my worry was there are actually a lot more factors than type, as distance is important too. If anyone wants to have a go and add it (with an option to turn on or off) feel free :) To both: Sorry can't help that much at the minute, no access to DCS. :(

I've thought about it but for some the boost needs to be the other way, above 0 so i think that'll confuse people even more. What I want to do is add a check to make sure you've done preview audio at least once before connecting to try to help with it a bit. So please, to all, always preview audio and adjust boost for the good of your fellow pilots ears :) Please follow the troubleshooting guide linked in my signature. Double check that your're running the radio as Admin and you've allowed SRS through any firewalls Daniel, does it work for every aircraft except Mig29? For both - Check the logs directory in Save Games/DCS and check inside the 3 simple radio log files for errors. All it does is expand the devices that it polls to enable things like the MFDs. The issue is this can cause problems, only for SRS, in detecting button inputs on other devices you're already using. No harm in trying though but remember to restart SRS once you enable or disable the option. Will not effect anything else on your system. :) Update Looking like I may have a home again and access to PC by Mid March now so hopefully development (and some DCS flying) will continue then.

Thanks a perfect spot, no worries :) Putting them there would work fine! Its not possible to respawn a pilot for rescue, but you could spawn a new AI aircraft (continuous trigger, coalition not in zone) and then use the explode trigger to cause the pilot to eject :) Sorry no AI CSAR possible. You can only pick up AI ejections Sorry for the slow replies!

I'd post your missing here if you havent already solved it and someone will help :) Sorry for the slow reply!

Just a gentle reminder, please don't post questions and requests, just examples as I'm trying to keep this thread just examples so they're easy to find. If you want help, open a new thread or post in the main CTLD one (https://forums.eagle.ru/showthread.php?t=143107). It says on the first post and on the previous page :) Post a sample mission there with the issue and someone will help :)

The radio pulls the frequencies straight out of the aircraft radio so if its not coming through than actually the ingame radio isnt set to that frequency. To be sure (and check its not a bug) You could try a quick test by setting up a radio transmission on a frequency in the DCS mission editor and then try tuning to that frequency first manually, and then with the channel configured and see if you can actually here it. Glad you liked it. Sorry i've not managed to work on it.

Please post on the GitHub any recordings you have of this. Any recordings would be very helpful in diagnosing and fixing. Obviously this is a bug and not programmed behaviour.... :) I've not been able to replicate and therefore unable to fix. Also currently homeless, have been for a while now, with no access to my main PC so obviously progress has been slow.... Blue Flag always tries to strike a good balance between realism and fun, and thats why I made SRS, to increase both the realism AND fun but there does seem to be a split in the community between those that enjoy messing with cockpit radios, and those that don't. There is nothing wrong with that! Horses for courses and all that... :) Ideally, once this bug is fixed then SRS would likely be made mandatory but again, i'm homeless, everything is subject to change, but it would be great to try for a round to see how it goes. I have also succeeded in bringing the overlay in to DCS (non interactive other than show hide but shows frequencies, tx & rx) so you can't really get more integrated then that :)

Yes, you just have to start one server, then edit the config file to change the port it listens on, then restart it again. Do the same for any other servers you want :) BuddySpike (BlueFlag) is running 3 SRS servers on one physical server on 3 different ports. Just run the installer, it'll automatically install into openbeta, openalpha and release versions. If its not working, follow the troubleshooting guide in my signature. The Viggen doesnt have the specific radio code in but it should still work like a default FC3 aircraft once its installed correctly :) Hopefully should have access to my PC in a month or so so I can start work on this again :)

Double check which comm button you're using, try a different radio button if the current one isn't working like intercom. Check keybinds and try all of them, one should work :) Nope sorry, no option for that. Try increasing the weight of the crates, change the weight numbers here: https://github.com/ciribob/DCS-CTLD/blob/master/CTLD.lua#L424 Make sure that they all have different weights or the system wont know whats in the crate :) Once you respawn, or deactivate and reactivate a until you'll need to reinitialise the JTAC unit with CTLD with the ctld.JTACAutoLase command No, anything that works with the simulated system will also work with the real sling loading. :) Checkout the example missions, one shows simulated, the other real (https://github.com/ciribob/DCS-CTLD/blob/master/test-mission%20-%20real%20slingload.miz) to see it working Sorry for the slow replies, due to IRL issues I don't have access to a PC or DCS and won't for at least another month or so.

Turn off easy comms in DCS settings. It stops you being able to change channels in the mirage. Also double check that the radio is set to M Still no access to PC, so no progress yet. Sorry all.

Can you please post a very simple sample mission showing it not working? I'll try to take a look.

Change this line - https://github.com/ciribob/DCS-SimpleRadioStandalone/blob/master/Scripts/DCS-SimpleRadioStandalone.lua#L741 In the Scripts folder in the DCS-SimpleRadioStandalone.lua to have a 0 instead of a 1 _data.control = 0; This means the HOTAS controls will work instead of having to use the incockpit radio selector. You can do this for any radio :)

Problem is reported internally and ED are working on it so don't despair :)

Thanks! :) Unfortunately I dont get the full name of the device so I guess whats being returned for those two entries by the API is identical, hence why it appears not to save your preference. You could try disabling the device you don't use but obviously thats not ideal. I'll try to take a look. Update on Project in General As you might've noticed, work on this has slowed quite considerably. Fear not, it is not abandoned but due to some fairly drastic changes in my circumstances, time to work on this is currently non existent. The most pressing issue for me at the moment is sorting out where I will live! Once i've managed to resolve some life issues, I will continue on the project. Likely with a fairly drastic rewrite and switch to C++ for all audio and UDP packet handling. Sorry for the not such great news and Merry Christmas!

Sorry guys, I'm away with no access to PC so can't test. I've posted here and if someone could do the tests I've listed at the link below that would be a huge help for when I'm back either late Sunday or Monday evening. https://forums.eagle.ru/showpost.php?p=2987144&postcount=5 Sent from my SM-G900F using Tapatalk

Sorry I'm away so can't investigate. :( If it works partially in a mission, could you try creating a fresh mission , adding four groups containing one client each and then try using addCommandForGroup? Two aircraft and two choppers It may be something like the mission format is subtlety different so the wrong group is having the radio menu added to it. Try it without mist as well to rule out that. The other thing to look as is add radio items using the mission editor and see what the lua generated by the mission looks like. Apologies I can't be more help Sent from my SM-G900F using Tapatalk

Ah ok, thanks! Thats very helpful. That sounds like the initial ping isn't opening the firewall anymore hence why you have to tap PTT for comms to work. I'll have a look and see if I can replicate

On a branch here :) https://github.com/ciribob/DCS-SimpleRadioStandalone/tree/inGameOverlay Quick demo video of the overlay in DCS next to the other overlay to show update speed and verify info Thats odd, I've tested that before locally with a transmission on and picked it up when switching away from the channel and back again. I'll take a look! Please update your .NET to the latest one linked on the download page, should solve it :) Yes still planned and being looked at :) Probably not any time soon but i'll try and have a go next week. As i've said before, i've not had time to work on this for a while, sorry all.

New version of the CTLD Script v.1.64 Make sure you have the new MIST 4.3.74 ! Change log: Mission Editor crates weren't counted by crate in zone function - Bug Fixed! :) Added new crate types (Wont work on Nevada until new crates are added!) - Thanks mvee! Radio Beacon list item is shown even if radio beacons are disabled if beacons are spawned in the mission (Thanks emilianomolina !) Bug fix for crates and/or groups disappearing when another spawns Updated MIST Updated all sample missions The real sling loads are now fully working in DCS 1.5 (and 2.0 when new crates are added), its really worth a go as its a lot better than my simulated system. Be aware, the rope can now snap if you fly too fast! :) Please see Readme and Github for latest code and how to use Link:https://github.com/ciribob/DCS-CTLD Examples:http://forums.eagle.ru/showthread.php?p=2621619 As always, please let me know if you have any issues or suggestions! *** FOR 1.5 or 2.0: Make sure all human players are in separate groups / flights ***