Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Volume is high initially, but then is lowered and stays lowered after first death #16

Closed
miguno opened this issue Jun 23, 2022 · 0 comments

Comments

@miguno
Copy link

miguno commented Jun 23, 2022

First, thanks for developing this tool!

Description

I have noticed that initially when joining a game, the volume has a level of (say) 100%. Then, after the first death (I think that's what triggers it), the volume is lowered and stays low. Is there a way to re-raise the volume after death?


(Edited) From the README:

Its simple, it lowers the csgo.exe volume when it detects a death and returns the volume when you get to freezetime. This effectively means your volume will be low for everything (e.g. Deathmatch) except actual matches (competitive / casual) where there is freezetime.

Hmm, this could be the issue. I recall that I notice it mostly when playing DM, which means there is no freezetime. This could be the reason why the volume is never reset (raised) after the first death.

Question: IIRC, GSI data (game state integration) exposes the type of the current match, i.e., whether it is DM, competitive, etc. This would allow putting in conditional code that (a) keeps the current behavior when playing competitive matches vs. (b) does not change the volume when playing DM?

Here's an example snippet from the map provider of GSI, which includes the game mode. Example values for mode are:

  • "competitive"
  • "deathmatch"
  • "custom"
  • "casual"
  • "cooperative"
  • "scrimcomp2v2"
  • "skirmish"
  • "survival"
  • "training"
{
    "map": {
        "mode": "competitive", // <-- this entry
        "name": "de_mirage",
        "phase": "live",
        "round": 0,
        "team_ct": {
            "score": 0,
            "consecutive_round_losses": 0,
            "timeouts_remaining": 1,
            "matches_won_this_series": 0
        },
        "team_t": {
            "score": 0,
            "consecutive_round_losses": 0,
            "timeouts_remaining": 1,
            "matches_won_this_series": 0
        },
        "num_matches_to_win_series": 0,
        "current_spectators": 0,
        "souvenirs_total": 0
    }
}

In the current gamestate_integration_VolumeFix.cfg, the map provider is disabled:

Enabling the map provider should have minimal impact because its data volume is small. Also, I can confirm that the data from the map provider is not restricted to spectators-only, i.e., it is actually available in any situation (i.e., when playing, when observing, etc.).

Environment

The software version is 1.1 as of Jan 2022. OS is Windows 11.

My settings:

  • Death volume 40%
  • Flash volume 10%
  • Bomb explosion volume 20%

Related Issues

  • This might be related to or the same issue as Not working well #15. The issue description sounds similar.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant