Flashplayer based game extremely laggy

Hello Jeromie

I dont know, did Nexters contact you? If not, you wrote: " the content provider ist the best position to debug the issue..."
So is this more for the developers, or did you mean something what we can check in chrome canary?
I also installed lighthouse, but didnt try it yet

Thank you

Hi Jeromie

well Nexters promised us, they will contact you:

And the Chrome Canary has the same graphical speed as the firefox 32 bit version has, so its fast (much better then 64bit version of Firefox) but still get laggy after skipping the battles. So I would say Mozilla Firefox 32bit 5/10 and Chrome Canary 6/10.

But our case is much more why the game gets so laggy after skipping battles (finding new opponents). Sometime we skip 10 times, and after that the game is so slow, that you just cant play it, the mouse response, and everything turns into the same I showed you what happens in 64bit version.

Can it be, that something is still in loading after I loaded a new battle, like: "if I skip a battle, and all the resorces werent loaded, it still keeps loading into the next and next and next battle I skip, so the internet resources are becoming overwhelmed, or maybe their servers?" I dont know, its just really strange: after you do a lot of work in the game, and start a battle, its unplayable, you always have to restart facebook (refresh)

They also told us to turn off the antivirus to keep up the bandwith not beeing used. They always come with internet connection.

I think its some puffer/buffer thing what their server doesnt clean after skipping battle, something like that, I have no idea of programming, but "if its fast in the beginning, it cant be slow after 10-20 skipping. something is still working in the background"

- my opinion

I hope they will contact you

Thanks for your answer Jeromie

Kind regards

Adobe provides a free profiling tool called Adobe Scout, which the game developers could use to profile and identify what area of code is running slow.  This is really the best place for them to start, and will usually point them directly to the hotspot in their code that needs optimization.

In the event that the developer identifies an issue that they've determined is in the Flash Runtime itself, they're welcome to send me a private message, and I'll be more than happy to get a conversation going with the right people to see what we can do to help.

In terms of things that you can do as an end-user, you really don't want to disable sandboxing.  You're much better off switching to 64-bit Firefox, which includes a native NPAPI sandbox.  The long-standing performance and stability issues on 32-bit Firefox for Windows stem from the fact that we bolted a sandbox to the wrong side of Mozilla's plug-in interface, because they declined to make an investment in sandboxing NPAPI plugins at the time. 

For 64-bit Firefox, Mozilla invested in a native NPAPI sandbox, which allows for an optimal architecture.  This, in turn, reduces the amount of traffic sent between processes by a multiple (by eliminating redundant processes that were beyond our control).  Ultimately, this means that that we're no longer overwhelming the operating system's ability to send those messages reliably.  This is why the vast majority of Flash-related crashes and hangs on 32-bit Firefox for Windows happen.  That reduction in traffic also reduces CPU overhead incurred from sending and receiving those messages, which helps with performance.

https://www.mozilla.org/en-US/firefox/all/