Post 4.0 lag, possible causes?

Yeah,my gaming has been lag city especially since 4.0 75% of the time it's virtually unplayable and all PIX responses are can you give more information about what you mean by lag?

Lag here makes it impossible to play. Hopefully they get it fixed or there is truly no point in logging on.

You sound As if you know a bit about devices, I know very little other than something is very wrong with the game.Pix is so disingenuous and condescending when I contact support. As far as Pixionics owning up forget it,they are the most dishonest and sanctimonious business I've ever dealt with.

There is no way Pixonic can do a new code rewrite,their original code writers are working on another project now BoT.

Yep, exactly my point. The code is a mess and that is why we are having lags and crashes. Our devices have limitation but Pixonic has not taken that into account as they push more content in. 

I have started to notice a lag on my device and it is pretty much common across the board. 

Be interesting to start to track the devices, models, types and so forth who are having problems and the nature of those problems. We might be able to coordinate with devices are affected and which are currently usable so we can advise this community. Forget telling Pixonic because if they cared, they would already been trying to fix it. 

Soon, and very soon, Pixonic is going to find that most of their customers are gone, not because we quit, but because our devices could not handle their code. And it will be a sudden event. 

Causes? Gross incompetence.

The textures would generally see an across the board slow down, the game plays as good as it ever did on my phone.. except it's not dropping frame rate.. it's quite litterly pausing in a jerky fashion.. not 30 fps.. 20fps... dips down to 10fps.. no it's 30, 0, 30, 0, 30, 0

It can't be just a upscaling of textures, it's more.. my guess it's CPU bound, something they messed with in the code not game assests..

Android says War Robots used a max of 504mb of ram, my phone has 2gb, 1.1gb-900mb free at any given time
My phone is not loaded down with running apps either about 800mb of ram is just the OS, with only a few 100mb's for services/apps (google keyboard, a tracker app, calling recording service, etc) I can't cut those, but if your device starts running low it'll scale back services that aren't in immediate use to free up ram.. but at least in my case it is not running out of ram.

I'd be real shocked it if wasn't a fast/tight running loop they added or they modified some dusty (but stable) code.
Like painting a mustache on Mona Lisa.. and hell no I ain't comparing this game to the Mona Lisa.



What ever it is they need to address it. mobile games need to be humble, yes there are some truely powerful devices on the market but most people aren't packing top end stuff.. They're gonna find their market shrinking but then again maybe they want people with 1,000 dollar phones to go along with their 100 dollar robots, I dunno.

I'm no tech guy but whatever the reason, it's out of hand. Game is almost unplayable. Stealth bots are useless. I'm seeing hits register well after 3 seconds (i know you can get hit, but not by target lock weapons like scourge) Emptying entire weapons only to have the bot die 5 seconds later.... just the worst.

The biggest tell about the issues being caused by badly optimised code is that most folk who experience the problem can still play FFA mode. There are half the players and so half the number of player updates to process and consequently half the number of effects etc. to render.

I started to suspect the issue was related to the complexity of the tick-rate (the frequency with which player updates are returned to the server and clients updated with the server's processed results) when the very linear map of the floating carrier map was introduced.

All matters related to tick-rate and server/client updates is referred to as 'Netcode'.

In the case of the floating carrier map (sorry, I don't know its name), pretty much the entire map full of scenery, players, weapons fire and display overlay (player tags, health bars etc.) is usually in front or behind you (ask yourself, when did you last look side-on on that map, ie. out to sea?) and that means there is likely way, way more processing required for each update or 'tick'. Coming back to FFA mode, with its anything up to half the amount of moving assets in motion the client and server should have an easier workload and consequently that is why I believe we are seeing FFA more playable than other modes.

When it comes to v4 I am of the belief that there have been more issues introduced by way perhaps of some dodgy code that hasn't been optimised properly, or perhaps the same issues of the floating carrier map found their way into the other maps as part of a code update/re-write but in any case the problems have gotten far worse with all maps being affected but still FFA still remains playable far more often than the other game modes, again I believe because of the reduced workload with less players etc. in that mode.

Even in older versions of the game a lot of people have reported experiences with apparent audio issues too such as Tempest/Punisher fire of close-by players causing stammering. Those two weapons in particular have the highest rate of fire or at least are likely to put some of the most work on CPUs, GPUs and DACs and so it is possible that such weapons add credibility to the argument that the cause could again be netcode related in that they likely create far more work for a client server both audibly and visually as well as by way of having to process the data related to every round fired.

When all is said and done, if the server-side of War Robots is at fault it should be fixable with a server-side update or perhaps just more servers to process client updates (they likely have a virtualised farm and so expansion could be done quite quickly) but if the client code is at fault the chances are that a new app version is the only likely fix and that isn't going to get to us any time soon.

Also out of all the maps... Rome is reallly bad (I know my tablet is crying uncle when Rome loads). I would say Rome is probably the most detailed map in game and it just contribute to all the other crap making everything worse.

Yes, the map is awesome..... when you start seeing bots warping around... not so awesome at all.

iOS with 150MB/second internet and no lag.

In a general sense I think your on to something. However modern CPUS the sort of number crunching that your talking about isn't going to be an issue.  In all my recent experiences a phone reboot fixes the issue for me. 

That would point to an issue that is memory (or GC) bound. Adding the calculations pushed it over the edge - it isn't the math going on it is the data being moved and where it is moving from and to. 

Because of how modern QA gets done it is unlikely that what ever testing pix is doing (automated or otherwise) is probably done on a fresh device. 

If "rebooting" and Not running anything gets performance back, and you have a higher end device it is a pix problem. I think a few of us could come together to file a bug report that is fairly reproducible at that stage. 

No offense, but you are using devices that are between 5–7 years old. So in your specific situation, I get it.


What doesn't make sense to me is that I'm playing the game on a new iPhone X, and even I often have terrible issues with the phone overheating causing frame rate drop, and overall lag issues that have plagued the game but have gotten worse. I often disconnect during games (usually when I'm on the attack for some reason). All the while I'm using strong and stable wifi connections both at work and at home. I can't play the game without the 'poor connection' symbol constantly flashing or indicating 'no connection' in the upper-right corner of the game screen. It's been a joke since 3.9, but 4.0 is a disaster.