Halo Maps Forum

Quote: - Original message by M5clan ---- On the Gearbox forums ------------
**SAPIEN**
Q & A:

Q: What is a Sapien error?
A: Whenever you go to open Sapien and it locks up, followed by closing, there's an Error.

Q: How do I get the error information?
A: You will find it at the end of debug.txt (hover to show directory in status bar)

Q: What's the usual cause of an error?
A: You probably have a incorrect reference in, or corrupt tags.

Posting For Help

In case of Sapien errors, you should make a thread containing the following format.
1. Everything you may know about the error
2. the latest entry in the debug.txt
3. Wrap the entry in CODE tags to save excessive scrolling

**TOOL**

Q & A:

Q: What is tool?
A: Tool is generally the last program used. It compiles everything you have made. Whether it be a BSP, bitmaps, models, or even the final map.

Q: Why does Tool give errors?
A: Tool doesn't screw up, the user does. Whatever it is you are attempting to compile, is not correct.

Q: Where can I find the error info?
A: Tool will tell you what's wrong in 2 places. One, in it's window. two, in debug.txt of course.

Posting For Help

Any time you have an error, you can count on needing the debug.
Include the following in your thread:
1. everything tool said
2. Latest entry in debug.txt
3. What you were attempting to do
4. Wrap the error information in CODE tags to save on scrolling

**GUERILLA**

Q & A:

Q: What is guerilla needed for?
A: Guerilla is essentially an all-forms version of Sapien, and is where you will do most of your tag creating/editing.

Q: How do I know if there's an error?
A: Open the tag, and look in the boxes for red text. Anywhere there is red text, is a problem. Most likely incorrect reference, files, or filenames.

Posting For Help

There's really no guideline to posting guerilla errors. Its usually just because you can't fix something. Just be sure to include the following.
1. Give us information on what this tag is, and what you are trying.
2. Give us at least 2 screenshots of the tag opened in guerilla.
3. Please be as descriptive on the problem as possible, we can't help otherwise.

----I will be updating this list as more errors appear.

Sapien Debug Errors
----NOTE: The file names inside the " ' "s in these errors are only examples. The contents inside the " ' " may vary.

Code:

Quote:
ERROR:

SOLUTION: The tag you have tried to add into the heirarchy is missing tags, or its tags are not correct. It will fail to function or show up properly until fixed.

ERROR:
failed to load gbxmodel tag 'weapons\overwatch\fp\fp'
failed to load weapon tag 'weapons\overwatch\overwatch rifle'
file_open('tags\material #.shader_model') error 0x00000002 'The system cannot find the file specified. '

SOLUTION: That tag and/or file does not exist. Either make one, or fix the tag in guerilla.
OR
Ctrl+F it will come up with a search box. Click on "-> All files and
folders". Enter all or part of the file name. When it finds it check which
folder you debug says it should be in ,and than put it there. If you
can't find it you may have to get it from a friend, reinstall the
HEK ,or Halo CE. --- x opocolypse x

ERROR:
failed to load weapon tag 'weapons\battle_rifle\battle_rifle'

SOLUTION: The tag mentioned is corrupt, and needs fixed immediately. Use guerilla to do so.

ERROR:
EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#3157 : #3 is not a valid bitmap_group_sequence_block index in [#0,#3)

SOLUTION: There is a sequence index thats incorrect in your weap Hud interface. Fix by correcting path to a existing file in guerilla.

ERROR:
EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#3157 : #-1 is not a valid object_function_block index in [#0,#4)

SOLUTION: Go through all the tags you just changed and make sure your block indexes do not say -1. Its usually one of the funtions in the tank's vehicle tag. Just find someone and get the tank folder from them.

ERROR:
EXCEPTION halt in \halopc\haloce\source\objects\objects.c,#1913: function_index>=0 && function_index<NUMBER_OF_OUTGOING_OBJECT_FUNCTIONS

SOLUTION: If you have AI in the map, this is their way of telling you..
you gave them birth defects. Fix by deleting the entire AI encounter
before saving the scenario. Then re-make the AI tags

(Hobbet360's) REVISED SOLUTION: You need new energy sword tags, the birth defects are caused by faulty weapons.

ERROR:
EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#3157 : #1 is not a valid scenario_biped_palette_block index in [#0,#1)

SOLUTION: biped/biped pallet is corrupt. open the .scenario in
guerilla, and scroll down to biped section. delete the suspicious bipeds from there first, the delete it from the biped pallet. doing this in the
opposite order will result in crashing.

ERROR:
EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#3157 : #0 is not a valid shader_transparent_chicago_map_block index in [#0,#0)

SOLUTION: Your scenario is either referencing a corrupt
shader_transparent_chicago, or the shader is referencing corrupt
items

ERROR:
EXCEPTION halt in \halopc\haloce\source\tag_files\tag_groups.c,#3157 : #-1 is not a valid animation_graph_unit_seat_block index in [#0,#0)

SOLUTION: Your animation graph fails. Try adding a new block or making a new one.

ERROR:
file_open('tags\levels\test\dangercanyon\dangercan yon.scenario_structure_bsp') error 0x00000002 'The system cannot find the file specified. '
couldn't open scenario_structure_bsp tag 'dangercanyon.scenario_structure_bsp'.
failed to load structure bsp 'levels\test\dangercanyon\dangercanyon'

SOLUTION: Your structure bsp is not correctly referenced. Fix in
guerilla by... open your .scenario, and find the BSP reference. It
should be red. Fix the reference to the correct path of
the .structue_bsp

ERROR:
file_read('tags\effects\particles\air\bitmaps\smok e tank cannon.bitmap') error 0x00000026 'Reached the end of the file. '

SOLUTION: "reached the end of the file." means your tags are
fubar'd. Any of them with this error need to be deleted, unfortunately.

ERROR:
07.28.06 15:27:06 need to get the following tags:

SOLUTION: All the tags listed after that, are missing. Find them, or
make them.

ERROR:
EXCEPTION halt in \halopc\haloce\source\cseries\profile.c,#442: parent_timesection->self_msec >= child_timesection->elapsed_msec

SOLUTION: Go into Tasks/Processes and change the affinity for the
program to single CPU.
OR
Right click sapien.exe, select Properties. Then go to compatibility, and set it to run in Windows 98

ERROR:
EXCEPTION halt in \halopc\haloce\source\tag_files\tag_files.c,#1373: tag_file_count<MAXIMUM_TAG_FILES_PER_INDEX

SOLUTION: Sadly, sapien is whining about too many tags. Delete as
many unused ones as possible.

ERROR:
s\objects.c,#3250: object_compute_node_matrices root node matrix had a bad position (1.#QNAN0,1.#QNAN0,1.#QNAN0)

SOLUTION: vehicles and weapons are fubar. Open scenario in guerilla
and remove all of the vehicles/weapons. Then re-add them one by
one, until you figure out which one is crashing sapien. Take it and
remake the nodes.

ERROR:
###Too many lens flares submitted to frame

SOLUTION: lens flares will not show in-game. In the shaders, there is
one that has lensflares and its creating lensflares in the BSP That
shouldn't be there. Remove the lens flares from the shader,
recompile BSP, and render lightmaps.

ERROR:
EXCEPTION halt in \halopc\haloce\source\math\matrix_math.c,#1109: !realcmp(determinant, 0.0f)

SOLUTION: You've failed at tags. renameyour tags folder and
reinstall HEK. Only add your tags back in as you need them. Once
you find which ones corrupt, delete and/or fix it.

ERROR:
file_open('tags\ui\editor\markers\normal\normal.gbxmodel') error 0x00000003 'The system cannot find the path specified. '
couldn't open gbxmodel tag '<name>.gbxmodel'.
EXCEPTION halt in .\editor_renderer.cpp,#189: marker.model_index!=NONE

SOLUTION: Normal.gbxmodel is corrupt. Sapien reads this for the object icons. (diamond with the arrows) Fix this by getting the file from a friend, or reinstalling HEK.

ERROR: EXCEPTION_ACCESS_VIOLATION

SOLUTION: You're being denied access to the SP maps. Back up your tag set and reinstall HEK. Then use HEK+ to **Recursively** extract the SP map.

ERROR:
### ERROR rasterizer_transparent_geometry_group_draw failed
### ERROR unsupported shader type

SOLUTION: Only known reason is you're trying to use xbox shaders.
If not, make a thread telling us what shaders you're trying to use.

ERROR:
Texture UV is jacked or there are verts not welded correctly. Import debug.wrl for area affected.
I'll try and continue radiosity calculations, but most likely the light map will be jacked because of this error.
radiosity error: degenerate triangle [or triangle with bad uvs] (see blue in error geometry)

SOLUTION: convert to mesh, vert mode, ctrl-A, and weld all with low value.

ERROR:
EXCEPTION halt in .\editor_persist.cpp,#392: pos+buffer_size<=size

SOLUTION: Your sapien.config file is Fubar, delete it. --- T3h_lag

ERROR:
08.06.06 16:57:57 DirectInput: 'Acquire (keyboard)' returned (DIERR_OTHERAPPHASPRIO#-2147024891) ...
EXCEPTION halt in \halopc\haloce\source\cseries\profile.c,#442: parent_timesection->self_msec >= child_timesection->elapsed_msec

SOLUTION: If you're running dual cores, change sapien's properties to only run on one.