DCS-SimpleRadio Standalone

[Ciribob]

I'll try to get some recordings and the other peoples values. My mic boost was -61% and speaker boost 105% (can't adjust it to 100%). But I think there's a fundamental problem with the mic boost and speaker boost adjustment as there's many balanced settings (as many as a slider has possible positions) and therefore you are unlikely to have similar (compatible) settings for every client unless you have some systematic way of ensuring it. Basically you need some benchmark that everyone can use to adjust their mic boost to correspond to like indicate a desired level in the VU meter that people should target.

 

When I actually manage to sleep - Not work... and have some free time I'll look at putting a max dB level for both input and output that should then be common for all and i'll try to find a good dB value that you should aim for.

 

It's odd that switching API has changed how audio is boosted - It seems the new sound API introduces its own boost for some reason which isn't documented :(

 

 

After updating to 1.2.8 from 1.2.6, I am unable to get SRS working. I log on to our server, where I can see that my name is allocated to an aircraft, and there is an entry on the Ckient Log (I monitor the server on a separate laptop). However, unlike everyone else, I am shown as a neutral entry (white dot), and my name does not appear against my logged on symbol on the SRS Client list. I have tried starting SRS and connecting, both before and after starting DCS.

 

The radio overlay appears, the volume and frequencies can be changed, and the transmit lights appear when I use the relevant PTT. However I neither hear, nor am heard, by the other players.

 

I was running with a triple monitor, using Helios on the second monitor and Kneepad on my third (Lilliput) monitor. However I have disabled Helios temporarily, and am using an export.lua, with just the single SRS line in it.

 

Any suggestions?

 

It sounds like your DCS-SRSGameGUI.lua file is missing or corrupt as thats what does the side and play name.

 

To do a complete uninstall - Just open the installer and press uninstall which'll remove the registry entries and should delete the script files from Saved Games/DCS/Scripts . Worth double checking after pressing uninstall that it's all gone though!

 

Hi Ciribob,

We tested it last night with the old and new API and it's working OK. It looks like updating .net and setting the volume down to -95% makes it workable. Do you have any plans to readjust the internal values so that the slider is 0% without distortion?

 

Not going to adjust yet as if I allow both old and new sound APIs to be switched between for maximum compatibility there is no common value between the two. Again not sure why as nothing in docs about taht...

 

Re my post #947 below, I now believe that my problem lies in a corrupt/mixed installation. Despite removing all immediately obvious traces of the earlier installation, there appears to be some left over. Notably the radio overlay is of what I think is the earlier pattern, that is with the selection/transmit lights on the right of the overlay, rather than on the left.

 

Furthermore, when I re-install 1.2.8.1 (New-Audio) it the initial DCS-SS CLIENT General connect screen has the server address that I had previously inserted, indicating that it is recovering this information from somewhere in my system.

 

Can anyone suggest where this left-over data is likely to be found and how I can do a full clean re-install.

 

I am using Windows 10.

 

A final puzzle is that when I try to install .NET .4.6.2, the system tells me that I have a later version already installed. However, when I scan through the Registry, I can find reference only to .4.6.1xxxx. Is this normal?

 

See Above reply for first part fix

 

For checking .Net version - https://msdn.microsoft.com/en-us/library/hh925568(v=vs.110).aspx

 

It seems to store its data in:

 

HKEY_CURRENT_USER\SOFTWARE\DCS-SimpleRadioStandalone

 

You could remove the key but only if you know what you're doing!

 

It is indeed there. Please don't delete your whole registry... :P

 

Sorry for the brevity of replies to all. Short on time! :)

[Ciribob]

Also, still experiencing significant distortion when two people speaking on the same channel (or two different channels). :/

 

Sorry missed in my mass reply!

 

If you can, please send me a recording as I think this is tied to the odd volume handling. I can't replicate on my side between multiple PCs (one wired - one connected via my mobile for different routes) so recordings will help me diagnose.

 

Thanks! :)

[Snoopy]

Sorry missed in my mass reply!

 

If you can, please send me a recording as I think this is tied to the odd volume handling. I can't replicate on my side between multiple PCs (one wired - one connected via my mobile for different routes) so recordings will help me diagnose.

 

Thanks! :)

 

I had the same thing happen my last sortie, it's on twitch. I'll post the time stamp when I get home from work.

Edited October 13, 2016 by Snoopy

[Ciribob]

I had the same thing happen my last sortie, it'a on twitch. I'love post the time stamp when I get home from work.

 

Ah prefect! Thanks!

 

Also thanks for the support! Just hope I can keep up with the development over the next few weeks as free time is not looking good... - See attached screenshot :)

[Bushmanni]

Here's the recording from my test, details in the video description. We had lots of problems setting audio levels so that sound quality would be comprehensible so if something can be done about it it would be great.

 

[Esac_mirmidon]

You must set not only de Mic boost but also the incockpit volume selector.

 

In our squad we find around 50%-60% incockpit volume strenght adjusted in the volume selector of each radio panel and -40 to +50 Mic Boost a good solution for clear radio sound and almost no distorsion.

[Snoopy]

Ah prefect! Thanks!

 

Also thanks for the support! Just hope I can keep up with the development over the next few weeks as free time is not looking good... - See attached screenshot :)

 

 

Go to approximately 1:49:50 My wing man is talking on VHF/FM and Catman 2 is on UHF.

[Rivvern]

Master Arms are struggling with the same issues as 476vfg.

 

Snoopy. Did you come so some kind of conclusion? Is there a workaround for the current version?

 

I was about to do some testing, but if i can save some time id be glad.

[Snoopy]

 

Snoopy. Did you come so some kind of conclusion? Is there a workaround for the current version?

 

 

Nope, but it only happened twice that I can remember during that sortie. Also, I could still understand what both individuals were saying so it's not unusable IMO.

[sc_neo]

Hey, i set up SRS yesterday and it looks quite the neat program. Today i noticed that the distinct transmission 'click' when pressing/releasing the ptt button is not audbile on most/all radios. I can hear it in the L-39 (only one radio), in the first AM G radio of the F-15 but not the other two radios, and in neither radio in the A-10c and SU-25T for instance. Any reason behind that or is something wrong with my installation?

 

By the way, i have addionally installed and set up the the 'auto connect promt' file on own pc from which i runs the server and dcs 1.5/2.0. I don't seem to get the auto connect promt myself. Does it work for external client connections only or should i get the promt as well if i forget to connect to my own server when i load up a dcs mission?

[Eddie]

Cribob,

 

Finally had 5 mins to play with the new ATC/AWACS panel, it's coming on nicely, however, it appears that it's not possible to transmit on two or more radios at once?

 

Unless I'm missing something and it is possible already, can this be added, please? ATC/AWACS controllers will usually need to broadcast on more than one freq. at a time (VHF & UHF tower freqs for example).

 

If possible it'd be nice to be able to use a single PTT (common PTT) and select which radios will transmit using the GUI.

[Looney]

Like Ariesradio and UR you mean?

[Cibit]

Last night was the first time I got in a huey with volume control on FM radio rolled to lowest setting. Thats the physical in-cockpit rotary. Is this part of SRS?

[TorsteinE]

Forgive me if this has been asked before, but is there a plan to add a list over recent servers to connect to? Shure would come in handy!

[Coug4r]

Yes that was requested, auto connect makes it kinda unnecessary though.

 

@Ciribob, i've seen the input or output device change a couple of times now since v1.2.8.x. So i fired SR up with my correct settings, connected and everything is fine. Disconnected, shut SR down then do stuff (not changing audio/hardware) and try SR again hours later then the input or output device sometimes changed to another in/output. Other settings are unaltered.

[Kozmyk]

Yes that was requested, auto connect makes it kinda unnecessary though.

 

@Ciribob, i've seen the input or output device change a couple of times now since v1.2.8.x. So i fired SR up with my correct settings, connected and everything is fine. Disconnected, shut SR down then do stuff (not changing audio/hardware) and try SR again hours later then the input or output device sometimes changed to another in/output. Other settings are unaltered.

Before the Win 10 Anniversary Update my default audio output device was continually changing, at power-up, between outputs A and B of my Voicemeeter. Since the Update it has all been stable. (fingers crossed)

[TorsteinE]

I'd still like the option for it, most servers don't use autoconnect yet, and connecting to "local" servers makes it annoying to keep typing in adresses.

[Recon Stewart]

So I've installed the 1.2.8.1 using the old API sounds. My client then crashes whenever I try to preview the audio or attempt to connect to a server. It says that it was unable to load opus.dll. Any ideas on how to fix this? Thanks!

 

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.UI.MainWindow Started DCS-SimpleRadio Client 1.2.8.1

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 6f1d2b60-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b60-d5a0-11cf-bfc7-444553540000 Mouse Usage: Undefined

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 6f1d2b61-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b61-d5a0-11cf-bfc7-444553540000 Keyboard Usage: Undefined

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 6f1d2b61-d5a0-11cf-bfc7-444553540000 Instance: 6f1d2b61-d5a0-11cf-bfc7-444553540000 Keyboard

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 0404044f-0000-0000-0000-504944564944 Instance: 9a8fe7d0-d407-11e5-8002-444553540000 Throttle - HOTAS Warthog Usage: Generic

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 0404044f-0000-0000-0000-504944564944 Instance: 9a8fe7d0-d407-11e5-8002-444553540000 Throttle - HOTAS Warthog

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 076406a3-0000-0000-0000-504944564944 Instance: 46ed4260-d404-11e5-8001-444553540000 Saitek Pro Flight Combat Rudder Pedals Usage: Generic

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 076406a3-0000-0000-0000-504944564944 Instance: 46ed4260-d404-11e5-8001-444553540000 Saitek Pro Flight Combat Rudder Pedals

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found c228046d-0000-0000-0000-504944564944 Instance: 284bd770-d3f7-11e5-8002-444553540000 G19 Gaming Keyboard Usage: Consumer

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found c228046d-0000-0000-0000-504944564944 Instance: 284bd770-d3f7-11e5-8003-444553540000 G19 Gaming Keyboard Usage: VendorDefinedBegin

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 00140d8c-0000-0000-0000-504944564944 Instance: d1300dd0-5579-11e6-8001-444553540000 USB Audio Device Usage: Consumer

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found c229046d-0000-0000-0000-504944564944 Instance: 284bd770-d3f7-11e5-8001-444553540000 G19 Gaming Keyboard (Macro interface) Usage: VendorDefinedBegin

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 0402044f-0000-0000-0000-504944564944 Instance: 9a8fc0c0-d407-11e5-8001-444553540000 Joystick - HOTAS Warthog Usage: Generic

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Adding 0402044f-0000-0000-0000-504944564944 Instance: 9a8fc0c0-d407-11e5-8001-444553540000 Joystick - HOTAS Warthog

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 508106a3-0000-0000-0000-504944564944 Instance: f0d4e530-d404-11e5-8003-444553540000 Programmable Hotkeys Usage: Consumer

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Client.Input.InputDeviceManager Found 0a15046d-0000-0000-0000-504944564944 Instance: 284bd770-d3f7-11e5-8005-444553540000 Logitech G35 Headset Usage: Consumer

12:38:43 Ciribob.DCS.SimpleRadio.Standalone.Common.UpdaterChecker+<CheckForUpdate>d__2 Running Latest Version: 1.2.8.1

12:38:50 Ciribob.DCS.SimpleRadio.Standalone.Client.AudioManager Error starting audio Quitting! Error:Unable to load DLL 'opus.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)

[Recon Stewart]

I was able to fix it by installing a fresh opus.dll using the following website. I can now connect to servers but the client still crashes when I try to preview audio. Thanks!

 

http://dllyes.com/opus-dll/

Edited October 15, 2016 by Recon Stewart

[Hook47]

Quick question guys- In CA/JTAC I can be heard by aircraft but cannot receive any aircraft transmission. Anyone advise on what may be the problem? LOS is not an issue

[Ciribob]

Sorry away at the moment so replies will be brief - Not trying to be rude, just little time :)

 

 

Go to approximately 1:49:50 My wing man is talking on VHF/FM and Catman 2 is on UHF.

 

Great thanks! Will have a look when I'm back.

 

Hey, i set up SRS yesterday and it looks quite the neat program. Today i noticed that the distinct transmission 'click' when pressing/releasing the ptt button is not audbile on most/all radios. I can hear it in the L-39 (only one radio), in the first AM G radio of the F-15 but not the other two radios, and in neither radio in the A-10c and SU-25T for instance. Any reason behind that or is something wrong with my installation?

 

By the way, i have addionally installed and set up the the 'auto connect promt' file on own pc from which i runs the server and dcs 1.5/2.0. I don't seem to get the auto connect promt myself. Does it work for external client connections only or should i get the promt as well if i forget to connect to my own server when i load up a dcs mission?

 

It sounds like you haven't actually turned on the mic click effects. Have a look under settings and turn them on (Tx/Rx Effects). The Mic click you're hearing in the L-39 is probably the actual in cockpit one from the module.

 

Cribob,

 

Finally had 5 mins to play with the new ATC/AWACS panel, it's coming on nicely, however, it appears that it's not possible to transmit on two or more radios at once?

 

Unless I'm missing something and it is possible already, can this be added, please? ATC/AWACS controllers will usually need to broadcast on more than one freq. at a time (VHF & UHF tower freqs for example).

 

If possible it'd be nice to be able to use a single PTT (common PTT) and select which radios will transmit using the GUI.

 

Transmitting on multiple radios is quite a big change but can be done with a lot of effort. I'd probably have to set a maximum of 2 or 3 at most to be transmitted on at one time and it would have to be done via hotkeys rather than selecting multiple radios for the minute.

 

How many would you ideally like to transmit on and whats the minimum you reckon you could get away with?

 

Last night was the first time I got in a huey with volume control on FM radio rolled to lowest setting. Thats the physical in-cockpit rotary. Is this part of SRS?

 

Nope not an SRS thing. SRS just passively takes data from DCS, no data injected back so if its at 0 volume the module just comes like that for some reason

 

Forgive me if this has been asked before, but is there a plan to add a list over recent servers to connect to? Shure would come in handy!

 

Yes its been asked before. As mentioned - the autoconnect is the stopgap until I get around to implementing a favourites / history system. No concrete plans to have an auto populated server list yet as I've got no where to host a master server for it.

 

Before the Win 10 Anniversary Update my default audio output device was continually changing, at power-up, between outputs A and B of my Voicemeeter. Since the Update it has all been stable. (fingers crossed)

 

The new API may not give me the list of audio devices consistently in the correct order which would explain the devices swapping. All I save is in index on the list so I'll switch to saving something more robust like device GUID in future.

 

So I've installed the 1.2.8.1 using the old API sounds. My client then crashes whenever I try to preview the audio or attempt to connect to a server. It says that it was unable to load opus.dll. Any ideas on how to fix this? Thanks!

 

I'd download the release again (either old or new API) and run the installer as the opus.dll should be included. Its essential you use the one that comes with the program and not one from the internet as its been modified :)

 

Quick question guys- In CA/JTAC I can be heard by aircraft but cannot receive any aircraft transmission. Anyone advise on what may be the problem? LOS is not an issue

 

Can you hear yourself if you press Preview Audio? Sounds like you might have the wrong output device.

 

Dev Update

I'm in the process of continuing the rewrite of audio input and output and will release a new testing version in a week or so. A proper packet protocol check was implemented in the last 1.2.8.1 update which now means testing versions will work against release without issue.

 

If the protocol does change it'll not let you connect so testing will be easier.

 

When I release the new version, please can those of you who are still on the old API just download it, extract the zip and try preview audio? No need to install.

 

The new api will be entirely WASAPI and also 64-bit. Its not an easy switch (http://markheath.net/post/what-up-with-wasapi) but should make it work with all sound cards.

 

Edit: It also seems that downloads have shot up!

Edited October 16, 2016 by Ciribob

[Eddie]

Transmitting on multiple radios is quite a big change but can be done with a lot of effort. I'd probably have to set a maximum of 2 or 3 at most to be transmitted on at one time and it would have to be done via hotkeys rather than selecting multiple radios for the minute.

 

How many would you ideally like to transmit on and whats the minimum you reckon you could get away with?

 

It's a case of the more the better really, but as a minimum three would likely work in most cases. ATC would want to transmit on their UHF and VHF channel simultaneously, AWACS could be broadcasting on one channel (talking to one package/flight) up to 10 if they were broadcasting to everyone in the sky.

 

Like Ariesradio and UR you mean?

 

Yeah, Looney do you have any thoughts on how many radios you'd need to tx on at a time?

[myHelljumper]

up to 10 if they were broadcasting to everyone in the sky.

 

Then can't he use the Guard frequency ?

[Eddie]

Then can't he use the Guard frequency ?

 

Well, that depends if you want the enemy to hear when you're directing fighters on to them and where you're telling the strike aircraft to retrograde to as well? You also don't want aircraft not under your control to be hearing messages not intended for them, you may have more than one AWACS airborne with each covering different airspace sectors for example.

 

Remember guard is heard by everyone in the sky and isn't secured, package and other C2 frequencies usually are both encrypted and using have quick anti-jamming.

[Hoggorm]

Hi,

 

I just tried to run a server on a spare laptop I'm using but I'm unable to connect to it...

 

I've opened port 5010 and 5002 both UDP and TCP in my Cisco E2500 router. I'm then just running the SR-Server.exe file.

 

On the client side I've tried to connect to my IP address at home both with and without :5002

 

The server is at a laptop at home, while I've tried to connect from a computer at work.

 

Am I doing something wrong since it's not working?