Ashley's Forum Posts

  • This is a ridiculous thing to do in the first place, since it would be much better to import the PNG as a project file and load it from an actual URL rather than a data URI. Even if for non-image content you have large amounts of data, it makes far more sense to paste them in to a text file, import them as a project file, and AJAX request them. You should never be pasting large amounts of data in to events.

    However to prevent the dialogs disappearing/corrupting, I've implemented a maximum height for the next build. The dialog still won't display correctly, but you shouldn't be doing this in the first place.

  • Closing - your .capx uses third party plugins (Windows Phone, Rex Pause). As per the guidelines please don't submit bugs that use any additional plugins or behaviors. Also note it would be worth checking your graphics card driver is up to date in case that is the cause.

  • I can't reproduce any issue in my dev copy of r144. All missiles appear to move at exactly the same speed. Perhaps it's a bug we've already fixed.

    Closing for now - if you can still reproduce with r144 when it's out, re-submit it again. It would also be helpful as per the guidelines to make a minimal example, only including objects and events directly relating to the bug, and also demonstrating the bug immediately if possible.

  • Closing, exported projects must be uploaded before they run.

  • Can't reproduce on Windows 8. Works the same after export as it does in preview. Maybe this is specific to Windows 7? Could you try to find a Windows 8 machine to test on?

  • Can you narrow this down to a specific release that broke it? (i.e. was it r140, r141, r142 or r143?)

    Can you reduce the .capx to a minimal example showing only the part that is broken/has changed?

    Your attached .capx does not appear to use OR blocks. Why does your bug report mention them?

  • I can't reproduce any crash. All three of your repro steps work fine and don't crash in r143. Is it still an issue?

  • I think this is just an accidentally-by-design quirk. Layer visibility is global and persistent, and doesn't reset when re-visiting the layout. We could change that, but I think it would break a lot of projects, since I assume there is a lot of content out there that takes advantage of the fact layer visibility is global and persistent. So I think it's better not to change this. Closing as won't fix.

  • That's really weird. It looks like Windows doesn't like folder names that end with a dot. If you rename the project so it no longer ends with a trailing dot it exports OK.

    Next build just removes the trailing dot if any.

  • Closing as can't fix: this is because browsers prevent the mouseup event being sent to a different frame. The game is running in an iframe in the debugger. You have to move the mouse back then press it again.

    I can add touches to the watch - at least, when the mouse is over the debugger so it gets "stuck", I can add it to the watch then see it update again as I move the mouse back.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Closing, please only submit .capx files that show the problem by itself with nothing else included. Otherwise it's difficult to prove it's a bug and not just a mistake in your events.

  • Thanks, good find. Should be fixed in the next build.

  • Can't reproduce: <2% CPU in Chrome and <3% CPU in Firefox. The Sine behavior uses a negligable amount of CPU so I doubt it is really at fault here. Is your computer an old model or is the system busy in the background perhaps?

  • So you click a color in the list and nothing happens?

    It works fine on Windows 8, and I checked the documentation for all the functions we use and they are all supported on XP as well. Have you got Internet Explorer installed and updated? Uninstalling it can disable some Windows features which could be the cause of this.

  • You can just use forward slashes. Windows understands them as well, even when mixed with backslashes.