I also made just very simple box falling experiment and it does the same thing.

Actually I forgot I am using version 161 but it should't open it then if you are using later version. If that even is the issue.

Wow that took longer than I thought.

CAPX

Also note that player collision polygon is 1 pixel inward.

Link to .capx file (required! If link is blocked remove the http and www parts):

Zip containing CAPX and exe

dl.dropboxusercontent.com/u/104893773/just%20a%20box/just%20a%20box.zip

Steps to reproduce:

1. Run exe

2. Wait it to freeze for few seconds

3. If not.. maybe something to do with my specs

Observed result:

Freezes randomly for few seconds when running

Expected result:

No freezing

Browsers affected:

Chrome: no (not relevant)

Firefox: no (not relevant)

Internet Explorer: not tested

Operating system & service pack:

Windows 7 Ultimate SP1

Construct 2 version:

161 (64-bit)

Also if it helps here are some additional specs

Intel Core i5 3570K (Ivy Bridge)

GeForce GTX 560 Ti

8 GB RAM

Ok thanks I have i5-3570K but I have GeForce. Even very basic Node-webkit games I export does this. Also some games other people made does this or at least VIKTOR and not sure if Insanity's Blade did that before but now I played until that stage 2 boss and didn't notice anything. Well maybe I could make bug report.

Yes that is the same guy, but I mostly ment he is very hard <img src="smileys/smiley1.gif" border="0" align="middle" /> could't make any damage and he killed me with one laser hit.

I also made simple example where there is just a box with physics behavior falling down and it's then destoyed and spawns a new one. This is also doing the same thing.

Would like to know if others are having these issues.

First is the freezing issue. Like on

at 1:43. That is quite short but it can be longer and usually is about 4-6 sec.

Second issue is with some Blend modes. If you download THIS example and you try it in browser (tested Firefox and Chrome) it works as intended, but on Node-webkit it doesn't work if WebGL is enabled just shows black. Should be that blue background with some white lines.

Im using C2 version 168 64-bit

Could these be bugs or something else.

For anyone who's suffering from NWK freezes after exporting, try reverting back to 0.8.6, as it is working for us.

LINK:

https://github.com/rogerwang/node-webkit

Under downloads, Prebuilt binaries (v0.8.6 - Apr 18, 2014): win32

Remove your game.exe, extract the file to your node-webkit exported project (replace remaining files ), and that's it! You can rename the exe file.

I just noticed you don't seem to have any freezing problems with node-webkit. My game freezes every now and then for few seconds, so I was thinking are you using native node-webkit or the old third party plugin.

By the way stage 2 boss is insane <img src="smileys/smiley1.gif" border="0" align="middle" /> I mean that cave boss.

Sorry my explanation was't the best. I can't open your images but I took one from what I mean.

Something like this

<img src="https://dl.dropboxusercontent.com/u/104893773/C2%20examples/one%20direction%20shoot.png" border="0" />

Made an example. You could improve it further.

Web Game

CAPX

There is two set animation action on when hit. Maybe you remove set animation to normal and instead make new condition when animation pain finished set animation to normal.

Not sure but it seems changing animations on physics objects may cause some odd stuff to happen. Is collision polygon same on both animations.

Well one way would be to make variable "shootDirection" for the player and when pressin down set 90 etc. And then use or condition.

when right pressed

-or-

when down pressed

-or-

when left pressed

-or-

when up pressed

->

Spawn bullet to player

Set bullet angle to shootDirection