Yikes, yes we shouldn’t do an assert, a Lua error sounds more reasonable!
Sadly I don’t think we expose the max texture size currently (but internally we try to get it in runtime). You might be able to query it yourself in a native extension though?
(Added a ticket for the assert issue: DEF-3782. Maybe we could discuss in the team if it makes sense to expose the “max texture size”, @britzl?)
Ok, I will try. But please make render target creation without asserts as well - so it will be possible to catch any problems there at early stage. E.g. if device doesn’t support not POT textures.