If we want a STRONG margin of safety (we don’t know all the circumstances in which our game will run), we may consider 3

Note: the Chrome FPS Meter does not measure performance of a game that runs inside an iframe tag. If the rest of the page is static, the tool tells that no frame was dropped; doesn’t matter how bad can be the performance of the iframed game.

The current version of the Chrome FPS Meter features a very important advance. It tells how many frames are dropped (not printed on screen). And shows the percentage of the recent printed frames over all recent produced frames. The maximum value it shows is 99% even when all the frames are printed.

http://go.negronicocktailbar.com/jze/Video-Norway-Denmark-v-en-gb-1mqb30122020-4.php

http://go.negronicocktailbar.com/jze/videos-Norway-Denmark-v-en-gb-1vgb30122020-19.php

http://news7.totssants.com/izt/v-ideos-Maccabi-Tel-Aviv-Alba-Berlin-v-en-gb-egt-.php

http://news7.totssants.com/izt/videos-Maccabi-Tel-Aviv-Alba-Berlin-v-en-gb-xrm-.php

http://go.negronicocktailbar.com/jze/Video-norge-v-danmark-v-da-da-1vgn-21.php

http://news7.totssants.com/izt/Video-Maccabi-Tel-Aviv-Alba-Berlin-v-en-gb-wka-.php

http://news7.totssants.com/izt/videos-zenit-st.-petersburg-v-panathinaikos-bc-v-ru-ru-1yrj-10.php

http://news7.totssants.com/izt/video-zenit-st.-petersburg-v-panathinaikos-bc-v-ru-ru-1rme-9.php

http://news7.totssants.com/izt/video-zenit-st.-petersburg-v-panathinaikos-bc-v-ru-ru-1mtz-16.php

http://news7.totssants.com/izt/Video-zenit-st.-petersburg-v-panathinaikos-bc-v-ru-ru-1tgy-13.php

http://news7.totssants.com/izt/video-Zenit-St.-Petersburg-Panathinaikos-v-gr-gr-1ihz-15.php

http://news7.totssants.com/izt/v-ideos-Zenit-St.-Petersburg-Panathinaikos-v-gr-gr-1ens-10.php

http://news7.totssants.com/izt/video-Zenit-St.-Petersburg-Panathinaikos-v-gr-gr-1wjc-17.php

http://news7.totssants.com/izt/v-ideos-Zenit-St.-Petersburg-Panathinaikos-v-gr-gr-1zdl-5.php

http://news7.totssants.com/izt/v-ideos-Zenit-St.-Petersburg-Panathinaikos-BC-v-en-gb-1van-.php

http://news7.totssants.com/izt/videos-Zenit-St.-Petersburg-Panathinaikos-BC-v-en-gb-1sij-24.php

http://go.negronicocktailbar.com/jze/videos-norge-v-danmark-v-da-da-1loh-20.php

http://news7.totssants.com/izt/video-Zenit-St.-Petersburg-Panathinaikos-BC-v-en-gb-1buu-26.php

http://news7.totssants.com/izt/v-ideos-norge-v-danmark-v-no-no-1hgb-17.php

http://news7.totssants.com/izt/Video-norge-v-danmark-v-no-no-1jor-4.php

to work on the copy of the original data frame or the original data frame (there’s no difference) but the important thing is that you will be able to go back to one of those original files if you make an irreparable mistake and only notice way down the line when it’s too late or too confusing to “undo cell operation”.

The terrain list is the large list, containing 10 thousand (100x100) squareObjects. Each squareObject tells everything about the square of the terrain that it represents, including the creature and the missiles that may be over it.

The creatures list and the missiles list are small. And are used only for efficiency. Every loop, creatures and missiles must be updated. It is more efficient iterate over the 2 small lists than iterate over a 10 thousand object list.

My guess: with our tests written in JavaScript we test the performance INSIDE the V8 runtime. But there is more job outside the V8 runtime, like interact with the video graphics card. This can only be measured with the Chrome PFS Meter. It seems the video card is unable to process everything it receives.

We can see that the average time needed to execute the painting (which is the bottleneck) is 1.7 ms. Much lower than the strict limit of 3 ms that we chose. The worst case was 2.3 ms, also bellow the 3 ms! Excellent!!!

We could imagine an alternative, cheap repainting system for when the avatar is still. But its a bad idea for 2 reasons. First, it does not help when avatar walks (the game must be performant 100% of the time). Second, this system would be very hard to implement due to the intricated overlapping of the volume elements (creatures, walls, speaks, missiles, trees, etc..), mainly the moving ones, each with its own shape and size.

So why dropping exactly 50%? Another guess: Chrome realizes it can’t keep running at 60 FPS. So instead of trying it, failing almost all the time, Chrome decides to go directly to 30 FPS, providing a smoother experience.

When the avatar walks, his whole environment must be displaced on canvas (since he is always painted in center of canvas). Therefore we must repaint the whole canvas every loop. This is an expensive operation.

The image at the beginning of the article is a good example of the type of game I used as inspiration for the tests. A 2.5D adventure like game, third person view, which the player’s avatar is always positioned at the center of the canvas. The game environment is a labyrinth of 100x100 squares with lakes, creatures, and many trees and many walls.

So we believe in our Javascript code or in the Chrome FPS Meter? We can believe both. And more than believe them, believe in the experience we have playing the game: is it smooth or not?

The weight of game logic, even with the AI of creatures working, is negligible. Running the game without painting takes 0.1 ms or less. Therefore, we will no longer discuss the logic of the game in this article.

We only need to check what the Chrome FPS Meter says. Oh no! It says that 50% of the frames are being dropped!!! It is like paints one frame and drops the next, paints one frame and drops the next… It is bad!!! And we are not sure if the frame dropping is so regular or it is like paints 1, drops 4, paints 2, drops 1, paints 3, drops 1…

Why Chrome? Because it is by far the fastest (at the time of writing this article). Therefore, if the code doesn’t work in Chrome, we know it is not going to work anywhere else.