Overlay issues on NW.js export

Problem Description

I seem to be experiencing some issues with overlay effects on animated sprites, but only when exporting projects.

I'm not sure if this goes for other platforms but so far I have only investigated further with NW.js.

So to clarify, overlay effect on animated sprite DOOES work when previewing a project with NW.js but DOES NOT work upon exporting.

I am on the latest NW.js version (v0.12.0 (Chromium 41)

Attach a Capx

https://dl.dropboxusercontent.com/u/2053779/animated_overlay_nwjs.capx

Description of Capx

This CAPX file has got one animated sprite with overlay effect and one non-animated sprite with overlay effect for comparison.

Steps to Reproduce Bug

• Step 1: See if everything works in NW.js preview
• Step 2: Export to NW.js
• Step 3 See if it still works

Observed Result

The animated sprite with overlay effect flips out.

Expected Result

The expected result is for the animated sprite with overlay effect to work properly.

Affected Browsers

• NW.JS: Yup!
• Chrome/Firefox/IE: Haven't looked at this, sorry! Operating System and Service Pack Windows 8.1 Pro Construct 2 Version ID 204.2 (64.bit)

Has anyone had a look at this or tried the capx? I'm not sure if I'm the only one experiencing this issue right now.

I can reproduce, and it happens in browsers too: http://www.scirra.com/labs/bugs/overlaytest/

(Please always test everywhere you can, this is important information for bug reports)

This could be tricky to fix, I guess it relates to how the spritesheeting on exports interacts with background-blending WebGL shaders. I'll investigate, but may postpone this to the next beta cycle (I want to have a stable update out soon).

I can reproduce, and it happens in browsers too: http://www.scirra.com/labs/bugs/overlaytest/

(Please always test everywhere you can, this is important information for bug reports)

This could be tricky to fix, I guess it relates to how the spritesheeting on exports interacts with background-blending WebGL shaders. I'll investigate, but may postpone this to the next beta cycle (I want to have a stable update out soon).

Thanks Ashley! No worries, take your time.

Hey Ashley , did you investigate this matter further? The new beta (r207) is out and, unfortunately, I can still reproduce this bug.

This should be fixed in the next beta.

This should be fixed in the next beta.

I can confirm this. Greatly appreciated, thank you!