• Dear forum reader,
    To actively participate in our forum discussions or to start your own threads, in addition to your game account you need a forum account. You can     REGISTER HERE!
    Please ensure a translation in to English is provided if your post is not in English and to respect your fellow players when posting.

Feedback [Feedback] - HTML5 on Beta

  • Thread starter Retired Community Manager
  • Start date

qaccy

Emperor
Thyrgrym the bold said:
Can someone from Inno at least acknowledge if they are working to fix the GvG lag issues in HTML5? It's currently worse on Beta than on live.
Click to expand...

The HTML5 beta client as a whole is, funny enough, in the beta stage. Don't look at the HTML5 version as if it's finished, because it's not. This thing's probably going to be in development for several more months before it hits the live servers, at which time you can start lobbying your grievances if there are still performance issues. For now, look for bugs instead.
 

xivarmy

Overlord
Perk Creator
qaccy said:
The HTML5 beta client as a whole is, funny enough, in the beta stage. Don't look at the HTML5 version as if it's finished, because it's not. This thing's probably going to be in development for several more months before it hits the live servers, at which time you can start lobbying your grievances if there are still performance issues. For now, look for bugs instead.
Click to expand...

Serious performance issues should be raised and acknowledged long before it's even hinted at going to live. Yes it's beta. Yes performance will hopefully get better. No that doesn't mean we should be silent that performance is an issue until it's live already (certainly not til there's an official statement to the effect that devs don't consider the current performance adequate yet).
 

DeletedUser8854

Guest
Hi, it's fantastic. New impressions, new achievements, new pleasure!!!!!! Thanks to You FOE becomes better and better. yay yay yay weeeeeeee :);):):)
 

DeletedUser

Guest
In general we are looking into performance and memory usage. How this may affect GvG overall I really do not know at this time.
 

Bruce the Destroyer

Steward
This new HTML5 version isnt a new game. it's simply them porting the flash swf to using OpenFL/Haxe. thats why is looks very very similar to the flash version. its a good step forward, but its not the complete rewrite that many of us were hoping for. will the memory leaks disappear ? probably not, as I suspect all the bugs got ported too

maybe we can push to get gvg fixed. like when the game crashes when someone else kills a siege or one of the DA
 

DeletedUser6645

Guest
Off course I hope that other people give feedback so there is a bit of bystander effect here.
Supposedly max 1,5 gb of ram should be used by Chrome, I read somewhere it's capped. However opening foe beta in html5 uses 4 gb ram (of 8) If it's capped then quite impressive and I'm not even mad. You managed to put so much on the client side (yeah lazy or economical on your side) and everyone will have a different issue depending on their system.

If I have the game open for 15 minutes, waiting to collect things run smooth for the first 5 minutes or so. When collecting icons are bouncing everything slows down, nevermind collecting past 100 fp or going to messages to see where I can dump that 100 fp. Everything grinds to a halt!

I'm just saying the following things: memory leaks+ infuriating lag= frustrating me to the point I'm walking away from the game for a week.

Foe Sessions need to be kept under 15 minutes for me whatever I do and then I have to refresh. Chat, reading mail, G.E. hahaha GvG. Kinda horrible experience here and don't you dare not compensate the html5 testers!
 
Prom d Exolandia

Prom d Exolandia

Baronet
I agree, performance was realy realy not good with flash game it is worst with HTML5 :s since a few months many players leave the game because of these performance problems.
You only have to see that post to understand that players are exhausted :
https://forum.fr.forgeofempires.com/index.php?threads/foe-gel.99340/

We want a payable game with a normal computer (no GeForce graphic card, no 8Go RAM, no fibre network...)
I have a windows 7 computer with celeron 1,4GHz, intel graphical card (without dedicated memory) and 2Gb of RAM and it is not possible to play that game with this computer...

I do not understand why you use so big images in that game, i do not understand why you download sound when it is off... i do not understand why u dont user webcache (numbers à the end of each image won't allow to use webcache)... i do not understand...

I don't know why i have to download that on your images :
180220091245390774.jpg
I pay for that kb downloaded... is that really serious ?
 
Last edited:

DeletedUser16

Guest
It seems that there may be a misunderstanding when it comes to our intentions.
The fact that the HTML5 version has some performance issues is well known to the development team. That is why it's on Beta, and there is no intention of rushing it to live. Of course the HTML5 version will go live eventually, but the performance has to get better (and it will get better) before this happens. This is not only about GvG but about the entirety of the game.
That's why your continuous feedback is so important :).

Thank you!

Prom d Exolandia said:
I don't know why i have to download that on your images
Click to expand...
It seems to be some kind of an old placeholder image :). It was removed now and will be gone from Beta with the next daily update.
 

DeletedUser8277

Guest
The HTML version of the game seems to keep getting laggier and slower with each day. I'm not sure if perhaps more people switching over is making it run more jagged. Typically my beta game is laggier which makes sense as I'm across the pond from the server but the time each action takes is becoming longer and longer. What info are the devs looking for us to gather performance wise?
 
RedRed

RedRed

Viceroy
I guess that about the optimization there are still big steps to do :)

This is the the dev console a couple of minutes after entering the game, no actions done (just loaded and waiting), shows more than 500 warnings in the "verbose" category (optimization stuff), still growing while I'm writing (700+ after 10 minutes); if you look at the times, some took seconds...

6muWOwl.png


[Violation] 'DOMContentLoaded' handler took 260ms
[Violation] Forced reflow while executing JavaScript took 69ms
merged-haxe-deps-c75527b0.js:231 [Violation] Added non-passive event listener to a scroll-blocking 'wheel' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
create @ merged-haxe-deps-c75527b0.js:231
create @ merged-haxe-deps-c75527b0.js:452
create @ merged-haxe-deps-c75527b0.js:927
createWindow @ merged-haxe-deps-c75527b0.js:42
create @ merged-haxe-deps-c75527b0.js:791
bc.create @ merged-haxe-deps-c75527b0.js:45
qa.embed.D.lime.embed @ merged-haxe-deps-c75527b0.js:430
(anonymous) @ index?ref=:349
merged-haxe-deps-c75527b0.js:231 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
create @ merged-haxe-deps-c75527b0.js:231
create @ merged-haxe-deps-c75527b0.js:452
create @ merged-haxe-deps-c75527b0.js:927
createWindow @ merged-haxe-deps-c75527b0.js:42
create @ merged-haxe-deps-c75527b0.js:791
bc.create @ merged-haxe-deps-c75527b0.js:45
qa.embed.D.lime.embed @ merged-haxe-deps-c75527b0.js:430
(anonymous) @ index?ref=:349
merged-haxe-deps-c75527b0.js:231 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
create @ merged-haxe-deps-c75527b0.js:231
create @ merged-haxe-deps-c75527b0.js:452
create @ merged-haxe-deps-c75527b0.js:927
createWindow @ merged-haxe-deps-c75527b0.js:42
create @ merged-haxe-deps-c75527b0.js:791
bc.create @ merged-haxe-deps-c75527b0.js:45
qa.embed.D.lime.embed @ merged-haxe-deps-c75527b0.js:430
(anonymous) @ index?ref=:349
index?ref=:343 [Violation] 'load' handler took 376ms
merged-game-b4a922c3.js:26 Local storage available: true
merged-game-b4a922c3.js:27 LocalStorage has 280717 chars in 187 entries
index?ref=:702 [Violation] 'load' handler took 152ms
index?ref=:1 Cross-origin plugin content from must have a visible size larger than 400 x 300 pixels, or it will be blocked. Invisible content is always blocked.
merged-3rd-party-1a4348e5.js:93 [Violation] 'setTimeout' handler took 50ms
merged-haxe-deps-c75527b0.js:136 Big
merged-haxe-deps-c75527b0.js:114 Translations file loaded
merged-haxe-deps-c75527b0.js:16 [Violation] 'requestAnimationFrame' handler took 112ms
ForgeHX-f722ded5.js:sourcemap:24155 [Violation] Added non-passive event listener to a scroll-blocking 'wheel' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
create @ ForgeHX-f722ded5.js:sourcemap:24155
create @ ForgeHX-f722ded5.js:sourcemap:24932
create @ ForgeHX-f722ded5.js:sourcemap:25921
createWindow @ ForgeHX-f722ded5.js:sourcemap:158
create @ ForgeHX-f722ded5.js:sourcemap:25716
BX.create @ ForgeHX-f722ded5.js:sourcemap:162
nd.embed.ib.lime.embed @ ForgeHX-f722ded5.js:sourcemap:24847
loadGame @ index?ref=:353
ForgeHX-f722ded5.js:sourcemap:24156 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
create @ ForgeHX-f722ded5.js:sourcemap:24156
create @ ForgeHX-f722ded5.js:sourcemap:24932
create @ ForgeHX-f722ded5.js:sourcemap:25921
createWindow @ ForgeHX-f722ded5.js:sourcemap:158
create @ ForgeHX-f722ded5.js:sourcemap:25716
BX.create @ ForgeHX-f722ded5.js:sourcemap:162
nd.embed.ib.lime.embed @ ForgeHX-f722ded5.js:sourcemap:24847
loadGame @ index?ref=:353
ForgeHX-f722ded5.js:sourcemap:24156 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
create @ ForgeHX-f722ded5.js:sourcemap:24156
create @ ForgeHX-f722ded5.js:sourcemap:24932
create @ ForgeHX-f722ded5.js:sourcemap:25921
createWindow @ ForgeHX-f722ded5.js:sourcemap:158
create @ ForgeHX-f722ded5.js:sourcemap:25716
BX.create @ ForgeHX-f722ded5.js:sourcemap:162
nd.embed.ib.lime.embed @ ForgeHX-f722ded5.js:sourcemap:24847
loadGame @ index?ref=:353
merged-game-b4a922c3.js:19 [Deprecation] GainNode.gain.value setter smoothing is deprecated and will be removed in M64, around January 2018. Please use setTargetAtTime() instead if smoothing is needed. See https://www.chromestatus.com/features/5287995770929152 for more details.
r @ merged-game-b4a922c3.js:19
init @ merged-game-b4a922c3.js:11
(anonymous) @ merged-game-b4a922c3.js:19
t @ merged-game-b4a922c3.js:11
n @ merged-game-b4a922c3.js:23
t.registerSoundAtlas @ merged-game-b4a922c3.js:23
t.setAtlasDefinitions @ merged-game-b4a922c3.js:25
_onSoundAtlasLoaded @ ForgeHX-f722ded5.js:11248
e @ ForgeHX-f722ded5.js:14
_onDataLoaded @ ForgeHX-f722ded5.js:7285
e @ ForgeHX-f722ded5.js:14
__dispatchEvent @ ForgeHX-f722ded5.js:20
dispatchEvent @ ForgeHX-f722ded5.js:17
_onDataLoaded @ ForgeHX-f722ded5.js:7274
load @ ForgeHX-f722ded5.js:7274
_load @ ForgeHX-f722ded5.js:7291
load @ ForgeHX-f722ded5.js:7282
execute @ ForgeHX-f722ded5.js:11248
execute @ ForgeHX-f722ded5.js:26254
routeEventToCommand @ ForgeHX-f722ded5.js:26257
k @ ForgeHX-f722ded5.js:26251
__dispatchEvent @ ForgeHX-f722ded5.js:20
dispatchEvent @ ForgeHX-f722ded5.js:17
dispatch @ ForgeHX-f722ded5.js:7378
_executeNextStep @ ForgeHX-f722ded5.js:7381
_executeNextStep @ ForgeHX-f722ded5.js:11246
step @ ForgeHX-f722ded5.js:7380
postConstruct @ ForgeHX-f722ded5.js:7380
applyInjection @ ForgeHX-f722ded5.js:26340
applyInjectionPoints @ ForgeHX-f722ded5.js:26229
instantiateUnmapped @ ForgeHX-f722ded5.js:26224
instantiate @ ForgeHX-f722ded5.js:26234
execute @ ForgeHX-f722ded5.js:11240
execute @ ForgeHX-f722ded5.js:26254
routeEventToCommand @ ForgeHX-f722ded5.js:26257
k @ ForgeHX-f722ded5.js:26251
__dispatchEvent @ ForgeHX-f722ded5.js:20
dispatchEvent @ ForgeHX-f722ded5.js:17
dispatchEvent @ ForgeHX-f722ded5.js:7529
startup @ ForgeHX-f722ded5.js:7530
startup @ ForgeHX-f722ded5.js:10932
checkAutoStartup @ ForgeHX-f722ded5.js:7534
OA @ ForgeHX-f722ded5.js:7530
ak @ ForgeHX-f722ded5.js:7537
hha @ ForgeHX-f722ded5.js:10931
_bootstrap @ ForgeHX-f722ded5.js:212
_onContextCreated @ ForgeHX-f722ded5.js:212
e @ ForgeHX-f722ded5.js:14
__dispatchEvent @ ForgeHX-f722ded5.js:20
dispatchEvent @ ForgeHX-f722ded5.js:17
__dispatchCreate @ ForgeHX-f722ded5.js:25913
e @ ForgeHX-f722ded5.js:14
e.run @ ForgeHX-f722ded5.js:23920
(anonymous) @ ForgeHX-f722ded5.js:23920
setInterval (async)
Qp @ ForgeHX-f722ded5.js:23920
Qp.delay @ ForgeHX-f722ded5.js:23920
requestContext3D @ ForgeHX-f722ded5.js:25910
_checkVRAMAndInitStarling @ ForgeHX-f722ded5.js:210
init @ ForgeHX-f722ded5.js:208
start @ ForgeHX-f722ded5.js:129
zX @ ForgeHX-f722ded5.js:128
Dra @ ForgeHX-f722ded5.js:163
BX.start @ ForgeHX-f722ded5.js:162
(anonymous) @ ForgeHX-f722ded5.js:162
dispatch @ ForgeHX-f722ded5.js:24218
start @ ForgeHX-f722ded5.js:24189
display_onUnload @ ForgeHX-f722ded5.js:25832
e @ ForgeHX-f722ded5.js:14
__dispatchEvent @ ForgeHX-f722ded5.js:20
__dispatchEvent @ ForgeHX-f722ded5.js:43
__dispatchWithCapture @ ForgeHX-f722ded5.js:45
dispatchEvent @ ForgeHX-f722ded5.js:41
onLoaded @ ForgeHX-f722ded5.js:25835
this_onComplete @ ForgeHX-f722ded5.js:25836
e @ ForgeHX-f722ded5.js:14
__dispatchEvent @ ForgeHX-f722ded5.js:20
__dispatchEvent @ ForgeHX-f722ded5.js:43
__dispatchWithCapture @ ForgeHX-f722ded5.js:45
dispatchEvent @ ForgeHX-f722ded5.js:41
start @ ForgeHX-f722ded5.js:25831
updateProgress @ ForgeHX-f722ded5.js:24193
load @ ForgeHX-f722ded5.js:24188
BX.create @ ForgeHX-f722ded5.js:162
nd.embed.ib.lime.embed @ ForgeHX-f722ded5.js:24847
loadGame @ index?ref=:353
ForgeHX-f722ded5.js:23920 [Violation] 'setInterval' handler took 562ms
ForgeHX-f722ded5.js:24136 [Violation] 'load' handler took 264ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 71ms
ForgeHX-f722ded5.js:24143 [Violation] 'readystatechange' handler took 1458ms
ForgeHX-f722ded5.js:24143 [Violation] 'readystatechange' handler took 7031ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 1228ms
ForgeHX-f722ded5.js:14 [Violation] 'message' handler took 32228ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 188ms
ForgeHX-f722ded5.js:14 [Violation] 'setInterval' handler took 88ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 78ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 118ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 106ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 51ms
ForgeHX-f722ded5.js:24136 [Violation] 'load' handler took 327ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 90ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 109ms
ForgeHX-f722ded5.js:24142 [Violation] 'readystatechange' handler took 366ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 88ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 74ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 62ms
ForgeHX-f722ded5.js:24136 [Violation] 'load' handler took 438ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 148ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 61ms
ForgeHX-f722ded5.js:24136 [Violation] 'load' handler took 553ms
ForgeHX-f722ded5.js:24136 [Violation] 'load' handler took 165ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 136ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 85ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 66ms
ForgeHX-f722ded5.js:24142 [Violation] 'readystatechange' handler took 173ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 74ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 129ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 73ms
2ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 77ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 62ms
ForgeHX-f722ded5.js:24142 [Violation] 'readystatechange' handler took 418ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 202ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 58ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 50ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 55ms
ForgeHX-f722ded5.js:24136 [Violation] 'load' handler took 338ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 166ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 57ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 79ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 50ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 58ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 52ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 53ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 61ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 78ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 69ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 66ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 69ms
ForgeHX-f722ded5.js:14 [Violation] 'resize' handler took 287ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 169ms
ForgeHX-f722ded5.js:14 [Violation] 'resize' handler took 160ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 165ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 193ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 90ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 162ms
ForgeHX-f722ded5.js:14 [Violation] 'resize' handler took 176ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 105ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 53ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 57ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 64ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 55ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 53ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 55ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 51ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 53ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 52ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 50ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 60ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 51ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 50ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 51ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 99ms
ForgeHX-f722ded5.js:14 [Violation] 'resize' handler took 336ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 108ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 87ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 61ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 55ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 72ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 80ms
ForgeHX-f722ded5.js:14 [Violation] 'setInterval' handler took 121ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 1722ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 1694ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 200ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 58ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 60ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 402ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 60ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 71ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 58ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 447ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 66ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 524ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 473ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 426ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 435ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 52ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 66ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 549ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 450ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 69ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 71ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 454ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 51ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 506ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 418ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 424ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 423ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 51ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 479ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 82ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 59ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 566ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 77ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 50ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 55ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 465ms
2ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 58ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 99ms
ForgeHX-f722ded5.js:14 [Violation] 'setInterval' handler took 93ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 576ms
2ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 63ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 55ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 51ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 52ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 52ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 59ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 84ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 80ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 62ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 58ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 53ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 60ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 86ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 61ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 52ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 81ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 70ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 57ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 52ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 62ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 59ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 69ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 53ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 77ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 62ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 90ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 102ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 57ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 76ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 60ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 64ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 73ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 55ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 67ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 52ms
2ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 55ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 53ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 69ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 59ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 60ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 58ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 54ms
3ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 53ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 68ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 60ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 66ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 52ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 59ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 52ms
ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 67ms
2ForgeHX-f722ded5.js:14 [Violation] 'requestAnimationFrame' handler took 56ms
 
Prom d Exolandia

Prom d Exolandia

Baronet
Bryfft said:
This will happen as soon as the development team is happy with how fast and smooth the game runs on Firefox :).
Click to expand...
I use HTML5 on Firefox only changing user agent to bypass your control and it work fine (not worth than with Chrome), i don't understand why you don't open it to tests
 

Vimesfan

Merchant
Baking Sudoku Master
Thank you for trialing HTML5 and for working on improved solutions. I do have a concern, however, that I haven't seen mentioned yet. If I missed someone else's post on it, I'm sorry for repeating it.

When I log onto beta, the lag has always been greater than it is on the US server, quite a bit more, except for when I'm doing GvG on one of the worlds on the US server at recalc time.

I've enabled HTML5 on beta when I log in. There still is lag. I can't honestly tell if it is because of the change to HTML5 or not. So it is hard for me to offer any feedback on whether or not it improves things.
 
NormaJeane

NormaJeane

Viceroy
Prom d Exolandia said:
I use HTML5 on Firefox only changing user agent to bypass your control and it work fine (not worth than with Chrome), i don't understand why you don't open it to tests
Click to expand...

I already answered this here ;)
However, to make things more clear to you:
When you change the Firefox user agent to either Chrome or Opera for trying out FoE-HTML5 you are in fact not using (native) Firefox ...
 
Prom d Exolandia

Prom d Exolandia

Baronet
Not at all, firefox is the same, only the information of user agent is changed on response set by it. For the server client is chrome then he do not switch to flash but firefox engine can only do firefox html5 implementation.
 

DeletedUser16

Guest
Nobody will block you from faking the useragent info :). As such, if you want you can force the HTML5 version to run on virtually any browser already now.

The main reason why browsers are enabled in steps is because we want to be satisfied with the performance of the game with each specific browser on a low-end computer. We do not think that asking you to test something that we ourselves are not OK with makes too much sense :).
 
Prom d Exolandia

Prom d Exolandia

Baronet
Of course but many players do not want to use Chrome (https://www.wired.com/2016/06/latest-ad-tracking-move-google-gets-opt-right/).
Firefox is the third browser used in the world (after Chrome 50% and Safari 20%), all HTML5 are not implemented but all important one are :
https://html5test.com/results/desktop.html
On my computer FOE in HTML5 is better on Firefox than on Chrome... a lot of WebGL crash on Chrome

Firefox : 3,4/8Go RAM used / 63% CPU / 69% GPU
Chrome : 3,0/8Go RAM used / 86% CPU / 77% GPU

You might let player do their choice and do their experiment... if performances are really bad with firefox then players won't activate HTML5 option ;)
 
Last edited:
OQay

OQay

Farmer
I am using Chrome with my HTML5 beta world in one tab and the Flash live world in another. Mostly HTML5 works the same for me.

One annoying issue with HTML5 is when I drag my city around by clicking on it and dragging:
In HTML5, if my cursor leaves the city border while dragging, then when I release the mouse button and bring my mouse back over the city, it continues to move like I am still dragging it.

In Flash, when I release the mouse button and bring the mouse back over the city, it does not continue to move.
 
You must log in or register to reply here.
Top