Massive problem - TTLG Forums

ShadowSneaker on 26/8/2008 at 23:03

Hey, I'm really stuck with T3Ed. Can anyone decipher what is wrong in the log?

Quote:

Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Log: Found 22 zones
Warning: bspAddNode: Infinitesimal polygon 2 (4)
Warning: bspAddNode: Infinitesimal polygon 2 (4)
Warning: bspAddNode: Infinitesimal polygon 2 (4)
Warning: bspAddNode: Infinitesimal polygon 2 (3)
Warning: bspAddNode: Infinitesimal polygon 2 (4)
Warning: bspAddNode: Infinitesimal polygon 2 (4)
Warning: bspAddNode: Infinitesimal polygon 2 (4)
Log: Polys: 1008 -> 1008
Log: Nodes: 4815 -> 1997
Log: Points: 5313 -> 3710
Log: Vectors: 123 -> 123
Log: Vertex stream 0: 16383 -> 7612
Log: Vertex stream 1: 2827 -> 356
Log: bspBuildBounds: Generated 946 bounds, 7033 hulls
Log: BuildZoneInfo: 0 ZoneInfo actors, 0 duplicates, 0 zoneless
Log: Portalized: 1928 portals, 34 zone portals (34 fragments), 638 leaves, 1997 nodes
Log: BspOptGeom begin
Log: MergeNearPoints merged 417/3710, collapsed 3
Log: Polys: 1008 -> 966
Log: Nodes: 1997 -> 1997
Log: Points: 3710 -> 3261
Log: Vectors: 123 -> 123
Log: Vertex stream 0: 7612 -> 7612
Log: Vertex stream 1: 356 -> 344
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Warning: Node side limit reached
Log: BspOptGeom building sidelinks
Log: BspOptGeom end
Log: Processed 1426 T-points, linked: 9407/9425 sides
Log: Polys: 966 -> 966
Log: Nodes: 1997 -> 1997
Log: Points: 3261 -> 3261
Log: Vectors: 123 -> 123
Log: Vertex stream 0: 7612 -> 4768
Log: Vertex stream 1: 9202 -> 4657
Log: bspBuildBounds: Generated 946 bounds, 7033 hulls
Log: Bsp Rebuild
Log: Allocating 16384 byte dynamic index buffer.
Log: Found 340 coplanar sets in 1994
Log: BspMergeCoplanars reduced 1994->1555
Log: Polys: 966 -> 966
Log: Nodes: 1997 -> 1997
Log: Points: 3261 -> 899
Log: Vectors: 123 -> 123
Log: Vertex stream 0: 4768 -> 0
Log: Vertex stream 1: 4657 -> 0
Log: Polys: 966 -> 966
Log: Nodes: 1863 -> 1863
Log: Points: 3233 -> 3233
Log: Vectors: 123 -> 123
Log: Vertex stream 0: 7457 -> 7457
Log: bspBuildBounds: Generated 921 bounds, 6960 hulls
Log: OptimizeVertexStreams: Split 7457 vertices into 1 vertex streams.
Log: bspBuild built 1555 convex polys into 1863 nodes
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored front sliver
Warning: FPoly::Fix: Collapsed a point
Warning: FPoly::SplitWithPlane: Ignored back sliver
Log: Found 22 zones
Warning: bspAddNode: Infinitesimal polygon 2 (4)
Log: Polys: 966 -> 966
Log: Nodes: 4700 -> 1961
Log: Points: 4240 -> 3238
Log: Vectors: 123 -> 123
Log: Vertex stream 0: 16383 -> 7659
Log: Vertex stream 1: 2404 -> 184
Log: bspBuildBounds: Generated 921 bounds, 6960 hulls
Log: BuildZoneInfo: 0 ZoneInfo actors, 0 duplicates, 0 zoneless
Log: Portalized: 1858 portals, 30 zone portals (30 fragments), 615 leaves, 1961 nodes
Log: BspOptGeom begin
Log: MergeNearPoints merged 1/3238, collapsed 0
Log: Polys: 966 -> 966
Log: Nodes: 1961 -> 1961
Log: Points: 3238 -> 3237
Log: Vectors: 123 -> 123
Log: Vertex stream 0: 7659 -> 7659
Log: Vertex stream 1: 184 -> 184
Log: BspOptGeom building sidelinks
Log: BspOptGeom end
Log: Processed 1437 T-points, linked: 9309/9314 sides
Log: Polys: 966 -> 966
Log: Nodes: 1961 -> 1961
Log: Points: 3237 -> 3237
Log: Vectors: 123 -> 123
Log: Vertex stream 0: 7659 -> 4760
Log: Vertex stream 1: 8873 -> 4554
Log: Allocating 16384 byte dynamic index buffer.
Warning: **** Mesh nodes: 566 (time: 0.00)
Warning: **** Mesh nodes after adding terrain: 566 (time: 0.00)
Warning: **** Mesh nodes after adding static mesh surfaces: 622 (time: 0.01)
Warning: **** Mesh nodes after pre-merge: 488 (time: 0.95)
Warning: **** Mesh nodes after height split: 1409 (time: 1.53)
Warning: **** Mesh nodes after pre-merge: 703 (time: 2.27)
Warning: **** Mesh nodes after subtracting static meshes: 6023 (time: 42.51)
Log: Autosaving of map ignored : A level build is in progress
Warning: **** Mesh nodes after removing nodes under terrain: 6023 (time: 0.20)
Warning: **** Vertex elimination: 0 (time: 0.22)
Warning: **** Set node heights: 6017 (time: 0.48)
Warning: **** TOTAL TIME: 0 (time: 48.18)
Warning: **** NODE BIN SIZE: 12 (time: 0.00)
Warning: **** NODE BINGRID SIZE: 64 (time: 0.00)
Warning: **** Links after adjacent link addition: 14082 (time: 24.68)
Warning: **** Found stairs: 0 (time: 0.01)
Warning: **** Link data calculation (adjacent): 0 (time: 55.68)
Warning: **** Removed stair side-rails; nodes: 6017 (time: 0.00)
Warning: **** Z-delta calculation (far): 0 (time: 0.44)
Warning: **** TOTAL: 14082 (time: 81.32)
Warning: *** TOTAL NAVMESH BUILD TIME: 129.500000
Warning: **** Spatial DB build node matches: 0 (time: 0.04)
Warning: **** Spatial DB subdivide polys: 0 (time: 0.66)
Warning: **** node matching / dbg_find_lowest_unmatched_time: 0 (time: 0.00)
Warning: **** node matching / dbg_match_node_time: 0 (time: 1.42)
Warning: **** Spatial DB node matching: 0 (time: 1.56)
Warning: **** Spatial DB split and height adjust: 0 (time: 0.75)
Warning: **** Spatial DB small gridlet removal: 0 (time: 0.51)
Warning: **** Total # Gridlets: 1262 (time: 0.00)
Warning: **** Gridlet size: 84 (time: 0.00)
Warning: **** Total Spatial Database size: 186776 (time: 0.00)
Warning: **** Spatial DB calc blocked cells: 0 (time: 3.55)
Warning: **** CalculateOpenness() / GetCellsWithValue(): 0 (time: 0.07)
Warning: **** CalculateOpenness() / dbg_no_neighbors_time: 0 (time: 0.79)
Warning: **** CalculateOpenness() / dbg_expand_all_time: 0 (time: 4.69)
Warning: **** CalculateOpenness() / dbg_delete_and_append_time: 0 (time: 0.01)
Warning: **** Spatial DB calc openness: 0 (time: 5.57)
Warning: Final NavMesh size: 1366248 bytes (690300 bytes for nodes, 675948 bytes for links)
Log: Autosaving of map ignored : A level build is in progress

When I started making my mission I would do a 'Build All' every time I did something new, as that is all I knew to do. I then realised that the 'Navmesh Build' was what took so long and that I could do 'Geometry Build' and 'Flesh Build' and that was enough in order for me to play the mission.

I've done most of the mission doing 'Build All' but have made about 3 large rooms doing only the two builds and therefore the navmesh was not built for these rooms.

Tonight I added some more AI so I did a 'Build All'. The mission was playable before I did that. Now it goes to the loading screen but then returns to T3Ed.
Can anyone help?

Thanks

SS

massimilianogoi on 27/8/2008 at 01:59

I suggest you to recreate the map, with copy-paste all the things that doesn't give problems, and after re-create the rest in the new map. Then look if it gives to you the same problem.

If that is, then there is no other solutions than reinstalling from 0 the editor... :erg:

Martin Karne on 27/8/2008 at 03:22

You have probably a lot BSP work there, recheck for BSP errors, with Tools, "Report off grid BSP".
Once you do that, recompile and try again for BSP errors "Report off grid BSP".
And try increasing the vertex pool in the user.ini (root directory of thief).
Duplicate its size (do a backup of the user.ini first in case you want to increase slowly those values).

ShadowSneaker on 27/8/2008 at 10:33

I do have alot of BSP, that is correct. I will try those things then report back later.
Thanks guys.

Edit : I found the problem : there are alot of brushes in my mission that are tilted at weird angles which I believe was aggravating the navmesh.
T3Ed seems to hate the tilted cylindrical pillars in this screenshot :

(http://i212.photobucket.com/albums/cc4/Fumigated/SSFM16.jpg) http://i212.photobucket.com/albums/cc4/Fumigated/SSFM16.jpg

and too many of them causes that "node side limit reached" warning. They also make the navmesh go crazy in the places where they touch the ground.
I added a few navmesh subtraction volumes to the environment (around those areas where the navmesh was really dense) and the mission started playing again.

I have run into another problem though. I added 5 coffins with lids and candles ontop of each one, aswell as 2 wall torches to a room and now it won't load when I 'Send to Xbox'. I could get rid of them and have the room looking plain and empty but I wonder if someone knows why adding those things might have caused an error.
In the memory usage I have only used 1089KB of static meshes so I don't see why adding them would do this.

Thanks

SS

CrackedGear on 27/8/2008 at 19:08

Quote Posted by ShadowSneaker

I have run into another problem though. I added 5 coffins with lids and candles ontop of each one, aswell as 2 wall torches to a room and now it won't load when I 'Send to Xbox'. I could get rid of them and have the room looking plain and empty but I wonder if someone knows why adding those things might have caused an error.
In the memory usage I have only used 1089KB of static meshes so I don't see why adding them would do this.

Thanks

SS

I think the problem is not that you have all these static meshes, but rather that you had 7 light sources in one room. If the lights really need to be there, try turning off shadow casting on as many meshes as you can. Also, for your earlier problem, try replacing those tilted cylinders with meshes, which should ease a lot of your bsp problems.

Judith on 27/8/2008 at 20:36

Guys: never, I mean, never use "Build All" every time you want to test a map. I lost my .unr file because of that one day (and tons of time too). Use it after you built the map and you're tweaking your AI behaviour and navmesh. You do anything other than that - just build bsp and flesh lighting.

Beleg Cúthalion on 27/8/2008 at 20:42

I never had any problems giving my map a build-all from time to time, although it's probably eight times as big as Stonemarket by now. I cared for Krypt's suggestions about the Navmesh, though, so that might have helped.

ShadowSneaker on 27/8/2008 at 22:34

I tried that, CrackedGear and it made no difference. I deleted all of the extra stuff I had added and also a whole room and it still does not work. Is it possible that a complex AI path could cause this? I changed a few of them as they were too predictable.
I also do not have 3DSMax so I can't turn the pillars into SMeshes and there are no Smeshes in T3Ed that are interchangeable with them.

Judith, I always save before doing a 'build all' and only do them when I have altered the navmesh, or a part of the environment where AI can go.

Beleg, what were Krypt's suggestions about the navmesh?

Thanks

SS

massimilianogoi on 27/8/2008 at 23:21

Quote Posted by Judith

Yes, Judith is right. :erg:

Building everytime is a huge loss of time.

massimilianogoi on 27/8/2008 at 23:27

Quote Posted by ShadowSneaker

Judith, I always save before doing a 'build all' ...

Work ALWAYS with two files! One for work, and the other for backup: after some change save also on the backup file; I use naming namemap.unr for the file to work, with "namemap" a name choosed, and namemap1.unr for the backup copy.

In this way you will never lose all your work.

And in extreme case, don't forget to recover your last functionning Autoplay.unr, where there is your ultimate functionning map. :thumb: