10-22-2019
|
1 | |
Super Moderator
Join Date: Aug 2011
Posts: 724
|
WebGL Update Discussion & Bug Reporting Thread
As many of you have already noticed, the flash client has been replaced with a new WebGL client in these places: classic.graalonline.com era.graalonline.com zone.graalonline.com olwest.graalonline.com (This one is new!) We've just had our first round of bug fixes. The following issues from this thread should now be fixed:
Future bug reports and discussion of the client should be done here regardless of the game. Please make sure your browser is updated before you report any bugs and, if you get an error that says something along the lines of "See your browser JavaScript console for more info", please include the console log. Click here if you aren't sure how to get your console log (but disregard the part about sending them to support, as that is specific to their website. I'd recommend putting them in a text file and then attaching it to your post). Please also include what browser you are using with any bug reports (Chrome, Internet Explorer, Opera, Firefox, etc). Note about "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": Spoiler
Last edited by Jarace; 11-10-2019 at 08:18 PM.
|
|
10-23-2019
|
5 |
:pluffy:
Join Date: Aug 2011
Location: Sweden
Posts: 5,945
|
on chrome (likely applies to other browsers) -emojis are messed (ctrl + anything uses the browser's hotkeys, like ctrl + s opens up the save dialogue) -inconsistent ping, 170, 300, 280, 155, etc. actual command takes longer than usual to show me my ping. getting a consistent 150-155 on my phone over wifi -related to latency: everyone moves choppy. are we being re-routed through a proxy or something before hitting the normal server??? -fonts in general rendered differently and dont look right (likely need to be changed) -ingame chat text looks a bit blurry, this feels like a very old change around the v2/v4 era so i dont know if this is better or worse, but def not as crisp as before. might come down to preference -typing characters like @ twice will cause the next one to print 3 times (so @@@ becomes @@@@@). everytime the character is typed from there it will print 3 times. tested with [ ] * etc -opening the chat box and typing and then closing it (not with enter, i.e pressing tab) will cause the text you were typing to still be printed on the top left in yellow underneath the gui -nordic characters like ๖ไๅ all show up as "รรร" -cant copy or paste from textbox, attempting to paste shows "รรร" -scroll wheel only moving the window panes (like options for example) at a minimal pace despite my Windows wide setting being at a moderate rate Suggestion: -give us the option to disable "Upload Screenshot to FaceBook", FB Graal has been dead for a long time and I'd much rather save my images to my device
Last edited by Crono; 10-23-2019 at 09:08 PM.
|
10-23-2019
|
7 |
Kutsuu Divine
Join Date: Dec 2012
Location: Void
Posts: 62
|
Not sure, for me the game/client is very laggy now. For some odd reason my classic country thinks i'm placed in France. So I am unsure of how to fix that. I get over 200+ MS and the client itself skips mad frames. I never had this problem with the old flash player. I got about 30MS on classic easily.
|
10-23-2019
|
10 | |||
Registered User
Join Date: Jan 2016
Location: Neverland
Posts: 497
|
At the very least, cache is. I think we might be lol
This is one of the errors I noticed in the console. |
|||
10-23-2019
|
13 |
:pluffy:
Join Date: Aug 2011
Location: Sweden
Posts: 5,945
|
-Everyone still moves extremely choppy despite the improved ping, are we vpn/proxy'd? It really does look like it for some reason. -Ping still jumping to 280-320 when it should be sitting at 150-155 stable like on my phone via wifi. |
10-24-2019
|
15 |
???
Join Date: Dec 2011
Posts: 291
|
Using Facebook Gameroom doesn't even work. Getting a "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." Playing normally in a browser (both Chrome & Firefox) works fine though. |