ChaosRifle Posted October 27, 2023 Posted October 27, 2023 (edited) Loving the new changes, but a few things I think are needed to supplant SRS 1: default VOIP volume needs to be like 10% tops. holy crap, you are blowing peoples speakers and eardrums. its INSANELY loud by default. People are genuinely warning their friends before they boot up 2.9 because its so loud. That should NOT be a thing. I get that high impedance audio devices are a thing, and you need to be able to go that high for very specific, high end older gear, but that is not the norm. defaults are for the norm. Lets tone that default down to 8%-10%. 2: routing of audio to one ear, if desired: IE, Com1 to left ear, Com2 to right ear, com3 to both ears, as an example. user definable. This is partially an accessibility option. 3: Mic clicks to know when someone, or you, are keyed up. 4: Hornet MIDS is not present. Would like to see that added to the default radios and supported. 5: Distance based VOIP ranges - being able to radio someone 1000nm away on 30fm is, afaik, wrong. to my knowledge, there is no ill effects of range on the voip solution at this time. Not a huge issue, but would be nice to have some restrictions to play with the radios 6: standalone software to support people doing stuff like overlordbot or lotATC. (I know, this is planned, just reinforcing the need for this. Great stuff ED) 7: a tickbox on the server options to not allow connections from users that do not have VOIP enabled, giving them a popup warning (like integ check or server full warnings). (yes, technically, when we get the standalone software we could write some sort of script to do it ourselves using the slot-in callback for lua scripting, but having a native option would be nice) 8: bit controversial possibly, and assuming its not a bug: I really struggle to understand people over the ARC-210 (in hornet) when the receiver filter parameters are on. They make it sound like you are talking into a fan, and make the audio clip horribly. I know, radios are not perfect, and I am out of my depth here as to what is should sound like, but even if it is meant to be this bad, it might be worth allowing users to change its volume or disable that without server permission to do so, as it really is an accessibility thing, that won't affect other peoples experience. To be clear here: i don't want perfect radios. I just want to not have to ask a guy to repeat himself five times before giving up and reverting to using SRS instead. 9: the UI is opaque, and has a TON of wasted space. SRS is a great example here, its compact, transparent backdrop (on one of its modes). again, really digging the new changes, its so close to making SRS obsolete, which is one more barrier to entry for players doing multiplayer getting removed. Edited October 29, 2023 by ChaosRifle added 9 3
Hotdognz Posted October 28, 2023 Posted October 28, 2023 +1 For all of the above and for it to work 100% with every client, I know its a work in progress but at any point in its development our squad wont move until we know it will work for everyone. 1
Members igor.dmitriev Posted October 30, 2023 Members Posted October 30, 2023 On 10/27/2023 at 11:47 AM, ChaosRifle said: 5: Distance based VOIP ranges - being able to radio someone 1000nm away on 30fm is, afaik, wrong. to my knowledge, there is no ill effects of range on the voip solution at this time. Not a huge issue, but would be nice to have some restrictions to play with the radios Could you please provide more specific example? It worked like it should, with radio signal degrading over distance, with no 1000nm far communications, but maybe something did break in 2.9.
ChaosRifle Posted October 30, 2023 Author Posted October 30, 2023 20 minutes ago, igor.dmitriev said: Could you please provide more specific example? It worked like it should, with radio signal degrading over distance, with no 1000nm far communications, but maybe something did break in 2.9. precisely that, currently, in my testing (at release of 2.9, not in current hotfix) we found (group of friends) that radios were not displaying degradation of quality or loss of signal based on range. good to hear that was previously a feature that worked, so likely a bug. (never used built in voip until 2.9's overhaul) AFAIK they do however account for terrain?
Members igor.dmitriev Posted November 3, 2023 Members Posted November 3, 2023 On 10/30/2023 at 6:50 PM, ChaosRifle said: precisely that, currently, in my testing (at release of 2.9, not in current hotfix) we found (group of friends) that radios were not displaying degradation of quality or loss of signal based on range. good to hear that was previously a feature that worked, so likely a bug. (never used built in voip until 2.9's overhaul) AFAIK they do however account for terrain? It does account for terrain as well as for the radio horizon. Once everything is working good, try turning Squelch off and diving below a mountain, you'll see smooth signal degradation over the distance.
Recommended Posts