I'm thinking some of the engine-specific things that makes it happen (i.e. number of other animations???) will make a bug report difficult.

It seems so weird to me that removing one animation from the object will stop the issue from reproducing altogether. I can't even begin to imagine why that would be a contributing factor.

Ashley yeah, it's weird, isn't it. It doesn't happen at all in NW preview, but there are some other subtle rendering differences there too so I'm not sure that helps you too much.

Is this enough to file a bug report to Chrome? I'd hate to go through all that again (Last time I waited on Chrome to fix a bug it took over six months)

I don't think regressing NW versions is a good permanent solution - we need to find out what's actually causing the issue and get it fixed.

Cool, glad to see you guys are finding workarounds.

fariwinds thanks for your response, I see now that you indeed have a loop of names for your recent purchases. I was put off by the fact that some of the names were the same as when I checked it a while back, but I guess that could be coincidence.

Well, nice to see this isn't as scammy as I thought. Good move reaching out like this

scaffa it's great to hear that you can reproduce it in a small project, should be a lot easier for Ashley or even Chrome to have a look at.

fariwinds It's hard to believe your product isn't a scam when you fake recent purchases. Or perhaps everyone from Saudi Arabia really is named 'Ahmed'?

The only one I use is Spriter, and it's not present in the level where this occurs.

Roccinio yup.

Point sampling fixes it, but brings a host of other problems. it's really only suitable for pixel art applications.

Pixel rounding does not fix it.

Problem Description

Basically, on export to node-webkit, some objects appear to have one-pixel lines along one of their edges. Since this only happens on export, and only happens to objects with more than one animation frame, I have a feeling it's something to do with spritesheeting.

I've been having this issue for ages in Airscape, but it's been very hard to reproduce. Finally I've managed to by copying over an object from the Airscape project, but interestingly enough it's incredibly unstable - if the object is the wrong size the issue doesn't appear. Even if you remove an animation of the object that isn't ever played the issue stops appearing.

Here's an image of the issue:

Description of Capx

Just export it as node-webkit, and you should see a 1-pixel wide line under some of the images.

Affected Browsers

• Chrome: (NO)
• FireFox: (NO)
• Internet Explorer: (NO)

Operating System and Service Pack

Win 7 64bit

Construct 2 Version ID

r168

Problem Description

This error pops up in Airscape when previewing from time to time. It seems to only happen from a fresh preview restart, and in a specific level. I wish I could provide a capx but the game is huge and complex and this is the sort of problem that doesn't reproduce in a small project.

The error pops up after death, when loading a save state. pressing 'OK' allows the game to continue, but there are weird side-effects in the game for (weirdly) a few seconds afterwards (Some events don't execute properly).

In export, the error message doesn't pop up, but the side-effects remain.

Ashley, if you'd like me to send the capx in private just let me know. If there's anything more I can do to make this easier to solve let me know as well.

Affected Browsers

• Chrome: (YES)
• FireFox: (N/A)
• Internet Explorer: (N/A)

Operating System and Service Pack

Win7 64bit

Construct 2 Version ID

r168