This make sense to me. I wonder if even 4096 is too big? I was thinking also that excessivly large Atlases might incur some memory bandwidth penalties, but with PCI express 3 and even 2, this seems to be a non-issue. Still, maybe it would be worth doing a quick benchmark to see what the difference actual is.
Otherise, I think this make sense and will think about moving forward with it. On Tuesday, January 31, 2017 at 6:20:22 PM UTC+9, DXsmiley wrote: > > It's possible to get the maximum texture size dynamically with > "pyglet.gl.GL_MAX_TEXTURE_SIZE", so there's no reason to catch exceptions. > I think just taking this and rounding it down to the next power of two > would suffice for most cases. > > That being said, some graphics cards support extremely large textures, so > we could cap it at 4096 (~67 MB) unless explicitly overridden. > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
