Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Emma9]

What have everyone's experiences with using this implementation been? Spotty here...Firefox wasn't running it, so I switched to Chrome, worked for a while (known bugs/match issues notwithstanding), then Chrome started crashing after every couple of games, back to Firefox, that worked for a while, then this started popping up:

The browser could not allocate enough memory for the WebGL content. If you are the developer of this content, try allocating less memory to your WebGL build in the WebGL player settings.

So back to Chrome, which is working for now, but with major lag - not during play proper, but whenever I try to open settings/chat/log or even zoom into a card, I can expect the browser to hang for a minute at least, ditto after each match.

[popsofctown]

I wonder if it's the exact same memory and performance excesses that make the standalone app melt computer fans, just webGL refuses to put up with it.

Or maybe it's different.

[DG]

I've been using the browser version and it has been running ok. I actually installed the windows version today for the first time and that does run better (the graphics were scaling better, for example).

[Deadlock39]

I was resigning games over and over working on my side log plugin, and definitely noticed things getting slower and slower. I assume there are some memory leaks in their implementation still, so you may need to refresh every so often.

[YooperJake]

This mirrors my experience quite closely. 

[Limetime]

Whenever I try to do it on a chromebook it takes forever to load and then it crashes when I try to login.

[dedicateddan]

Takes a while to load, then crashes a lot

[Lekkit]

I have only tried it at work since I can't install the client which I use at home. No success whatsoever.