Ashley's Forum Posts

  • As far as I can tell dotscreen is working correctly. Because it is written to take in to account pixelWidth and pixelHeight, it means the effect produces a dot in a certain pixel distance. Therefore increasing the window size will show more dots. Then you have a letterbox scale which resizes them to both be the same final size, which is possibly confusing. If dotscreen were to look the same regardless of the window size, it should not use pixelWidth and pixelHeight and just base calculations off the texture co-ordinates, but we decided to do it the pixel-based way.

    Your effect simply looks like it mixes up texture co-ordinates and screen co-ordinates. It looks like you correctly convert the mouse to texture co-ordinates by dividing it by the resolution, but this line appears to be wrong:

    vec2 uv = (gl_FragCoord.xy / iResolution.xy);

    The fragment co-ordinates are already in texture co-ordinates, so dividing again by the resolution does not make sense.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Can't reproduce on Windows 8.1 x64 with Word 2010. Perhaps they changed how the file saving works? I can't think why Office saving would get in the way of C2 saving, since they shouldn't touch each other's files, unless Office is trying to lock the entire folder - but then it would affect all sorts of applications, not just C2...

  • Oops, thanks - should be fixed in the next build.

  • I guess some systems are configured differently. I know that on Linux you always have to enable execute permission on the executable file to allow it to run at all, perhaps some Mac systems are configured to require the same. So I suppose this can be put down to a permissions issue? I think C2 and node-webkit are working correctly, but you might need to create an installer or do some config to allow the system to run it.

  • Construct 2 retrieves the gamma value in a standards-compliant way, so it simply appears Windows Phone 8 does not support the standard. I'm not sure what we can do about this, but I think the Windows Phone 8.1 update will support it. You could also try publishing to WP8 using PhoneGap, which I think implements a workaround to enable inclinometer input.

  • I think I found a workaround for this anyway, it's when the driver does not support power-of-two textures. Should be fixed from next build even without NPOT support.

  • Link is now 404, please put it back up if you need this investigating!

  • Ah, thanks for the find - should be fixed in the next build.

  • Closing, please follow the bug report guidelines.

  • Closing, please follow the guidelines and attach a .capx.

  • It looks like the old version, since they just launched a newer update. The version there is about 7 years old now. The new version has an upgrade fee, so it looks like you'd still have to pay again after buying the bundle to get the latest version.

  • Can't reproduce, looks fine here. Sounds very much like a graphics driver issue, try making sure they're up to date.

  • You do not have permission to view this post

  • It would be difficult mainly because TMX files use a bunch of different internal formats (like zlib and gzip, which we'd need to find and import JS libraries to support) and is XML-based (so no CocoonJS support). It should work better if you stick to the JSON format that the Tilemap object uses itself. Perhaps an option could be added to Tiled to export in this format directly.

  • It should work fine if you rename index.html to something else, but the images and media folders might conflict, so just put each game in its own folder.