Halp

[Gwunty]

07.20.08 18:21:27 EAX: 0xFFFFFFFE
07.20.08 18:21:27 EBX: 0x00000201
07.20.08 18:21:27 ECX: 0x0012F2B8
07.20.08 18:21:27 EDX: 0x000002CC
07.20.08 18:21:27 EDI: 0x0012F2B8
07.20.08 18:21:27 ESI: 0x00000000
07.20.08 18:21:27 EBP: 0x0012F190
07.20.08 18:21:27 ESP: 0x0012F180
07.20.08 18:21:27 EIP: 0x7C90EB94, C3 8D A4 24 ?????
07.20.08 18:21:27 EXCEPTION halt in .\import_collision_bsp\reduce_collision_bsp.c,#208 : surface_index>=0 && surface_index<bsp->surfaces.count

Im compiling a .jms ive asked alot of people about this problem and no one seems to know how to fix it.

[Rentafence]

Just a wild guess, but maybe your model has too many triangles.

[Bastinka]

Just a wild guess, but maybe your collision model (which I'm guessing you're trying to compile) has too many triangles.
That, but I'm not 100% sure about collision.


EXCEPTION halt in .\import_collision_bsp\reduce_collision_bsp.c,#208 : surface_index>=0 && surface_index<bsp->surfaces.count
Always reading it and applying common sense can come a long way you know, it's really not rocket science.

[Rentafence]

I edited my post after realizing the error said bsp

[Roostervier]

I think you could fix it by adding some portals.

[Gwunty]

The map is very low-res ill get the polycount in a sec.
2220 Polies I dont see that as a problem.

[kid908]

The map is very low-res ill get the polycount in a sec.
2220 Polies I dont see that as a problem.

try relinking and reapply the material id. usually work for me.

[Rooster]

does this error produce a debug? When does it occure? (after fixing open edges or after unupdated tri's?)