You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the project, this might be exactly what I was looking for. Are there any limitations on mapping I should be aware of? Things like map size limitations? I want to make games ranging from small to huge, and I don't think the original quake 3 was meant for large outdoor environments.
The text was updated successfully, but these errors were encountered:
There should be no limitations based on the QIII engine. Part of our own reasoning behind this fork was to eliminate any reliance on that engine and the inherent limitations. BSP was an impressive technology for the time but it was adding a few annoying restrictions on us.
That said, it has only really been tested up to a map of a similar size to Quake III Team Arena and World of Padman. These are large open area maps but there is no reason it shouldn't support much larger. At the very least because it exports to .obj you can always access it in Blender if you do need to resort to patching chunks together for a truly massive size (probably much larger than a video game would comfortably support anyway).
Thanks for the project, this might be exactly what I was looking for. Are there any limitations on mapping I should be aware of? Things like map size limitations? I want to make games ranging from small to huge, and I don't think the original quake 3 was meant for large outdoor environments.
The text was updated successfully, but these errors were encountered: