In one of my sp's where u play as the arbiter and play across chilllout, carousel, longest and dangercanyon, When you reach the third BSP most of the people are frozen and don't do anything. I have set their manual BSP index to the right BSP and everything.

However in CMD when i compile it it says something like they are attached to BSP 1 and 3 or something like that.

How can I fix these poor frozen people?

post your latest debug.txt entry here.

10.18.10 10:26:16 tool pc 01.00.00.0609 ----------------------------------------------
10.18.10 10:26:16 reference function: _write_to_error_file
10.18.10 10:26:16 reference address: 42ca20
10.18.10 10:26:16 Couldn't read map file './toolbeta.map'
10.18.10 10:26:24 WARNING: encounter start_grunt could be ambiguously attached to BSPs #0 and #1
10.18.10 10:26:24 WARNING: encounter dc_allies could be ambiguously attached to BSPs #0 and #1
10.18.10 10:26:24 WARNING: encounter start_grunt could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter allies1 could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter half_room could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter stealth_room could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter tp_room could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter tp_room_flood could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter big_room_allies could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter big_room_covenant could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter big_room_flood could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter next_room could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter carousel_flood could be ambiguously attached to BSPs #1 and #2
10.18.10 10:26:24 WARNING: encounter carousel_covenant could be ambiguously attached to BSPs #1 and #2
10.18.10 10:26:24 WARNING: encounter carousel_allies could be ambiguously attached to BSPs #1 and #2
10.18.10 10:26:24 WARNING: encounter dc_allies could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter tunnel2 could be ambiguously attached to BSPs #0 and #2
10.18.10 10:26:24 WARNING: encounter outer_allies could be ambiguously attached to BSPs #1 and #2
10.18.10 10:26:24 WARNING: encounter cov_wave could be ambiguously attached to BSPs #1 and #2
10.18.10 10:26:24 WARNING: encounter banshees could be ambiguously attached to BSPs #1 and #2
10.18.10 10:26:24 invalid detail object data in structure levels\test\dangercanyon\dangercanyon
10.18.10 10:26:25 WARNING: encounter banshees could be ambiguously attached to BSPs #1 and #3
10.18.10 10:26:25 WARNING: encounter longest_allies could be ambiguously attached to BSPs #1 and #3
10.18.10 10:26:25 WARNING: encounter longest_flood could be ambiguously attached to BSPs #2 and #3
10.18.10 10:26:25 WARNING: encounter hall_flood1 could be ambiguously attached to BSPs #1 and #3
10.18.10 10:26:25 WARNING: encounter hall_covenant1 could be ambiguously attached to BSPs #1 and #3

For the encounters are you sure you checked the "manual bsp index" box?
Edited by d4rfnader on Oct 17, 2010 at 10:51 PM

thank you nader

I don't no if u ment look back at the manual bsp index box or check the box underneath 3d firing positions but i fixed it now thank you

Can you PM when map is up :D

sure thing yeeyayy. It may take a bit cos i still have to do 5 more sp's that go with the campaign including two airborne stile ones which will take a while and a training mission containing a lot of scripts