Jump to content
You must now use your email address to sign in [click for more info] ×

thiagodebastos

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by thiagodebastos

  1. Can I just mention that adding bevel emboss effect does per-pixel lighting, shadows are generated per-pixel, glow is per-pixel, noise is per-pixel, etc - so you're doing many things for each pixel which require non-trivial algorithms. Most of these algorithms also involve a convolution stage that requires sampling input from a large number of surrounding pixels for each destination pixel so when you multiply all of this up to being how large your image is on the screen and how large the effects are on the object then that is the reason your cpu is busy - it simply takes time to work out the answers. There are shortcuts but these result in inferior results so we don't use them.

     

    Other programs choose to cache the results so you can use the program smoothly after an initial lumpy delay - we don't do this because: 1: it takes memory, 2: it is cached at a particular size, so when you zoom in you would start to notice the pixellation. This is the only real alternative to it using your cpu to generate the effect at the required resolution per-frame.

    Thank you that makes a lot of sense! I don't experience a performance loss at all, just a bit of choppiness moving the item around. I forgot to mention that my canvas was in Retina mode, so a crazy DPI ;)

    You guys have created a truly amazing app!

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.