TestOMFReader texture memory limits
Our Linux CI machines are using Mesa which doesn't always expose that much texture memory. An I/O test shouldn't be pushing our rendering limits. Can the test be simplified at all?
Our Linux CI machines are using Mesa which doesn't always expose that much texture memory. An I/O test shouldn't be pushing our rendering limits. Can the test be simplified at all?