Ashley's Forum Posts

  • And yes, that's how I currently use Find, but if you name it similar to other objects and if it has a long name you don't remember and only type a partial, you can get more results of something making it hard to see.

    You're talking about a text search. 'Find all references' is better than that. It gives you exact results regardless of the name of the object,, because it looks at the project structure rather than the names of things. It can tell the difference between Sprite2 and Sprite20 for example.

  • Please do not post the same thread multiple times, and please be patient when waiting for responses on the forum. I deleted your other thread. See the Forum & Community guidelines

  • It's a limitation of common keyboard hardware, not Construct. Look up key ghosting.

  • The 'Find all references' is specifically designed to show you a complete list of everywhere something is used in your project. One of its uses is to review all usages of something before you delete it.

  • It was moved to the Platform Info object.

  • If you save your project to the browser storage, and then you clear your browser storage, it also clears your project. Construct warns about this when you save there. You should always keep backups of all digital work you do, for this reason and many others.

  • C3 should already be preventing this. It might be selecting on the parent page though (the Newgrounds page), in which case Newgrounds would need to prevent it.

  • Mipmaps improve the rendering quality and performance when downscaling sprites smaller than their source image. It's a similar case to a far-away texture in 3D - it's just another way it appears resized smaller.

  • Citation needed! I'd argue iframes are more secure and more performant, since in the case of cross-origin iframes the browser can put the game frame in its own independent process.

  • The runtime has to control the position of the canvas in order to know how mouse/touch input event co-ordinates relate to layouts, and to correctly position form controls. That's pretty difficult if it gets placed in a div. It's also not clear why you would want to do that instead of using an iframe.

  • I'm afraid without reliable steps to reproduce the problem, it's virtually impossible to do anything. This ought to be impossible. I have no idea how it could happen.

  • The problem is cross-image bleed in spritesheets when downscaling (because the smaller mipmaps are lower resolution, and combine areas of the image in to single pixels). It's a normal result in computer graphics when using spritesheets and mipmaps, it's not specific to Construct.

    The 'Downscaling quality' property was added to Construct specifically to solve this. It pads images on spritesheets out to power-of-two offsets which largely avoids the problem. The reason it's marked as "not recommended" is because this makes it use more memory, and so you shouldn't choose it for no reason at all. (I'd noticed in the past people choosing it because they "want better quality graphics" without understanding what it does or what the trade-off is, so I added the "not recommended" label to discourage that usage.) You should only use it if you really have the problem with seams, which you do, so you should use it.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It might be a Tiled Background wrapping around the other side of the image, or it might be spritesheet bleed from an adjacent image. As ever it's hard to say for sure without seeing a project file. If it's the latter, changing the downscaling quality may help.

  • Please note issues should be filed to the bug tracker following all the guidelines, otherwise they may not have enough information to be fixed, or may be buried in the forum and forgotten.

  • NW.js and Chrome use the same browser engine - Chromium - so I'd expect performance to be identical.