.Map :: MoHAA Mapping

Silent_Death wrote:************ ERROR ************
LoadPortals: couldn't read C:\PROGRA~1\EAGAME~1\MOHAA\main\maps\Door.prt

we need more information! could you give us more of what was written before that line. Most likely, there is no prt file, so it can't be read. the reason ought to be an error in bsp compilation, so we'd need what is written there.
How do you compile, using MBuilder or somehow else?

Silent_Death wrote:************ ERROR ************
LoadPortals: couldn't read C:\PROGRA~1\EAGAME~1\MOHAA\main\maps\Door.prt

you have too big visdata size usually

make some structual brushes into detail ones and see about putting some vis_leafgroups in

Hey, I just figured out how to make log files with MBuilder and it works great!!!

You can make seperate logs for each step. Just click on "change" and put in the code.

-v > c:\WINDOWS\desktop\log_bsp.txt

-v > c:\WINDOWS\desktop\log_vis.txt

-final > c:\WINDOWS\desktop\log_light.txt

I have them going to the desktop so they can be trashed easily, after looking them over.

Yeah you can do that with any command 8)

Ok, so where do we look for a list of the command symbols? I don't see anything about them in "Compiling Options/settings by jv_map".

What does ">" mean, "write to"?
What does "-" mean, "and"?

I have a feeling these symbols are basic DOS commands, but it has been a long time ago for me.

for the '>', maybe buy an ancient book of DOS commands

it is used to redirect output from the screen to something else, like C:\>dir>lpt1: would print out the directory of c:\ on your printer connected to lpt1.

the '-', you ought to know as this is common for adding parameters to many executables (where some may use '/' or just the command instead)
e.g. c:\>dir /? gives a summary of possible parameters

> in this context is called "pipe"... like in: redirect the text steam through this pipe that leads into the pond called "c:\WINDOWS\desktop\log_bsp.txt"
8)

another error:

max_patch_planes

theres too many patch meshes in the map, or too many faces on all the patch meshes. either delete some, or replace them with less complex ones [theres an option in the curve menu to decrease complexity i think]

you get that error in the console ingame, when you start to load the map, but no errors in the compile at all, and this stops you playing the map. but theres not many maps that would need that many meshes [im working on a mine map, with all the tunnel walls made from patch mesh to get the curves]

Trinculo wrote:*** Entity 0, Brush 47, bounds (236.759 1005.5 204) - (749.059 1009.04 306.046)
^-- Fence masks must only be used with fence or nodraw.


has anyone seen this error before????

it means that theres a fence texture [a texture with transparent areas, like the secfence texture] on a brush with another texture, other than another fence texture or nodraw. i get this all the while, and it doesnt have any effect on the map.

yeah, fences w/o nodraw i don't see why the fuss? doesn't affect

Saw someone posted this but didnt give any solution. Mine keeps deleing the prt. Wont compile right, cant see any changes. Does anybody know?

If you don't get a prt your map is likely to have a leak.

If you have a .lin file you can do file -> pointfile to find it.

WTF is this? I get it at FS startup when i compile with mbuilder.

Did you have a look on teh first page....

---------
ERROR: FloatPlane: bad normal

Somehow you've created an invalid brush in your map. At least one face of this brush will be invisible in game. This usually is the result of careless vertex-editing.

SOLUTION: Use a plugin (e.g. Rogue's) to remove bad brushes. Be careful with vertex editing in the future
-------------------------------------------------------------------------------

Also remove custom pk3's

m0g wrote:Did you have a look on teh first page....

---------
ERROR: FloatPlane: bad normal

Somehow you've created an invalid brush in your map. At least one face of this brush will be invisible in game. This usually is the result of careless vertex-editing.

SOLUTION: Use a plugin (e.g. Rogue's) to remove bad brushes. Be careful with vertex editing in the future
-------------------------------------------------------------------------------

Also remove custom pk3's

nah thanks though. I just didn figure it would be there i'll check next time. if that's all it is i don't really care.

need info on this or how to find what piece is doing it

************ ERROR ************
Exceeded MAX_POINTS_ON_WINDING

thanks