i try to opena map in sapien but it gives me this error

07.10.15 10:51:42 sapien pc 01.00.00.0609 ----------------------------------------------
07.10.15 10:51:42 reference function: _write_to_error_file
07.10.15 10:51:42 reference address: 401b13
07.10.15 10:51:42 Couldn't read map file './sapienbeta.map'
07.10.15 10:51:43 CreateDevice succeeded with refresh rate = 0
07.10.15 10:51:44 Sound card doesn't meet minimum hardware requirements. Disabling hardware option.
07.10.15 10:51:45 Increasing sound decompression buffer size to 1048576 bytes
07.10.15 10:52:21 EAX: 0x00000001
07.10.15 10:52:21 EBX: 0x00000001
07.10.15 10:52:21 ECX: 0x0012EF1C
07.10.15 10:52:21 EDX: 0x77CC64F4
07.10.15 10:52:21 EDI: 0x0012ED30
07.10.15 10:52:21 ESI: 0x00000000
07.10.15 10:52:21 EBP: 0x0012EC08
07.10.15 10:52:21 ESP: 0x0012EBF8
07.10.15 10:52:21 EIP: 0x77CC64F4, C3 8D A4 24 ?????
07.10.15 10:52:21 EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#3157: #66 is not a valid bitmap_group_sequence_block index in [#0,#66)


what should i do ?

While I cant give you an exact report on how to fix whats wrong without getting a bit more information, you can look at the debug report and help yourself a tad bit.

07.10.15 10:52:21 EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#3157: #66 is not a valid bitmap_group_sequence_block index in [#0,#66)

That line right there is telling you what's giving you issues. Right now its saying that you have an invalid bitmap sequence at index #0 and #66. Mind explaining what you're trying to open exactly?

My friend wants to do moding in bigass so i tried to extract and remove some corrupt files,i removed all corrupt files except that ,idk how to remove that

So, you extracted the Bigass map using the HEK+? After that, you tried to remove corrupt files?

What 'corrupt files' are you refering to?

Some model file were corrupted like falcon's model,mongoose'model ,so i downloaded the tags of same type and used in the file

People need to learn that if you're a beginner or even simply haven't done something before, only make changes INCREMENTALLY.

Do one or two things MAX between opening the scenario in sapien or compiling.

This way, although it takes a few extra seconds here and there, you will know for sure what went wrong between the last time it worked and when it broke.

If you spend 4 hours going from stock map to {hr}{h4}ULtrA_PWngE-BigASS_jnlx2.map, and then at the end it doesn't compile or crashes sapien, GOOD FREAKING LUCK finding the exact source of that error, especially with one as generic as this one.

It's like,


Sapien/Tool: "OH HEY, a bitmap is bad somewhere. Fix that and try again, yeah?"

You: "But....I just inserted 5,000 new bitmaps over the past 3 hours....which one is bad?"

Sapien/Tool: "Lel IDK nub, find it yourself scrub. My debugging is a joke, son!"

You: *weeping*


Save yourself the frustration. Only do small things between each compile check, you will thank me and thank yourself each and every time an error occurs, because instead of slogging through 5,000 bitmaps, you'll be going through maybe 10 between the last 2 models you added to the map.

Easy peasy.
Edited by NeX on Jul 10, 2015 at 11:55 AM
Edited by NeX on Jul 10, 2015 at 11:56 AM

Every waking hour of every damned day for a millennia to come.