It has intermediate jolts but overall has only been prolonged by 10 minutes. I have made it to 78minutes online before it got buggy like before.

eh the effect i pointed out before hasnt been fixed yet ;[ guess its not related to the timeout stuff people suggested before

Tile Layers still aren't rendering correctly at all (or at least the level I attached).

Note: The V5 image was displaying random garbage tiles till the window was resized then it worked fine.

Alt 8+9 so awesome lol, shame it seems to blur everything but my head and shield though. Cursor doesn't change back from the <-> to the regular icon when I move my mouse from the playerlist to the main window. This also happens with the cursor on the sides of the main window.

Also yeah:

formattimestring() is crashing the Windows client when providing non-standard % codes.

Can you explain a little bit more or prepare something simple for me test it?

Explain?

What's the level name where I can easily test it?

Ok there seems to be some massive slowdown for most people, will do a new version very soon.

zodiac_icedungeon-test.nw on Zodiac.

I believe Crono was referring to gani jittering effect. A good example of it was on Classic iPhone with the slippery snow ground, when the player is sliding the head seems to move first and then the rest of the sprites/body follows.

I will check the tile layers.
BTW: please someone on Zodiac remove that client.bufftime_expbuff=3349.300830075 stuff, it's updating that 20 times each second, which is causing 600 bytes being sent by each player each second, probably without real purpose (can't use some simple client-side var?).

Update: the problem with the tile layers had to do with the detection for fully black or transparent tiles (for optimiztations) which wasn't correct for RGBA images so tilesets with RGBA images were ok but not palettized ones. It will be fine with the next version which will be up in a few hours.

This is trying to use the docking playerlist. The only thing I can think of that is causing this is the second monitor, but Skyld also has a second monitor and he said it works for him.

That's been dealt with (once every 5 seconds instead of 0.05), and it does have an important purpose ultimately it comes down to so people don't complain when they reconnect and their Gelat Purchased EXP Potion buff is gone.

Also works fine on Win7 64-bit with dual monitors.

Do you have other programs running which try to dock at the same time? The docking mechanism in Windows is made by Microsoft which means it's not exactly intelligent and programs need to hack everything itself to support it correctly, although Graal is basicly only doing the basic things to not interfere with other programs too much. It should be the same as in v5.

Update: ok can reproduce the problem on Windows7, will try to fix it.

Update: provided a new version to Skyld, it should go live tomorrow:
- fixed playerlist docking on the right side of the screen
- fixed the optimizations for tile layers
- fixed a slowdown problem with the networking
- doesn't crash on strftime anymore

There's not really anything you can prepare I'm afraid. It is the same timeout bug as in the previous release, except it starts after having the client open for around 78 minutes instead of the previous 68 minutes.

As for the intermediate occurrence, it is easy to notice it with things such as musical instruments or anything that you can forcefully hold a sound down with so you can use your ears to hear the breaks in the timeout.


On the note of sounds though, I have noticed that every now and then there is like a digital "Pop" or digital "Crack" sound when there is a bit of noise coming from all directions. Easy way to reproduce this I guess is standing in the middle of Unstick Me on Era where people play a lot of instruments and randomly shoot in No PK for no reason.

The timeout becomes really obvious on Zodiac, when all the spell/casting effects start appearing choppy as well as movement.

You can use this simple moving block script I posted here on a server of your choice, let your client idle for the 78 minutes, and debug away.

There is also a timer showing the time from staring the client which will flash yellow/red once the glitch takes place on Era. Top left.