Ok guys I finally did that fudging map I've been asking how to do in 3DS MAX for the past few years however... One new problem has emerged, one I've never encountered before...

The geometry of my map flickers in and out of existence when moving around. Now what in the hell is this supposed to be about?

Could it be because its an interior map, it uses no sky and the odd lightmap is causing it? Please don't tell me it has something to do with the model in 3DS MAX...

This is so damn exciting though! I finally made a mashed up CMT like extended A10 campaign BSP! So this was the problem I had over the years: Importing BSPS came with errors such as multiple faces in one spot. I removed some faces, flipped the others, capped the holes with mesh and just slapped a texture over it, named the shaders to match the name as the tag files and added the correct '%' symbols to the right shaders.

THE NEW PROBLEM: Invisible Map Geometry


UPDATE: I've tried every combo and method I could think of and cannot get it to render properly. I'll assume campaign BSPs are way too large and don't work with our Tools. In other news, I'm now having a blast modifying multiplayer maps and adding sections to them, with some campaign assets of course. Sucks I cannot alter the campaign BSPs though. Oh well... Hopefully the MCC will come with a better toolkit or something.
Edited by Halo CE Noob Modder117 on Nov 5, 2019 at 09:59 PM

could have too many portals. (too many within visible range of eachother and they'll start to fight eachother)

or too few(going over the geometry budget)

or portals not placed in sane/safe locations for portaling

Or your bsp geometry is too simple to subdivide properly and needs more tesellation
Edited by OrangeJuice on Nov 3, 2019 at 12:32 PM

...I don't have any portals, I forgot to do them!

Importing the regular A10 portals causes Tool to crap out Magenta errors for every portal (now what in the hell is this one? Unearthed edges?). Would it be safe to put rectangles over every doorway and apply +portal? Or do I have to seal the geometry like a wall with verts connected to the actual map BSP itself?

Most YouTube tutorials I've seen literally just turn the map into a giant checkerboard with one giant plane. It this one simple way to do this? Note: As usual, they're outdoor maps so I'm not too sure if interiors have to be any different.

The debug file: The 'magenta' unearthed errors highlight the outer borders of each portal

I get this when I import all A10 portals:

D:\Program Files (x86)\Microsoft Games\Halo Custom Edition>tool structure levels\test\example new
Couldn't read map file './toolbeta.map'
building intermediate geometry...
### WARNING found #28 degenerate triangles.
building collision geometry...
reducing collision geometry...
building collision bsp...
### WARNING found nearly coplanar surfaces (red and green).
reducing collision bsp...
verifying collision geometry...
verifying collision bsp...
building portals...
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
EAX: 0x00000000
EBX: 0x06298801
ECX: 0x00000000
EDX: 0x00000000
EDI: 0x0019F210
ESI: 0x00000000
EBP: 0x0019F0E8
ESP: 0x0019F0DC
EIP: 0x77DA136C, C2 08 00 90 ?????
EXCEPTION halt in \halopc\haloce\source\memory\array.c,#130: index>=0 && index<array->count







I get this when using the grid/box method:



D:\Program Files (x86)\Microsoft Games\Halo Custom Edition>tool structure levels\test\example new
Couldn't read map file './toolbeta.map'
building intermediate geometry...
building collision geometry...
reducing collision geometry...
building collision bsp...
### WARNING found nearly coplanar surfaces (red and green).
reducing collision bsp...
verifying collision geometry...
verifying collision bsp...
building portals...
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### WARNING unearthed edge (magenta boxed lines).
### ERROR: portal does not define two closed spaces. (see yellow in error geometry)
building render geometry...
building subclusters...
building pvs... building pvs... building structure lens flares...done


structure bsp "levels\test\example\new"
BSP has 25668 nodes, 12609 leaves
51664 surfaces and 80312 vertices in 27 material groups
157 portals, 9 clusters

3010Kb collision data (388Kb vertices, 1222Kb edges, 308Kb surfaces)
4781Kb render data (3199Kb vertices, 958Kb surfaces,
347Kb nodes/leaves, 268Kb clusters)
0Kb pathfinding data
----------------------
8841Kb (without debug information)
Edited by Halo CE Noob Modder117 on Nov 4, 2019 at 08:22 AM