From 9c487a30017b338cda7c14c651e15b9f0f4e2ef4 Mon Sep 17 00:00:00 2001 From: Jon Atkins Date: Fri, 26 Jun 2015 02:13:53 +0100 Subject: [PATCH] and yet another update to the fallback defaults.... maybe Niantic should have load-tested the best values in dev before releasing into production, rather than repeatedly changing it so many times? or at least made it completely controlled by server-side code, so no client updates needed for every experimental change... --- code/map_data_calc_tools.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/map_data_calc_tools.js b/code/map_data_calc_tools.js index 40cf7162..560a9fb9 100755 --- a/code/map_data_calc_tools.js +++ b/code/map_data_calc_tools.js @@ -12,7 +12,7 @@ window.setupDataTileParams = function() { // default values - used to fall back to if we can't detect those used in stock intel - var DEFAULT_ZOOM_TO_TILES_PER_EDGE = [1,1,1,40,40,80,80,320,1000,2000,2000,4000,8000,16000,16000,32000]; + var DEFAULT_ZOOM_TO_TILES_PER_EDGE = [256,256,256,256,512,512,512,2048,2048,4096,4096,6500,6500,6500,18000,18000,36000]; var DEFAULT_ZOOM_TO_LEVEL = [8,8,8,8,7,7,7,6,6,5,4,4,3,2,2,1,1]; // stock intel doesn't have this array (they use a switch statement instead), but this is far neater