-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a workaround for MAX_PATCH_PLANES #336
Comments
There are also a lot of custom Q3 maps that fails to load due to MAX_PATCH_PLANES error. In Q3e they load fine, probably worth to look at. |
I plan to test that Quake 3 IHV Test map Maps that error MAX_PATCH_PLANES:
If anyone happens to know other maps that hit MAX_PATCH_PLANES error, let me know. I'll try to test everything in a week or whenever I get back to this issue. (This isn't really serious important testing. I don't expect addon maps to have patches with more planes than Q3 IHV Test map MAX_PATCH_PLANES required to load
I only tested MAX_PATCH_PLANES intervals of 50. I'm not saying these fixes are bad; even Quake 3 1.16n won't load It doesn't require 16x (MAX_PATCH_PLANES(2048)*16?) as I suggested possibly remembering it as in the original post; at least on Linux x86_64. Using MAX_PATCH_PLANES 5000 with Spearmint's current cm_patch.c on Linux x86_64 fixes loading I'm still deciding what to do with it but I'm leaning toward just increasing MAX_PATCH_PLANES to 5000. I don't really want to spend time messing with float precision issues, and I'll still probably have to increase MAX_PATCH_PLANES for Q3 IHV Test anyway. I'm not planning to increase MAX_PATCH_PLANES in ioquake3 as it probably won't stand up to scrutiny and I can't use |
This is really a problem I've spent a lot of time with. A long time ago I had a list of all custom maps that failed to load due to MAX_PATCH_PLANES error. I haven't been looking for such maps since Q3e and I can't find the list at the moment either. As far as I remember, other maps of ROMANET Gael are also affected https://ws.q3df.org/maps/?map=&au=ROMANET+Gael. Note: You know my heart will always go to Spearmint as it was the best time of my life. Anyways, regarding map loading, I have to say that Q3e outperforms everything else, even Spearmint. The problem is that besides the MAX_PATCH_PLANES error, other errors can also occur when trying to load custom maps, mostly memory problems. As far as I know, with Q3e you can load pretty much all maps, in contrast to other 1.32 based Q3A engines (Xreal/ioquake/Spearmint). At least default Q3 bsp format maps load pretty fine with Q3e. Of course no other format is supported. |
Was definitely not on my list, but found this one, due user report: https://ws.q3df.org/map/red_planet_escape_1/ |
One of the Q3 IHV maps fails to load due to MAX_PATCH_PLANES error. Increasing the max allowed needed 16x size if I remember correctly. So it needs changes to the precision instead.
The text was updated successfully, but these errors were encountered: