Open ns130291 opened 4 years ago
Thanks for reporting. Looks like a check to prevent size_t
overflow.
@poggenhans maybe it can be replaced by a system specific size_t
limits check?
Older versions of Ogre (and some graphic cards) have a hard-coded limit of 16bits for indexing vertices (see https://github.com/OGRECave/ogre/blob/9e26b734e3586bfb4dfe25f4a82d3928f283e74b/OgreMain/include/OgreManualObject.h#L358).
This assert just checks that. It can probably be removed by now. A better solution would be to call end()
and begin()
from time to time on the manual object when the vertex count gets too high to create new object.
I have a quiet big map and trying to load it results in the following error: