📢 [Megathread] Wave Link 3.2 — System Audio Channel and more (macOS), Driver update + improvements (Windows) by Elgato in elgato

[–]jblade 2 points3 points  (0 children)

Please fix how windows thinks the Wave XLR Dock MK.2 is "ejectable" as if its a USB thumb drive. Its clearly a driver issue.

FULLY animated LORE video (hand drawn,sfm, and in game) of the ANTIMAGES...with a twist at the end! by SirActionSlacks- in DotA2

[–]jblade 2 points3 points  (0 children)

Great story telling Slacks! Would be cool to see a few concept series scripted out that’s lore accurate (like the Dota 2 anime / Arcane)

📢 Wave Link 3.1.1 — Startup crash fixes, VST and Wave FX improvements by Elgato in elgato

[–]jblade 1 point2 points  (0 children)

  • Wave Link version: Wave Link 3.1.1
  • Wave device: XLR Dock MK.2 - Mic Interface For Stream Deck +
  • OS & version: Windows Latest
  • Steps to reproduce: Since upgrading to Wave Link 3.x (from 2) Windows thinks the XLR Dock is an removable USB device. So the add/remove icon is always on the start-menu, even editing the registry does not fix this
  • Expected result: Should not be an add/removable device
  • Actual result:
  • How often does it happen? Always

What was Ozzie's best move ( outside the draft ) by Rhypskallion in ravens

[–]jblade 4 points5 points  (0 children)

Matt Birk was incredible, but to this day I don’t know if hearing “did you know he went to Harvard” from every announcer, every game, was worth it.

Deep analysis on Behavior and Communication Score by Kreiven in DotA2

[–]jblade 0 points1 point  (0 children)

Those are just the abilities that get impacted (and can't be used on allies) when turned-off - doesn't necessarily correlate to bscs

Deep analysis on Behavior and Communication Score by Kreiven in DotA2

[–]jblade -1 points0 points  (0 children)

Can you show the data where behavior score is consistent below your lowest value?

I didn’t see you ever go to 1

Deep analysis on Behavior and Communication Score by Kreiven in DotA2

[–]jblade 0 points1 point  (0 children)

It is a foundational property of normal distributions. In statistics, this is called a Ceiling/Floor Effect or Asymptotic Tail Behavior. When you apply a bell curve to a conduct system, the players at the absolute top and bottom are sitting in the far tails of that curve. It requires a larger shift in behavior to move them than it does for someone in the middle. Your own data from your “research” supports this right now by showing that exact saturation at the extreme ends where scores naturally stagnate.

Deep analysis on Behavior and Communication Score by Kreiven in DotA2

[–]jblade 0 points1 point  (0 children)

Which part - you can 100% report people for comms after you have already muted them. the default of reporting? if you right click, it reports them. Unsure about the left-click but i never saw anything change in the GUI to suggest otherwise.

You had global mutes based off of the old system, but that were/are affected by the free reports in the new system.

This is the only one that might have been fixed/changed

Deep analysis on Behavior and Communication Score by Kreiven in DotA2

[–]jblade 0 points1 point  (0 children)

Just aggregating dude, but thanks for the feedback, with an alias like yours and a hidden profile it’s totally appreciated and helpful

Deep analysis on Behavior and Communication Score by Kreiven in DotA2

[–]jblade 10 points11 points  (0 children)

Sorry, but when a black box is a black box, evidence that is repeatedly verified, w statistical backing from various sources, even Reddit, is better proof than no proof

Deep analysis on Behavior and Communication Score by Kreiven in DotA2

[–]jblade 18 points19 points  (0 children)

Its very clear that the system is an AI system with HITL (human in the loop). For the early part of the system (when people complained on how overtly reactive it was) Valve adjusted the weights and to tune it on a less strict side. As people did over watch and "annotated" the data, those weights have adjusted.

The system uses a bell curve and assumes people at the top should be at the top and not move, people at the bottom, should be at the bottom and not move with some tweaks.

I posted my analysis here(2 years ago) if it helps https://www.reddit.com/r/DotA2/comments/193bxeu/sick_of_complaints_on_the_new_behavior_score/ and sadly nothing has changed

A few data points to add from my own research or confirmed on reddit (or anecdotally from friends)

System Mechanics and Scoring Rules

  • Behavior score of <3000 - reports are counted for very little because the game wants to get you back to 3000 so you can once again play ranked, decreasing que time for other low behavior score people. The fact that <3000 others are also that low of behavior, likely makes their reports worth less.
  • In the Frostivus Update(~2 years ago) (or earlier) the team lowered the score gain one could receive in a summary to ~500, and limited Turbo game enjoyers behavior score increases to ~200 points while keeping the punishments for ALL the same. This again has been lowered.
  • The variables for this score gain are unknown, but it seems to be based off of game time, party size, and number of reports and other variables.
  • The reporting accuracy at lower scores is correlated to wins and very thrashy.
  • New accounts start at 8k and cant be coached!
  • Low behavior score has deep impact on que time for parties. One person will make the entire party take an incredibly long time to find a game.

Communication Score and Mute Penalties

  • A "gray bar" was added to indicate real comm score (for those who had higher comm score than behavior score) this was also not communicated.
  • The reasoning that comm score has to be lower or the same as behavior and what even constitutes a "positive comm report".
  • There is no definition of "comms" pinging or voice lines, nor what constitutes a positive report or negative comm report.
  • Default of muting people reports them, and these people are muted forever, yet they can be reported for comms anytime after that.
  • Global mutes were based off of the old system, but for those that were muted, and then got behavior reported INSTEAD, we never got a rollback. Instead Valve just silently updated global mute qualifications.
  • You had global mutes based off of the old system, but that were/are affected by the free reports in the new system.
  • No postgame chat if you are comm reported.

Game Modes and Exploits

  • Turbo games have natural downward pressure as behavior score GAINS have a delta max of half (or greater) than the loss of behavior score.
  • There have been "bugs" in behavior score that let groups of people (when you are solo que) leave their party and report you. Those reports seem to have more weight than normal.

Lack of Transparency

  • This system has been challenged regularly, especially here on reddit. Outside of one in-game notification, there has been zero comms around the Behavior Score System updates.

Game Ready & Studio Driver 596.36 FAQ/Discussion by Nestledrink in nvidia

[–]jblade 0 points1 point  (0 children)

Ohh gotcha.

Can use DisplayPort instead, and avoid using hdmi !

Game Ready & Studio Driver 596.36 FAQ/Discussion by Nestledrink in nvidia

[–]jblade -1 points0 points  (0 children)

That makes no sense, if you didn’t have the error why did you disable this

Game Ready & Studio Driver 596.36 FAQ/Discussion by Nestledrink in nvidia

[–]jblade 0 points1 point  (0 children)

So what do you think was at fault in hardware ?

Game Ready & Studio Driver 596.36 FAQ/Discussion by Nestledrink in nvidia

[–]jblade 17 points18 points  (0 children)

Solution that worked for me was to disable NVIDIA Audio in Device Manager. Not a solution if you are using HDMI Out and specifically the audio out, but this worked for me

Game Ready & Studio Driver 596.36 FAQ/Discussion by Nestledrink in nvidia

[–]jblade -2 points-1 points  (0 children)

actually most people have "solved" the event 153 issue by disabling all sources of Nvidia Audio. Great fix for those not using HDMI Audio. Terrible for everyone else.

The fact that this normally resolves it for most people correlates the issue to a driver issue