Author Topic: ---  (Read 4199 times)

MON1TOR

  • 68 Carbine
  • Posts: 328
---
« on: June 30, 2015, 04:41:34 AM »
----
« Last Edit: August 27, 2015, 04:06:02 AM by MON1TOR »

JMR

  • Map Committee
  • Autococker
  • Posts: 574
Re: INPROGRESS MAPPACK: SIMPLES
« Reply #1 on: June 30, 2015, 06:35:33 AM »
MAX_PATCHES is caused when there are too many large surface areas, so much so that they cannot all be lit.

Usually when I run into the MAX_PATCHES error, what I do is scale up textures from the Surfaces panel. Do this for textures that don't matter / surfaces which you cannot see. For example, the sky, below the ground, outside of walls that they do not see, Etc. Set the size to 100x100, usually works wonders for me.

You can use the "Apply to face" button to scale up texture faces of brushes which players won't see.

MON1TOR

  • 68 Carbine
  • Posts: 328
Re: INPROGRESS MAPPACK: SIMPLES
« Reply #2 on: June 30, 2015, 07:22:26 AM »
MAX_PATCHES is caused when there are too many large surface areas, so much so that they cannot all be lit.

Usually when I run into the MAX_PATCHES error, what I do is scale up textures from the Surfaces panel. Do this for textures that don't matter / surfaces which you cannot see. For example, the sky, below the ground, outside of walls that they do not see, Etc. Set the size to 100x100, usually works wonders for me.

You can use the "Apply to face" button to scale up texture faces of brushes which players won't see.
Mhm. Thanks, goin' to try it out!

Ace

  • Autococker
  • Posts: 661
Re: INPROGRESS MAPPACK: SIMPLES
« Reply #3 on: June 30, 2015, 10:19:39 AM »
You can also go into bsp/pball/bats and create a new one named maxpatch help or whatever you want. It's basically final compile.bat, but chop tells it to subdivide the surfaces into larger patches. The default is 64, so don't go too large.

The better option is to break up large faces into smaller ones where you can.

call ..\compilers\qbsp %1
call ..\compilers\vis %1
call ..\compilers\rad -chop 256 -extra %1
call ..\compilers\runmap %1

BASEBALLDUDE

  • Autococker
  • Posts: 703
Re: INPROGRESS MAPPACK: SIMPLES
« Reply #4 on: June 30, 2015, 11:49:47 AM »
Make sure the map is not leaked. If it is leaked, it will be indicated by ****leaked**** in the black box.

MON1TOR

  • 68 Carbine
  • Posts: 328
Re: INPROGRESS MAPPACK: SIMPLES
« Reply #5 on: June 30, 2015, 12:18:18 PM »
Make sure the map is not leaked. If it is leaked, it will be indicated by ****leaked**** in the black box.
No leak, I attach the map file..

MON1TOR

  • 68 Carbine
  • Posts: 328
Re: INPROGRESS MAPPACK: SIMPLES
« Reply #6 on: June 30, 2015, 12:50:42 PM »
Ace, ur solution worx. Thx.

Rockyar_96

  • 68 Carbine
  • Posts: 370
Re: INPROGRESS MAPPACK: SIMPLES
« Reply #7 on: July 01, 2015, 07:11:30 AM »
Once the maps are finished make sure to make an extra thread for all of them. That'll make the feedback easier

MON1TOR

  • 68 Carbine
  • Posts: 328
Re: INPROGRESS MAPPACK: SIMPLES
« Reply #8 on: July 01, 2015, 12:29:51 PM »
Once the maps are finished make sure to make an extra thread for all of them. That'll make the feedback easier
Yup.