Skip to content

increase MAX_MAP_PLANES - #1086

Open
jhh8 wants to merge 1 commit into
reactivedrop_betafrom
more-planes
Open

increase MAX_MAP_PLANES#1086
jhh8 wants to merge 1 commit into
reactivedrop_betafrom
more-planes

Conversation

@jhh8

@jhh8 jhh8 commented Aug 10, 2026

Copy link
Copy Markdown
Member

No description provided.

@jhh8

jhh8 commented Aug 10, 2026

Copy link
Copy Markdown
Member Author

need to build vrad_dll.dll for this to take effect

@BenLubar

Copy link
Copy Markdown
Contributor

Wouldn't this require rebuilding the engine? I don't think anything in client.dll or server.dll uses this directly.

@jhh8

jhh8 commented Aug 12, 2026

Copy link
Copy Markdown
Member Author

its to not get numplanes + fakeplanes > MAX_MAP_PLANES error when compiling a map

@jhh8

jhh8 commented Aug 12, 2026

Copy link
Copy Markdown
Member Author

hammer++ probably swapped to dynamic arrays to not have limits on planes/lights/brushes etc

@jhh8

jhh8 commented Sep 1, 2026

Copy link
Copy Markdown
Member Author

To add more to this, theres also a brushsides limit which is the same 65536, launching a map with over that many brushsides (if you manage to compile it) crashes the game with "Map with too many planes". This num_max_planes is some seperate thing, havent looked into it in detail but feels like its a vrad only thing that has no references in the engine which counts things that dont get into compiled bsp like skip textured brushes or maybe it even counts displacement triangles. Because why it hits 65536 so much sooner than brushsides i dont know. I see it as just another random harmful source engine limit that has no real effect and limits brushsides even earlier than they should be

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

Successfully merging this pull request may close these issues.

2 participants