I change the volume from 1.0 to 0.20, be it in the mechbay or in a match, the audio level is as I wanted it, but the very next match, when I'm in the dropship about to drop, the game volume goes back to 1.0 levels. I go back to settings and the volume bar is still at 0.20. Touching the slider to move the bar eg from 0.20 to 0.21 changes the volume back to the desired levels.
This is happening for every match.


Audio Volume Bug
Started by arcana75, Sep 28 2017 03:56 PM
7 replies to this topic
#1
Posted 28 September 2017 - 03:56 PM
#2
Posted 28 September 2017 - 08:34 PM
Don't have my game under my eyes but did you try to put every volumes on the in game settings at 0.2? (so effects music master etc)
And if this continue for you, you can adjust it by the windows volume ftm and signal it at pgi contact and making a post with a little video on workaround to show that and link it with your ticket. It seems (for me) a really annoying and dangerous problem (not ironical I'm serious). I'm gonna to check it when I get home but I didn't notice that for moment.
BTW did you try to put your volume at 0.25 or another value? Maybe it's just a bug with the 0.2 value
And if this continue for you, you can adjust it by the windows volume ftm and signal it at pgi contact and making a post with a little video on workaround to show that and link it with your ticket. It seems (for me) a really annoying and dangerous problem (not ironical I'm serious). I'm gonna to check it when I get home but I didn't notice that for moment.
BTW did you try to put your volume at 0.25 or another value? Maybe it's just a bug with the 0.2 value
#3
Posted 28 September 2017 - 08:41 PM
The other sound bars are at different values eg music at around 0.6, dialogue and effects less than 1.0 but don't recall what. The master is at 0.2x. It didn't matter if it was 0.21 or 0.5 or 0.25, the same volume bug is present once the new match starts. Suddenly the audio of the "System Online, xxx Nominal" would be very loud, and the drop sound and everything as well. Going into Settings while in battlefield shows all sound bars untouched (ie at 0.2x, 0.6, etc) but just touching the master to move it abit resets the audio to the desired levels.
Changing the volume is not an option for me right now, cuz doing so will cause my recordings to be too soft.
Changing the volume is not an option for me right now, cuz doing so will cause my recordings to be too soft.
#4
Posted 28 September 2017 - 08:49 PM
Thx for the precisions. I mean gonna to check it by myself in something like 7 to 8 hours when I'm home if I have a similar problem.
I hope someone could help you before that.
I hope someone could help you before that.
#5
Posted 29 September 2017 - 02:53 AM
arcana75, pardon my asking a weird question, but you are clicking the "Save" Button on the left side after making those adjustments, right? 
More seriously, which version of the MWO Client are you running, the 64-bit or the 32-bit? Sometimes using the other one can help with weird bugs and issues. In my case, back when I only had 8 GB of RAM, forcibly using the 32-bit version took care of a lot of issues that I was having with the 64-bit version until I was running on 16 GB. Here's a link to info on how to manually set up your own 32-bit launching shortcut...
-->> https://mwomercs.com/forums/topic/224380-force-32-bit-game-client-missing/page__view__findpost__p__5083378
...so you have a chance to see if anything will act less problematically.
Also, there may be one other possible problem, but there's no fix for that one that I know of. Sometimes Windows mistakenly thinks it needs to protect certain files from harm and/or changes, and it won't let the file be written to. You can verify that one, I think, through changing some other item in the Settings, telling it to Save, and then restarting the Client and seeing if that item was changed back without your doing anything. I hope this isn't happening to you, but it just happened to cross my mind.
~D. V. "does not like the idea of somebody's ears being unnecessarily hurt" Devnull

More seriously, which version of the MWO Client are you running, the 64-bit or the 32-bit? Sometimes using the other one can help with weird bugs and issues. In my case, back when I only had 8 GB of RAM, forcibly using the 32-bit version took care of a lot of issues that I was having with the 64-bit version until I was running on 16 GB. Here's a link to info on how to manually set up your own 32-bit launching shortcut...
-->> https://mwomercs.com/forums/topic/224380-force-32-bit-game-client-missing/page__view__findpost__p__5083378
...so you have a chance to see if anything will act less problematically.

Also, there may be one other possible problem, but there's no fix for that one that I know of. Sometimes Windows mistakenly thinks it needs to protect certain files from harm and/or changes, and it won't let the file be written to. You can verify that one, I think, through changing some other item in the Settings, telling it to Save, and then restarting the Client and seeing if that item was changed back without your doing anything. I hope this isn't happening to you, but it just happened to cross my mind.

~D. V. "does not like the idea of somebody's ears being unnecessarily hurt" Devnull
#6
Posted 29 September 2017 - 03:48 AM
Thanks for the reply DVD, yes I hit save.
I don't have a choice of 32 or 64 bit I use the steam version.
Anyway this happened last night as I was using my BT headphones for the first time. Problem with this is that even at volume 5/100 in Windows, I need to bring the volume in-game to 0.2. Strangely this is not an issue with my headphones in wired mode (yeah it does BT and wired) or when piping to my panel via DP. Wired or DP mode, I leave everything at 1.0 which was why I never noticed this issue.
I don't have a choice of 32 or 64 bit I use the steam version.
Anyway this happened last night as I was using my BT headphones for the first time. Problem with this is that even at volume 5/100 in Windows, I need to bring the volume in-game to 0.2. Strangely this is not an issue with my headphones in wired mode (yeah it does BT and wired) or when piping to my panel via DP. Wired or DP mode, I leave everything at 1.0 which was why I never noticed this issue.
#7
Posted 29 September 2017 - 04:09 AM
arcana75, on 29 September 2017 - 03:48 AM, said:
Thanks for the reply DVD, yes I hit save.
<<<snip>>>
Anyway this happened last night as I was using my BT headphones for the first time. Problem with this is that even at volume 5/100 in Windows, I need to bring the volume in-game to 0.2. Strangely this is not an issue with my headphones in wired mode (yeah it does BT and wired) or when piping to my panel via DP. Wired or DP mode, I leave everything at 1.0 which was why I never noticed this issue.
<<<snip>>>
Anyway this happened last night as I was using my BT headphones for the first time. Problem with this is that even at volume 5/100 in Windows, I need to bring the volume in-game to 0.2. Strangely this is not an issue with my headphones in wired mode (yeah it does BT and wired) or when piping to my panel via DP. Wired or DP mode, I leave everything at 1.0 which was why I never noticed this issue.
You're welcome, and thank you for putting up with my asking such a lame question. Getting down to the other issue at hand, it sounds to me like your BT (BlueTooth, perhaps?) Headphones may have some kind of auto-amplifier that they're kicking in when they're not wire-tethered to your computer. If you can, check any settings you can find specifically for the particular device itself in Windows, as well as any settings that are directly adjustable on the headset itself. There might be a way to fix that problem... At least, I hope there is.

As for the other part...
arcana75, on 29 September 2017 - 03:48 AM, said:
I don't have a choice of 32 or 64 bit I use the steam version.
You might not have the choice directly from either the StandAlone launcher (both Old and New Portal) or the Steam launcher, but if you follow the instructions I linked to in MWO's Forums at https://mwomercs.com/forums/topic/224380-force-32-bit-game-client-missing/page__view__findpost__p__5083378, you'll find that you can rather safely bypass the normal launching method to diagnose the issue, and see if using the other version of the MWO Client can help you at all. It's still up to you whether you try the manual bypass launch or not, but I thought it might help work around something.

~D. V. "There's got to be some way to fix this skunk of a problem..." Devnull
#8
Posted 30 September 2017 - 02:55 AM
Thanks DVD, I think I'll just have to deal with it.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users