Construct 3 r345

You're viewing a single comment in a conversation. View all the comments
  • 5 Comments

  • Order by
  • I feel like the default for anti aliasing should take the screen size / ppi into account instead of always defaulting to 4x. I‘m using a lot of 4k sprites and the performance difference on mobile is between 5-10%, so quite noticeable. Great updates!

      • [-] [+]
      • 1
      • Ashley's avatar
      • Ashley
      • Construct Team Founder
      • 1 points
      • (3 children)

      Anisotropic filtering is different to antialiasing.

      • Sorry, I meant that. It is quite vram intensive and therefore impacts mobile performance. From my testing I saw a ~10% fps improvement on my galaxy s8 and ~5% on my iphone 11 when I disabled it.

        • It is only a default setting, you can easily change it to your needs,

          and IMO trying to get lots of 4K sprites to run on a phone from 2017 is not a default use case.

          • With phone resolutions ramping up, it‘s not uncommon. However, I have veery few actual 4k sprites but they have to be sharp enough so that the viewport resolution can be 4k and they have at least enough resolution to match the pixels. Also, on, for example a snapdragon 855 (soc from 3.5 years) I get a stable 90fps so it seems to be working out and I‘m hoping for some performance improvements with web

            gpu as well. I thought, this was going to be the new baseline, if you can still disable it I‘m not bothered at all.