DCS-SimpleRadio Standalone

I think I may have found a bug, when I run SR either host or join, and mods or vanilla, I have found that when I push L-CTRL + L-Win + L the game suddenly starts lagging until I exit SR, then the game is fine, but when I relaunch SR the lag returns until I exit DCS and restart it. The game runs fine otherwise and SR runs fine as long as I don't hit those keys.

Had a similar issue while hosting this morning even tho I didnt press those controls.

Heavy lagg until I exit SR.

Lagg restarting when I relaunched SR so I had to close the game.

Anyway, thanks Ciribob. Loving your work. :thumbup:

So I did a bit more experimenting and this does occur in other aircraft when using the L-CTRL+L-SHIFT+L combination regardless of bindings. However, the L-CTRL+L-SHIFT+L combination does seem to reverse the effect, so that's a plus and not a game breaker. It's only when SR is running either as host or client. I have a feeling it is something SR is interacting with some other software that is running, that doesn't like that keybinding. But all that under-the-hood stuff is dark magic to me, so you are on your own.

Now that makes sense as I was turning lights ON on the F-15C.

1.2.9.7 w/ hotfix at https://forums.eagle.ru/showpost.php?p=3100412&postcount=1417, I still have to toggle the Radio Effects option to ON every time I start SRS.

Same here, setting is saved but not loaded.

Same here, setting is saved but not loaded.

1.2.9.7 w/ hotfix at https://forums.eagle.ru/showpost.php?p=3100412&postcount=1417, I still have to toggle the Radio Effects option to ON every time I start SRS.

Yeah sorry that has to be fixed with a new release. Might get round to it on Sunday evening :)

Sent from my ONEPLUS A3003 using Tapatalk

<EDITED>

Hey Guys & Ciribob,

I have a problem with DCS that is caused by Simple Radio.

When I installed the server part of SRS a problem occurred where I couldn't click things within the top left part of my screen in DCS. I couldn't click part of the MissionEditor or the Multiplayer server filter options.

Here is a link to the thread where this was figured out to be the problem:

https://forums.eagle.ru/showthread.php?p=3106456#post3106456

I have to admit, I didn't bother to read all 144 pages of this thread so I'm sorry if this is solved somewhere else in here.

<EDIT> ***Just looked and yes this was reported recently. I'll leave this here just in case***

<EDIT> Solution: Hotfix: https://forums.eagle.ru/showpost.php?p=3100412&postcount=1417

Thanks

sBryansGames

<EDITED>

Hey Guys & Ciribob,

I have a problem with DCS that is caused by Simple Radio.

 

When I installed the server part of SRS a problem occurred where I couldn't click things within the top left part of my screen in DCS. I couldn't click part of the MissionEditor or the Multiplayer server filter options.

 

Here is a link to the thread where this was figured out to be the problem:

https://forums.eagle.ru/showthread.php?p=3106456#post3106456

 

I have to admit, I didn't bother to read all 144 pages of this thread so I'm sorry if this is solved somewhere else in here.

<EDIT> ***Just looked and yes this was reported recently. I'll leave this here just in case***

 

<EDIT> Solution: Hotfix: https://forums.eagle.ru/showpost.php?p=3100412&postcount=1417

 

Thanks

sBryansGames

Fixed on the release as well :)

https://github.com/ciribob/DCS-SimpleRadioStandalone/releases/latest

If you ever need support, you can get me here too:

https://discord.gg/baw7g3t

Hi Ciribob,

do you think the issue with the "different radios/frequencies distorting each other if transmitted simultaneously" can be fixed sometimes? (It means two incoming transmission NOT on the same frequency garbling each other out, unlike in real life).

THX

Hi Ciribob,

 

do you think the issue with the "different radios/frequencies distorting each other if transmitted simultaneously" can be fixed sometimes? (It means two incoming transmission NOT on the same frequency garbling each other out, unlike in real life).

 

THX

If you're still having it, please send me a recording.

It should be much much better in the latest version. :)

Sent from my ONEPLUS A3003 using Tapatalk

This is a test we did on 1.2.9.7;

Cheers

Hans

This is a test we did on 1.2.9.7

 

Cheers

Hans

Thanks! Yours definitely sounds worse than some of the others which is interesting

I'll make some tweaks in the next release and see how it goes :)

Sent from my ONEPLUS A3003 using Tapatalk

Hello Ciribob,

I wanted to thank you for SRS and share my pleasantly strange experience with it. I have a very unique cockpit setup. It is multi monitor, external gauges with Ikarus, and I have vibrations working through exports.

I decided to add SRS to my setup. First thing I notice is my Ikarus gauges became choppier in performance. More similar to a Helios gauge in performance. I was put-off at first by this and then did testing to see if I could stop it. As I did my testing, I noticed that my DCS performance was smoother than I had ever seen it. I attributed this to O/C'ing my graphics card, but I then noted the poorer performance would return (please note "poorer" is still very good!).

I could not believe my eyes when I finally figured out what was going on, but I just sat down and verified it...

DCS without SRS (AO 1.5 server, L-39 cold A/C), 37-54 fps.

DCS with SRS running overlay on my Ikraus gauge panel, same server, minutes after first test. 71 fps.

I can repeat it every time and it is just amazing. I am running a life-size multi monitor setup with better performance than many get with one monitor. AO server, at maximum player numbers, smooth. I actually saw triple digit fps.

The slightly choppier gauges are worth it and I'll never fly without SRS again.

DONT... CHANGE... ANYTHING! :)

Are you now in fact bragging, or complaining? :lol: :thumbup:

I have a problem...

I can only use it in 1.5, and not in 2.0.

Any suggestion?

I have a problem...

 

I can only use it in 1.5, and not in 2.0.

 

Any suggestion?

Any additional tools using export (TacView, Helios, etc.)?

Did you verify the export script has the necessary lines attached and not commented (-- in front)?

The SRS lua files are in the scripts folder?

In the zip archive is a read me how the manual install works, there you can see what files/folders to check.

Getting that error again:

21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.UI.MainWindow Started DCS-SimpleRadio Client 1.2.9.7
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Starting Device Search. Expand Search: False
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 6f1d2b60-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b60-d5a0-11cf-bfc7-444553540000 Mouse Usage: Undefined Type: Mouse
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 6f1d2b60-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b60-d5a0-11cf-bfc7-444553540000 Mouse
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 6f1d2b61-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b61-d5a0-11cf-bfc7-444553540000 Keyboard Usage: Undefined Type: Keyboard
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 6f1d2b61-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b61-d5a0-11cf-bfc7-444553540000 Keyboard
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 13841038-0000-0000-0000-504944564944 Instance: 63fdca10-8723-11e5-8004-444553540000 SteelSeries Rival Usage: Consumer Type: Device
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 13841038-0000-0000-0000-504944564944 Instance: 63fdf120-8723-11e5-8005-444553540000 Rival Gaming Mouse Usage: -64 Type: Device
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 80362341-0000-0000-0000-504944564944 Instance: e608b640-8ac1-11e5-8001-444553540000 EDTracker EDTracker2 Usage: Generic Type: Joystick
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 80362341-0000-0000-0000-504944564944 Instance: e608b640-8ac1-11e5-8001-444553540000 EDTracker EDTracker2
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 0267004c-0000-0000-0000-504944564944 Instance: 63fda300-8723-11e5-8002-444553540000 Apple Keyboard Usage: VendorDefinedBegin Type: Device
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 0267004c-0000-0000-0000-504944564944 Instance: 63fda300-8723-11e5-8003-444553540000 Apple Keyboard Usage: Consumer Type: Device
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 13841038-0000-0000-0000-504944564944 Instance: 63fe1830-8723-11e5-8006-444553540000 Rival Gaming Mouse Usage: Consumer Type: Device
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found ffff044f-0000-0000-0000-504944564944 Instance: 5fe63160-8ac5-11e5-8006-444553540000 Thrustmaster Combined Usage: Generic Type: FirstPerson
21:14:23 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding ffff044f-0000-0000-0000-504944564944 Instance: 5fe63160-8ac5-11e5-8006-444553540000 Thrustmaster Combined
21:14:24 Ciribob.DCS.SimpleRadio.Standalone.Common.UpdaterChecker+<CheckForUpdate>d__2 Running Latest Version: 1.2.9.7
21:14:26 Ciribob.DCS.SimpleRadio.Standalone.Client.Audio.AudioPreview Error starting audio Output - Quitting! Retrieving the COM class factory for component with CLSID {F447B69E-1884-4A7E-8055-346F74D6EDB3} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

Tried to install these: https://support.microsoft.com/en-us/help/3145500/media-feature-pack-list-for-windows-n-editions

But I'm getting an error on both x86 and x64 saying: "The update is not applicable to your computer."

Could this be due to the creator's update that recently rolled out ? My Windows 10 version says 1703.

Problem solved with these updates right here: https://support.microsoft.com/en-us/help/4016817/media-feature-pack-for-n-edition-of-windows-10-version-1703-april-2017

I think I may have found a bug, when I run SR either host or join, and mods or vanilla, I have found that when I push L-CTRL + L-Win + L the game suddenly starts lagging until I exit SR, then the game is fine, but when I relaunch SR the lag returns until I exit DCS and restart it. The game runs fine otherwise and SR runs fine as long as I don't hit those keys.

Same here, happened to two of us tonight.

I did a bit of testing in the current 2.0, SRS 1.2.9.7 freshly installed before the problem occurred:

- happens in MP and SP

- happens in A-10C module (other modules not tested)

- happens even cold & dark, before switching battery on

- LCTL + LSHF + L stops the problem

- does NOT happen while in the ESC menu or in the controls assignment menu

I had TrackIR and Sim Shaker off when I tested, even commented TacView out of my Export.lua to narrow it down. Problem still happened as long as SRS was connected to a server.

Here's my Export.lua I used while testing in case it's relevant:

function LuaExportStart()
end
function LuaExportBeforeNextFrame()
end
function LuaExportAfterNextFrame()
end
function LuaExportStop()
end
function LuaExportActivityNextEvent(t)
local tNext = t
return tNext
end

-- local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua')

local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[scripts\DCS-SimpleRadioStandalone.lua]])

-- local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua')
-- dofile(lfs.writedir()..[[scripts\SimShaker-export-core\ExportCore.lua]])

Hello Ciribob,

 

I wanted to thank you for SRS and share my pleasantly strange experience with it. I have a very unique cockpit setup. It is multi monitor, external gauges with Ikarus, and I have vibrations working through exports.

 

I decided to add SRS to my setup. First thing I notice is my Ikarus gauges became choppier in performance. More similar to a Helios gauge in performance. I was put-off at first by this and then did testing to see if I could stop it. As I did my testing, I noticed that my DCS performance was smoother than I had ever seen it. I attributed this to O/C'ing my graphics card, but I then noted the poorer performance would return (please note "poorer" is still very good!).

 

I could not believe my eyes when I finally figured out what was going on, but I just sat down and verified it...

 

DCS without SRS (AO 1.5 server, L-39 cold A/C), 37-54 fps.

 

DCS with SRS running overlay on my Ikraus gauge panel, same server, minutes after first test. 71 fps.

 

I can repeat it every time and it is just amazing. I am running a life-size multi monitor setup with better performance than many get with one monitor. AO server, at maximum player numbers, smooth. I actually saw triple digit fps.

 

The slightly choppier gauges are worth it and I'll never fly without SRS again.

 

DONT... CHANGE... ANYTHING! :)

I can tell you why this is happening, the frames from Ikarus are being exported at a higher frequency than SimpleRadio Runs at. SRS exports every 0.2 second but is called every 0.1 second (which gave good results with Helios)

If you mess with this number: https://github.com/ciribob/DCS-SimpleRadioStandalone/blob/master/Scripts/DCS-SimpleRadioStandalone.lua#L83

It'll control how often your Ikarus export runs, try setting it to 0.05 instead of 1 and the gauges will get smoother but you'll lose performance as its now doing twice as much work. :thumbup:

I have a problem...

 

I can only use it in 1.5, and not in 2.0.

 

Any suggestion?

Definitely confirmed working in Nevada, just tested it. I'd do a reinstall and check the Export.lua as usual. If not, use the troubleshooting guide in my signature :)

21:14:26 Ciribob.DCS.SimpleRadio.Standalone.Client.Audio.AudioPreview Error starting audio Output - Quitting! Retrieving the COM class factory for component with CLSID {F447B69E-1884-4A7E-8055-346F74D6EDB3} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).[/code]

 

.. snip ...

 

Problem solved with these updates right here: https://support.microsoft.com/en-us/help/4016817/media-feature-pack-for-n-edition-of-windows-10-version-1703-april-2017

Thanks for that, Microsoft have a dead line on the main page... :music_whistling: I'll add this to the next release so people can find it!

Same here, happened to two of us tonight.

 

I did a bit of testing in the current 2.0, SRS 1.2.9.7 freshly installed before the problem occurred:

- happens in MP and SP

- happens in A-10C module (other modules not tested)

- happens even cold & dark, before switching battery on

- LCTL + LSHF + L stops the problem

- does NOT happen while in the ESC menu or in the controls assignment menu

 

I had TrackIR and Sim Shaker off when I tested, even commented TacView out of my Export.lua to narrow it down. Problem still happened as long as SRS was connected to a server.

 

Here's my Export.lua I used while testing in case it's relevant:

 

 

function LuaExportStart()
end
function LuaExportBeforeNextFrame()
end
function LuaExportAfterNextFrame()
end
function LuaExportStop()
end
function LuaExportActivityNextEvent(t)
local tNext = t
return tNext
end

-- local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua')

local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[scripts\DCS-SimpleRadioStandalone.lua]])

-- local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua')
-- dofile(lfs.writedir()..[[scripts\SimShaker-export-core\ExportCore.lua]])

Thanks!

I've done quite a big investigation and traced it to the new overlay.

For some reason pressing the key combination must turn on some kind of debug mode or something as LUA memory usage doubles when receiving an update until you undo the debug mode with L Cntrl + L Shift + L. Unfortunately there isnt anything I can do about this as its something in DCS that does it. I've tried to replicate in testing version but no luck so far.

00389.827 INFO LuaNET: LISTEN 56320434
00389.827 INFO LuaNET: Receive 56345182
00389.827 INFO LuaNET: Decoded 56345256
00389.827 INFO LuaNET: Assigned 56345394
00389.928 INFO LuaNET: Garbage Collected 56314651
00389.929 INFO LuaNET: Paint Start 56317917
00389.929 INFO LuaNET: Paint End 56317995

With Windows Key Hotkey Weirdness

00395.678 INFO LuaNET: LISTEN 57120082
00395.834 INFO LuaNET: Receive 106464899 -- WTF
00395.834 INFO LuaNET: Decoded 106478543 -- WTF
00395.834 INFO LuaNET: Assigned 106496603  -- WTF
00395.973 INFO LuaNET: Garbage Collected 56319716 -- Back to normal
00395.974 INFO LuaNET: Paint Start 56719112
00395.975 INFO LuaNET: Paint End 56986179

Thanks for looking into this. At least you've found the culprit.

New RELEASE Version - 1.3.0.0

.NET Version - PLEASE INSTALL THIS or it may not work: https://www.microsoft.com/en-gb/download/details.aspx?id=53345

Windows 7/8/10 N Users - PLEASE INSTALL THIS OR IT WILL NOT WORK - Adds the media codecs you need which are removed in the N Version - https://support.microsoft.com/en-us/help/3145500/media-feature-pack-list-for-windows-n-editions - You'll know when you get the audio initialisation error :)

This release tidies up a few bugs, the Overlay code slightly and adds new key binds

KNOWN BUG

If you get lag while using the radio, press L Ctrl + L Shift + L to fix. This is a DCS bug i'm trying to work around and is triggered by pressing L Ctrl + L. It doesn't matter if that key is bound or not, it'll still cause lag when you press it

Changelog

• Added Toggle Guard Hotkey
  
• Added Toggle Encryption Hotkey
  
• Added Next & Previous Radio Hotkey
  
• Added Increment / decrement encryption key Hotkey
  
• Fixed Radio Effects not saving
  
• Fixed Line of Sight not working
  
• KNOWN BUG: If you get lag while using the radio, press L Ctrl + L Shift + L to fix. You can also not use the In Game DCS overlay to stop it as well (either hide entirely or delete the DCS-SRS-OverlayGameGUI.lua )
  

Overlay and Overlay Configuration

The overlay has 3 states, hidden, small & full that you can see by pressing Left Control + Left Shift + Escape by default.

The Full state has a title bar that you can click and drag the window around with. The window position will be saved for when DCS is next opened.

The radio status is removed after 5 seconds if SRS is closed or loses server connection

To configure the overlay hotkey, run DCS once to create a config file in Saved Games\DCS\Config which will look something like so and quit DCS:

config = 
{
   ["mode"] = "minimum",
   ["hotkey"] = "Ctrl+Shift+escape",
   ["windowPosition"] = 
   {
       ["y"] = 342,
       ["x"] = 981,
   }, -- end of ["windowPosition"]
} -- end of config

Edit the "Hotkey" section and add the characters from the keyboard you'd like to use instead. i.e

config = 
{
   ["mode"] = "minimum",
   ["hotkey"] = "Ctrl+Shift+1", -- now uses the combination of ctrl shift and 1 together to toggle
   ["windowPosition"] = 
   {
       ["y"] = 342,
       ["x"] = 981,
   }, -- end of ["windowPosition"]
} -- end of config

Dont forget to restart DCS after editing this file or you wont see the changes.

If you want to remove the overlay entirely and never use it, just delete:

• DCS-SRS-Overlay.dlg
  
• DCS-SRS-OverlayGameGUI.lua
  

In Saved Games\DCS\Scripts

As always, thanks for the support and let me know if there are any issues!

Dedicated support now available on Discord: https://discord.gg/baw7g3t

DOWNLOAD THE LATEST RELEASE: https://github.com/ciribob/DCS-SimpleRadioStandalone/releases/latest

I've done quite a big investigation and traced it to the new overlay.

Good to know, thanks for looking into it! :thumbup:

Update killed my favorites again. :D

Yesterday red team on BF claimed they couldn't use SR, because it was bugged for parts of the team. Why don't bug reports in here reflect that? -.-

Hello Ciribob!

FC3 airplanes (Su-25, Su-27, MiG-29, Su-33) have radiostations with pre-loaded frequencies. So you just change the channel and ready to comm. Now we have to dial all that 6 numbers. Can you do a radio pre-set window just like it is done in DCS for L-39, Mi-8, P-51, etc?

Looks like some peeps agree with you:

https://github.com/ciribob/DCS-SimpleRadioStandalone/issues/176