Please report any issues to the bug tracker following all the guidelines otherwise we cannot help.
It would mostly affect GPU texture read performance. I'm not sure we have a performance test that directly covers that, but the fillrate test is probably closest.
Please file any issues to GitHub following all the guidelines. Last time I tested it, it worked.
Issues only mentioned in comments won't be investigated - please use the bug tracker.
It's still complicated to do that - there are no other features that require a layout restart to apply a change at runtime, and currently restarting a layout does not reload any textures because it knows it's using the same set of textures. So there's a new codepath to write for 'reload layout and also reload all textures as if it's a different layout', which will need separate implementation and testing to a normal 'restart layout'. I'd be more persuaded this was worthwhile if you actually had benchmark numbers showing this made a significant difference for a particular game.
In general we try to avoid device-specific features, since they complicate the codebase significantly (in this case making two separate paths for handling sampling). This involves more development work and more difficult bugs (e.g. issues that only happen in a specific WebGL version which are harder to diagnose and fix). If we do this a lot then it gets even worse as you can end up with issues that only occur on devices that match three or four requirements, which turns in to a major time-sink, which we just can't afford with our limited resources. Sometimes we can justify it for a major feature, but I don't think this qualifies, it seems like it's just a nice-to-have.
This is actually very difficult to do, because in WebGL 1 samplers and textures aren't separated, so you have to specify the sampler when loading the texture.
Please file a bug following all the guidelines.
Please file an issue following all the guidelines, otherwise we cannot investigate.
Please file a bug following all the guidelines otherwise we cannot help.
If you are having trouble with payments please contact supportxwb@scirra.com.
I measured an improvement using your project. So I'm not sure why you'd see something different.
The best practices haven't changed. We would mention if they had.
Member since 21 May, 2007
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.