Skip to content
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

Are there any limitations I should be aware of? #6

Open
ghost opened this issue Apr 13, 2021 · 1 comment
Open

Are there any limitations I should be aware of? #6

ghost opened this issue Apr 13, 2021 · 1 comment

Comments

@ghost
Copy link

ghost commented Apr 13, 2021

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.

@osen
Copy link
Owner

osen commented Apr 13, 2021

Hi,

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant