No I definately did not. I always keep both construct 2 and the project running while previewing. The preview has no issues with loading assets in the level. Only ajax files and sound is affected.

I'll admit that it's a wild guess for me to target the cache as the source of the issue. However the reason I'm suspecting it, is that the game always performs as expected right after boot up, but it very rarely does if I either reload the layout, or progress to a different stage.

puu.sh/5ESLZ.png Here's a screenshot of the closest I could track down to an issue in the console. This screenshot was taken after the Ajax files had failed to reload, but the music played off as intended.

Edit: Here's a screenshot from the "console" tab. puu.sh/5ET1l.png

Nothing strange or unusual happening there.

Hope this helps.

Hi. I've been having this problem with sound not loading properly in my game previews for a long time now. At the beginning of every level, the game usually loads in a music track of avarage 2 minutes in length, and also a couple of ajax ".txt" files.

However too often the files simply refuses to load. This is however not a problem at all after I've exported to Node-webkit, but it makes for a very impractical testing process in Chrome.

Is there any ways to increase the cache size for construct 2 in chrome, or apply any other tricks to gurantee that the preview loads everything properly, even in a long playsession?

Edit: Also. This issue is also present in Node-Webkit preview!

Thanks

Thanks for the kind feedback everyone. I really appreciate it! :)

As for the difficulty, I might haven't communicated it well enough in the tutorial, but this is actually a rythm-game. If you try to follow the very predictable beat in the songs, it should become a lot easier.

Zantium: Issue number 3 is something I'm also worried about. Do you have any proposals of working around this? Isn't this simply how construct 2 works, and that I simply need to optimize my sprites better?

Thanks a ton everyone. What would I do without you guys? <3 It works now. I'll take the optimization advice into account as well.

-Tom

Thanks for the feedback. I'll check it out when I have the time. Even though I'm still concerned that it worked as intended right before the update but not after I updated to r141?

This build is running off r 139. If you want to check out the build where the problem is present, please check out the capx. File shared in my topic in the bugs section.

Strange... Have you had similar problems with other webkit games you've played? It bugs me so much that the game only performs poorly on computers I can't watch it run on personally.

Ashley Just posted a stripped down capx that reproduce the problem in the bugs section.

CJK Oh... Did it keep running that poorly after the title screens? Heard some computers completely freaks out of the game, but it's never happened to the PCs I've personally tested it on.

Alright so I've been able to strip the game down to it's bare minimum while also triggering the bug. The capx is still fairly huge, clocking in at approx. 100 mb

Link to .capx file (required!):

https//dl.dropboxusercontent.com/u/5323353/Klang%20animation%20bug.capx

Steps to reproduce:

1. Leave event 107 and 108 on at event sheet "tutorial level" , and 82 and 83 at "tutorial level 2". Turning these off makes the game runs smooth again. Proving that it's this event that's the source.

2. Boot up the game

3. Press any direction with the arrow keys

4. Witness the lagspike

Observed result:

The player performs a meele strike using the arrow keys, which triggers a set amount of animations within the environment. This makes construct 2 freeze for 1-3 seconds at a time consistently.

Expected result:

The parry and animations should feel fluent and snappy, even when spammed in every direction. This has always worked as intended until [r141], and this code hasn't been touched for months!

For a demonstration on how it really is suppose to look like. The last stable node webkit build can be found here: dl.dropboxusercontent.com/u/5323353/Klang12_8.zip

Browsers affected:

Chrome: YES

Webkit (target platform): YES

Operating system & service pack:

Windows 7 SP1

Construct 2 version:

[r141]

As previously stated in one of the other posts, I mentioned that disabling the animations made the game run fine again. The issue though is that the game has always run devilishly smooth while them being on up until r141.

I've double checked my events, and there's nothing interfering with spawning of these objects (in fact they're always static and hand placed in the environment).

I also experimented with screen size, everything from 33 % size to 200 % in chrome didn't change anything, but 25 % and lower made the game run slower. However this isn't part of the real issue.

The game still runs 100 % smooth, except for when the player meele strikes (which is the core mechanic that triggers this animations). This has always worked flawlessly, except for the r141 update...

I also update my video card drivers. No change.

The reason why I doubt it is the sound at work, is that this slowdown is present also in layouts where I haven't touched ANYTHING since the last update.

If anyone wants to test out the last stable build the link can be found here: dl.dropboxusercontent.com/u/5323353/Klang12_8.zip

Or well actually it was closer to 500mb when saved out. My bad. Still not something I can just casually share.

DrGreenThumbCAN: Thanks!