Ciribob

I'd join the Hoggit discord and their Georgia at War Server They use SRS a lot, and have many users you can test with. The a10a is FC3 so only has SRS keybinds Bind all you need and make sure to test audio with preview audio https://discord.gg/hoggit Sent from my HD1903 using Tapatalk

That list is for prefixes, as in the start of the name You would put Alpenwolf as the name in the list, and call the aircraft Alpenwolf1 mi8 etc If the start of the player name matches the prefix then it will let you in Sent from my HD1903 using Tapatalk

One last bump @c0ff :) If list_indicators is added, DCS-BIOS (or any cockpit integration) plus SRS can be gone using GameGUI / hooks and migrate away from Export.lua Understood this is not a priority in any way though! Sent from my HD1903 using Tapatalk

Please go to Discord for support with this https://discord.gg/Ajzxqxj Sent from my HD1903 using Tapatalk

It's not unsupported, make sure you have the latest version. I added support two weeks ago. :) If unsure, reinstall with the autoupdater Sent from my HD1903 using Tapatalk

I'm still around but working on SRS, just haven't had time to properly review or test anything, sorry about that It's not abandoned, neither have I abandoned DCS, just a lot for me to support at the minute with SRS :) Sorry! Sent from my HD1903 using Tapatalk

Make sure he's on 1.9.0.3 or 1.9.1.0 - there was a bug in a later release that was pulled Think you've already posted on Discord - replied there The point of the thread is to point people to Discord for support :) Its also still an ad for what SRS is and how it works, as the first page still gives an OK overview. The reason for pointing everyone to discord is I have consolidated a load of troubleshooting and quick start guides there. I can also have a conversation in real time, which is much better for actual troubleshooting and means I or others can solve issues quickly. There are also 1000s of SRS users on that channel so chances are someone will help if its not me. Finally - I dont see it as too onerous a request - Discord can be entirely browser based, so no different from logging into the forum so I can't see why anyone would have an issue with that or choose to not get support for that one small request from me. Can you post on the feature request section on the SRS discord? Sounds like an interesting idea!

Ok sorry one is missing - or I'm misunderstanding how to use it In the Export.lua there is list_indication I use this to to read the UFC in the hornet to work out the state of MIDS and Guard on a radio (same in Harrier and F16). This is also used extensively by DCS-BIOS for Home cockpits in the GameGUI environment I found an undocumented call Export.GetIndicator() Which returns something with the same parameters as list_indication - for example for the Hornet list_indication(6) is the upfront UFC I cant figure out what methods it has in order to read the value of the indicator Any pointers? Edit: the returned object has 3 methods - but none of which seem to return any data. As such list_indication is still needed from the Export.lua environment. Is there any chance this could be added as Export.list_indication in the newer GameGUI environment? This would allow DCS-BIOS, SRS and others to migrate fully to GameGUI (i think)

Turn off the VAICOM TX inhibit in SRS See the VAICOM manual for details Sent from my HD1903 using Tapatalk

Thank you! This made my week :) Sent from my HD1903 using Tapatalk

That I didnt know... Thank you! Calls in Export I currently use are: Loading Terrain using local terrain = require('terrain') and a load of other imports to get terrain to load. Needed for terrain.isVisible call for Line of Sight calculations LoGetSelfData() LoGetPlayerPlaneId() LoGetCameraPosition() LoLoCoordinatesToGeoCoordinates(point) GetDevice with get_argument_value & get_frequency() & get_modulation() list_indication(indicator_id) Are these all available? If so I'll move all that over to the Hook and stop using the export.lua entirely Not sure TacView or any other author knows that they can exclusively use the Hooks environment and ignore the export one Thank you!

Can you give some more details? SRS uses both Hooks GameGUI and Export.lua With export.lua everyone that hooks has to a good citizen - but not all scripts are For example SRS export.lua line is just pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil); To try to catch any loading errors In the file itself the two functions are: -- Prev Export functions from other hooks local _prevExport = {} _prevExport.LuaExportActivityNextEvent = LuaExportActivityNextEvent _prevExport.LuaExportBeforeNextFrame = LuaExportBeforeNextFrame LuaExportActivityNextEvent = function(tCurrent) local tNext = tCurrent + 0.1 local _status, _result = pcall(function() -- SOME CODE end) if not _status then SR.log('ERROR: ' .. _result) end local _status, _result = pcall(function() -- Call original function if it exists / other hooks before me if _prevExport.LuaExportActivityNextEvent then _prevExport.LuaExportActivityNextEvent(tCurrent) end end) if not _status then SR.log('ERROR Calling other LuaExportActivityNextEvent from another script: ' .. _result) end return tNext end LuaExportBeforeNextFrame = function() -- read from socket local _status, _result = pcall(function() --- SOME CODE end) if not _status then SR.log('ERROR LuaExportBeforeNextFrame SRS: ' .. _result) end -- call original _status, _result = pcall(function() -- Call original function if it exists if _prevExport.LuaExportBeforeNextFrame then _prevExport.LuaExportBeforeNextFrame() end end) if not _status then SR.log('ERROR Calling other LuaExportBeforeNextFrame from another script: ' .. _result) end end Saving any existing LuaExportBeforeNextFrame and then calling my version, then passing back up the chain so all the other scripts hanging off work The issue is others dont always properly handle errors on their end - causing all the scripts in the chain to break. Could Export.lua be done in the same way as GameGUI where you have multiple gamegui luas? Is that already in place and if so, how do we name the file?

Please use Discord for SRS for support https://discord.gg/Ajzxqxj Sent from my HD1903 using Tapatalk

One post above, please use Discord for support Sent from my HD1903 using Tapatalk

Please use Discord for SRS for support https://discord.gg/Ajzxqxj

Discord for SRS for support https://discord.gg/Ajzxqxj Sent from my HD1903 using Tapatalk

On the SRS radio overlay there is a question mark - hit that and it will explain what's available on the aircraft you're currently in. That'll save any confusion in future Sent from my HD1903 using Tapatalk

Discord for SRS for support https://discord.gg/Ajzxqxj Sent from my HD1903 using Tapatalk

This is not a bug, in preview all radio effects are applied including the FM tone to give you an idea of how you will sound. Turning off FM tone will stop it in preview, but also remove the realistic effect from FM transmissions Discord for SRS for support https://discord.gg/Ajzxqxj Sent from my HD1903 using Tapatalk

Discord for SRS for support https://discord.gg/Ajzxqxj This is listed under #common-issues Sent from my HD1903 using Tapatalk

This shortcut is listed... In help in SRS on the client In dcs if you click the SRS module In dcs if you go to settings - SRS On the download page of SRS On the support Discord for SRS https://discord.gg/Ajzxqxj I'd suggest any of those places over here to find it! The help section in SRS being the best one over looking in the LUA! Sent from my HD1903 using Tapatalk

go here for support https://discord.gg/Ajzxqxj I think you're both talking about the admin prompt Post your issue there and I'll help Sent from my HD1903 using Tapatalk

See the SRS Discord, that's explained there Sent from my HD1903 using Tapatalk

You'll have beta updates enabled on your client, turn that off in settings The current beta is not backwards compatible Sent from my HD1903 using Tapatalk

For support, discord is your best bet https://discord.gg/Ajzxqxj On the SRS radio overlay, hit the ? Mark, it'll explain how your current SRS settings relate to the specific module. For example always allow SRS hotkeys means that SRS has control over radio, and not the module so the in cockpit selectors for the Huey will no longer function, and you must select a radio using SRS key binds Allow dcs ptt means you can trigger the ptt with a dcs key, this is only supported on some modules and again the panel mentioned above will explain the module you're currently in You can safely disable the dcs ptt and just use SRS ptt Sent from my HD1903 using Tapatalk