Ashley's Forum Posts

  • I think Chrome has a limit on how much text can be entered in to a text input (at half a megabyte). It seems pretty reasonable, since it's unlikely anybody will sit there and type half a million characters in to a single-line text control. This is also a limitation in Chrome and not a problem with Construct 2. It's easy to work around:

    • use a textarea instead, which appears to handle the full string just fine (and scrolls so you can view it more usefully)
    • import the file as a project file and AJAX request it, which also handles the full length just fine

    If, for some reason, you really want the ability to paste a megabyte of data in to a single-line text input, you could report this to Chrome. However I'm going to close this as won't fix and would suggest one of those workarounds.

  • Closing as not a bug - most languages I've used treat % as allowing numbers to stay negative, but you can always just add in an abs() if you want different behavior.

  • This is another seam issue due to using linear sampling and the tiles blending some of the adjacent pixels from the tilemap.

    Technically it is wrong but it's pretty difficult to fix (the editor uses a different, simpler rendering algorithm to the runtime) and it doesn't affect the runtime which is where it really matters. And you can work around it by using point sampling. So closing as won't fix.

  • Yeah, HD generally means 1920x1080 or 1280x720, which are basically how many pixels are used. Both that and the bitrate affect quality - obviously HD allows for more detail than SD, but it's possible to have very high bitrate SD and very low bitrate HD such that the HD actually looks worse than SD. That's pretty uncommon though since it defeats the point of having HD in the first place, but it shows technically the resolution alone doesn't guarantee quality.

    Some TV channels broadcast in HD, but use a low bitrate so things commonly turn in to a blurry mush of pixels, but they can still call it HD. It's one of those marketing tricks

  • Can't reproduce, works just fine in Chrome here.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Closing, please see the bug report guidelines, we do not investigate issues that do not follow them for the reasons described within the guidelines.

    I also cannot see that you've provided any evidence at all that garbage collection is actually responsible for any problem you think you've identified.

  • Closing, please see the bug report requirements

  • Closing, please see the bug report guidelines.

  • Thanks for the report, should be fixed in the next build.

  • I can't reproduce this, it works here, and you say it works for you too.

    We can't fix bugs unless we can reproduce the problem. It could be something broken on just that user's system otherwise.

  • It also depends a lot on quality settings. Even if you have a 2mb JPEG (PNG is really not suitable for photography), it could just be that it was saved with very high quality, and the video is very low quality (HD refers to the resolution, not the encoding quality). So really you can get any numbers you want by adjusting quality levels.

  • When did I write that? :S I think it would have been a few years ago at least. I'm not sure it's still relevant - those tools now help ensure you have the latest driver installed, which is definitely a good thing...

  • I thought they required collision checks to happen before any instance filtering occurred in the event sheet? Most of the times I need to check collisions it's after filtering has occurred.

    Oh right, yes, that was a limitation. But then in theory your filtering has already reduced the list of candidates that need to be tested for collisions. Or are you picking large numbers of instances first? That could effectively disable the optimisation, but if it's really bad it should be possible to rearrange events to do the collision-cell enabled check first.

  • Are you sure you're calculating the bias correctly? Maybe it's thrown off by spritesheeting? I am pretty sure the mipmaps are all there.

  • As long as "downscaling quality" is not "low", Construct 2 creates mipmaps and enables tri-linear filtering (linear sampling between the nearest 2 mipmaps, linear-sampled). The "point" and "linear" project settings in this mode correspond to whether the mipmaps are linear or point sampled. So if you're accessing a mipmap from the shader... it should be there already?