Accessing a game will flood the console with the same two errors, regardless of the game. Issue persists after clearing all appdata files associated with YNOdesktop and after adding the binary/zip to my AV exceptions and also disabling shields (I'm using Avast, its cybercapture feature is extremely trigger happy). This issue was not present on the previous release nor does it occur in Firefox. It affects both the DRPC and NoDRPC versions.
This could perhaps be an issue with YNO itself. The console throws 404 errors and all sorts of warnings regularly, which you can see in the screenshot below. A while back the website would look for a "niko" charset when playing anything but OneShot...
That said, the presence of the notification as well as the flooding of the console could be a concern for some users. I initially caught the issue on the 21 of December and decided to stay in version 1.2.2. I've now tested once again and more thoroughly to confirm it hasn't gone away.
The errors I'm referring to are right after the ScriptProcessorNode deprecation warning:
Accessing a game will flood the console with the same two errors, regardless of the game. Issue persists after clearing all appdata files associated with YNOdesktop and after adding the binary/zip to my AV exceptions and also disabling shields (I'm using Avast, its cybercapture feature is extremely trigger happy). This issue was not present on the previous release nor does it occur in Firefox. It affects both the DRPC and NoDRPC versions.
This could perhaps be an issue with YNO itself. The console throws 404 errors and all sorts of warnings regularly, which you can see in the screenshot below. A while back the website would look for a "niko" charset when playing anything but OneShot...
That said, the presence of the notification as well as the flooding of the console could be a concern for some users. I initially caught the issue on the 21 of December and decided to stay in version 1.2.2. I've now tested once again and more thoroughly to confirm it hasn't gone away.
The errors I'm referring to are right after the ScriptProcessorNode deprecation warning: