Ashley's Forum Posts

  • Ah, I think the spritesheeting on export changes the way the effect works. Should be fixed in the next build.

  • I can reproduce on an iPad Air 2 running iOS 9.3, but I think the signs are pointing to a mobile Safari or graphics driver bug. I also cannot reproduce on Chrome, Firefox, Edge (on Windows 10) or Chrome for Android, or Safari 9 on a Macbook. This suggests the Construct 2 code is correct (since it works across a broad array of browser engines, OSs and graphics hardware) and that it's possibly not a Safari bug (since it works on OS X). It could possibly be a Safari bug that manifests in the mobile variant only, or a graphics driver bug (I think iOS devices same the share similar graphics hardware/drivers, and while iOS is generally good on driver quality, our past experience is all drivers have buggy behavior at some point).

    Your simpler example uses a third-party effect, which we cannot accept in bug reports. (There's a built-in replace color effect anyway?) I think your theory about transparency turning black is probably correct, but to investigate further can you provide the simpler demo with no third-party addons?

  • This is actually a missing feature in the engine. Collision testing between layers with different scale/rotation is a bit of an exotic feature, and it was never implemented for tilemaps!

    I'm not sure how much work this would be to address right now. I'll leave this report open as a TODO.

  • I think this is a beta-only debug check and it's only the check that is wrong - it really updated OK If you press "Ignore" it appears to continue to save OK.

    I've fixed the next build so the message does not appear, which I think was the only problem.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Looks like this is an NW.js issue that was already reported here: https://github.com/nwjs/nw.js/issues/5093

    Closing as the issue will be followed up from there.

  • Anyway, ig75icd64.dll is the Intel graphics driver, and so the problem is with the driver and not Construct 2, so closing. You'll need to either update the graphics driver, or if it's already the latest, report the problem to Intel.

  • Closing, please see the bug report guidelines, which describe in detail why we need a .capx and what to do in this situation.

  • Closing as won't fix. I'm not sure what we can do about this: look at how shallow the angle is from the shadow casting off the top of the wall. For the shadow shape to really fill in the whole area, it would need to extrude that shadow up to infinity. Sadly computers work with the finite, so it extrudes it a very long way, but then stops. This means it fills the shadow in to a finite area with a right edge (instead of an infinite area), and sometimes that edge is visible on-screen.

    The manual entry does say you should avoid moving lights too close to casters to avoid these extreme cases. The algorithm could probably be updated, but I think it would need to be fundamentally rewritten. Realistically I don't think that will happen before C3.

  • Closing as original issue is over a year old and unlikely to be related - I think some time after the original post an XDK update fixed it. Please file a new report following all the guidelines if you still have trouble.

  • Closing, please see the bug report guidelines.

  • Construct 2 has never supported IE8. It doesn't support HTML5! I'm not sure how you're even running this.

    Also one of your screenshots includes a log message from in.js, which AFAIK is not part of Construct 2. Sometimes people have browser addons which break things, so maybe you should try disabling all your addons and see if that fixes it.

  • Closing, please see the bug report guidelines.

  • Closing, please see the bug report requirements, and only post in English.

  • Closing as .capx uses third-party plugin "Photon", which is not allowed in bug reports as per the requirements. Also this problem sounds like a corrupt .capx, in which case there is nothing we can do without the original steps to reproduce the problem in the first place.

  • Closing, please see the bug report guidelines, and only post in English otherwise we cannot help you.

    Also if you have issues specific to the Intel XDK, I'd recommend reporting them to Intel.