You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Mumble for positional audio, in addition to Blish HUD, going through 2 loading screens seems to disconnect MumbleLink from GW2 temporarily and when the link "light" returns, Blish still doesn't respond properly. Currently the suspect is the linked section starting at 93 and current suspicion is that Blish doesn't know how to handle it when a disconnect happens without the game closing, causing the _prevTick to be GREATER than this.RawClient.Tick and "hangs" until the normal criteria is met. Maybe a case statement that also sets _prevTick to be equal to this.RawClient.Tick could handle this, but I have no idea if that could potentially have other effects or cause float errors or anything.
Contact DragonHeart996 if you need someone to test it.
The text was updated successfully, but these errors were encountered:
DragonHeart has made a forked version and it seems to work with just this one line change! Of note, it may cause issues with making Blish falsely detect TacO as running?
Blish-HUD/Blish HUD/GameServices/Gw2MumbleService.cs
Line 93 in 1459439
When using Mumble for positional audio, in addition to Blish HUD, going through 2 loading screens seems to disconnect MumbleLink from GW2 temporarily and when the link "light" returns, Blish still doesn't respond properly. Currently the suspect is the linked section starting at 93 and current suspicion is that Blish doesn't know how to handle it when a disconnect happens without the game closing, causing the _prevTick to be GREATER than this.RawClient.Tick and "hangs" until the normal criteria is met. Maybe a case statement that also sets _prevTick to be equal to this.RawClient.Tick could handle this, but I have no idea if that could potentially have other effects or cause float errors or anything.
Contact DragonHeart996 if you need someone to test it.
The text was updated successfully, but these errors were encountered: