Too many surfaces error (texinfo maximum)

[Ypsckud]

There seems to be a 8192 texinfo maximum in the engine. Can it be increased?

[0lvin]

Do you have map example with bigger amount of texinfo? It could require changes in all renders to support bigger maps.

[Ypsckud]

Yes, it's the map I am currrenlty making. I think that 8192 is a pretty small number considering that there are a lot of textures to be used with unique offsets for modern mapping (like trim textures). I managed to run the map on re-release version of Q2, but not on Yamagi (so the map itself is OK)

[0lvin]

You could try branch with partial ReRelease support, but I don't know when I finish code changes or when it could be merged, if merged/finished at all.

Look to #2, #3 and #4 for more info.

[Ypsckud]

Will do, thanks for answering!

[Yamagi]

I'm very hesitant to change these kind of things in YQ2 because these are that kind of changes which seem to work well until someone finds that one case which doesn't. However this is a good argument for doing Q2 Remastered support in a separate branch with relaxed backward compatibility considerations.

[0lvin]

@Ypsckud Could you please check with bd19960 ?

Code has allocated memory for map dynamically, (except count of submodels and one place for Leafs), it should be enough to load any maps.

Only GL1 and VK are checked with some random maps from ReRelease. Other renders has issues with wall lights. GL1 sometime has broken images after load maps, so it's known bug. I am checking what is wrong image allocation, maybe some limit or hard-coded value.

[0lvin]

@Ypsckud do you need windows binaries for test?

Could you please reopen issue if it is still reproduced?