This is an error that some of our users receive (about 1k a week).
when playing lol, and no highlight was captured, on match end the replays onCaptureError throws the following error:
{"error":"StreamingErrorEvent","reason":"failed to start game recording","additionalInfo":"Unknown"}
We were unable to reproduce the issue consistently so we don’t know to pin point at what scenario does it happen
Impact for my app: mid
Do you currently have a workaround? No, this is purely a replays API issue
@shir.brass to clarify and understand the issue: before i deep dive to the logs - did you get all the events as expected, etc., and you just got the unwanted StreamingErrorEvent error, OR you were supposed to capture the highlights, and they weren’t captured at all?
Hi. We examined the logs, and we found out that this is a PBE client, which is not supported.
Besides, the PBE allows you to run LoL in DirectX 11, which not supports highlights recording yet.
BTW - you mentioned that it happens to ~1K users per week. Note that this is a friction of your users (~0.05 or something like that from your users, I don’t remember the exact number). So basically, a minority of your users get that error.
Shir,
PBE is supported, handling it app-wise is not the correct solution.
We’ve investigated this further and found that the PBE has the ability to render the game in DirectX 11 with some configuration changes.
These users who ran DirectX 11 are the one where Overwolf wasn’t able to render the overlay and start streaming in.
We’ve released a fix in the Gameslist to support DirectX 11 for League of Legends, that should resolve your issue.
There’s no need to take any action from your side.
Just to clarify:
even though the ticket originally refers to LoL only, the problem I described appears to be broader and effects more games.
I wish for the problem to be resolved to all games so let me know if you prefer that we’ll carry over the work with this discuss or shall I open new discuss issue(s)
According to R&D, it’s a Vulkan related issue (on R6, not LoL).
We need a user that can reproduce this error in order to investigate / fix it @shir.brass