Ashley's Forum Posts

  • I think we can update the website to list older versions, but I don't want to roll back the version that ships with C2. The problem is that on Windows only Chrome 38 has a vsync bug. To roll back, all platforms (Windows, Mac and Linux) go backwards to Chrome 35, losing all the new features and performance improvements since then on all platforms, and we also lose Windows 64-bit support. I just think that's too big a backward step to take to work around a single bug. I think from looking at Canary the problem is already fixed (perhaps even already in v39), so I'm sure the next time node-webkit updates the Chromium version then this will be fixed as well. So I think it is better to wait for the next version than to roll back. And I'll work with Tom on getting older node-webkit downloads listed on the site so people can opt-in to rollbacks if they want.

  • Chrome 39 seems a lot better here. Check you're up to date in 'About Google Chrome' and then try again - are games working better?

    If node-webkit can update to at least v39, that could fix it there too.

  • Closing as not a bug. All four objects are set to anchor to the window top-left, and it is working correctly given those settings. (Note anchoring works by aligning the bounding box edges, not the origin, so you should not expect that it adjusts relative to the origin either.)

  • Fixed for the next build (a bug in Windows makes it thinks the 32-bit one has 0 frames... so I just made it always use at least one frame for a gif).

    Top tip: use PNG. Gif is an ancient format from the mid-90s that ought to die.

  • Added a scrollPos vec2 for the next beta.

  • Closing as works for me, can't reproduce, and no steps to reproduce provided. We cannot fix issues that happen in "random projects at random times": we have no leads to start an investigation.

    Try disabling all your browser addons in Chrome - sometimes they break C2 games.

  • I don't think this is a Construct 2 issue: as you have basically identified yourself it appears to be a problem with either Node-webkit, OS X or HFS+. Construct 2 uses unicode support throughout, as well as the standard unicode-aware Windows APIs when writing and copying files, so I'm not sure what we could change there. Sometimes people raise similar issues where misconfigured web servers use some different characterset and mangle UTF-8 filenames, then return 404 not found. I'm not sure to what extent it's Construct 2's responsibility to solve that.

    Sticking to ASCII names sucks for non-English people, but is a pragmatic way to avoid these problems. You say the zip trick works too, but note that it could increase the loading time of the application (since it must first decompress the zip).

  • You do not have permission to view this post

  • I clarified the documentation. Closing as not a bug.

  • It works fine here, and we have never heard of this problem from anyone else before either. I think it is very likely a graphics driver issue. Most display glitches in the editor are fixed by driver updates. Please check directly from your graphics card vendor for driver updates (don't rely on Windows Update).

  • This was an unintentional breaking change in r188. It's reverted with an alternative solution for the next beta.

  • Closing as not a bug. Remove the 'Solid' behavior from the player. It is not necessary, and it is by design that objects with the Platform behavior cannot move in to anything solid.

    In future please do not email any part of a bug report - just attach the .capx to the bug. As per our guidelines it should be created from scratch in a new project with the minimal events and objects necessary, and then you can make sure it doesn't use any artwork you don't want to share either. This makes it a great deal easier to deal with the bug report.

  • Closing since no reliable steps to reproduce provided since April. We cannot investigate the problem without that. Please file a new report if you can find a way to reproduce it.

  • Closing as very likely a graphics driver issue. Check your drivers are up to date. This exact problem has been reported numerous times in the past and every time was fixed by a driver update.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Closing as very likely a graphics driver issue, please check your drivers are up to date.