A Community discussion forum for Halo Custom Edition, Halo 2 Vista, Portal and Halo Machinima

Home  Search Register  Login Member ListRecent Posts
  
 
»Forums Index »Halo Custom Edition (Bungie/Gearbox) »Halo CE Technical / Map Design »My test map isn't building correctly in tool

Author Topic: My test map isn't building correctly in tool (2 messages, Page 1 of 1)
Moderators: Dennis

Sargent 0
Joined: Nov 21, 2017

Accurate Depiction of me. ↑


Posted: Nov 23, 2017 12:18 AM    Msg. 1 of 2       
ok so i spent like an hour making the test map. I built my map in tool and it doesnt show up in the game. (I ran everything in admin btw) tool said that some custom weapons and hud didnt build properly. I think this affects how my test map doesnt show up in game. heres the output
>
C:\Program Files (x86)\Microsoft Games\Halo Custom Edition>tool build-cache-file levels\test\tutorial\elite
Couldn't read map file './toolbeta.map'
crosshair item 0 for weapons\battle_rifle\battlerifle references an invalid sequence
crosshair item 0 for weapons\dual_smg\dual_smg references an invalid sequence
crosshair item 0 for weapons\gravity_rifle\gravityrifle references an invalid sequence
crosshair item 0 for weapons\spraycan\can references an invalid sequence
crosshair item 0 for weapons\spraycan\can references an invalid sequence
the meter definition ui\hud\cyborg shield does not specify a stencil bitmap group.
the meter definition ui\hud\cyborg body does not specify a stencil bitmap group.
culling uncompressed model vertices...done
culling uncompressed structure bsp vertices...done
culling uncompressed model animation data...done
building predicted resources for structures...done
structure bsp 'levels\test\tutorial\tutorial' is 0.26M
tag headers and names are 0.21M
streaming model vertex and index buffers...done
streaming tags...........................done
writing vertex and index buffers...done 9.63M
writing tags...done (2740 tags for 6.68M)
total tag size is 6.94M (16.06M free)
compressing 27.29M...done
successfully built cache file.
Cache pack file bitmaps hits: 828 for 39.53M
Cache pack file bitmaps adds/misses: 114 for 6.14M
Cache pack file sounds hits: 676 for 12.94M
Cache pack file sounds adds/misses: 246 for 4.69M
Cache pack file loc hits: 104 for 0.22M
Cache pack file loc adds/misses: 0 for 0.00M
<

also whenever i try to open halo as a regular user, a pop up says "prepare to drop; failed to find stock bitmaps, sounds, and or loc data files" Dont know whats wrong. None of my tags are corrupt(I just have vanilla ce tags) and I dont have any corrupt maps. All of my resource maps have the same amount of storage before this was happening.


Isxz
Joined: Apr 14, 2013

MrChromed


Posted: Nov 24, 2017 12:26 PM    Msg. 2 of 2       
Let's see this by parts (this is gonna be a little messy, but I hope you can understand this):

- The "references an invalid sequence" issue is, at some point, a common mistake that someone commit if it's not very familiar with the way "bitmap indexes" work. Open a .weapon_hud_interface from a weapon and go to the "CROSSHAIR" section. You'll see that there's a bitmap located in the "Crosshair bitmap" field. Open it and see how many "Sequences" it contains.

For example, I'll look into the original crosshairs from H1, which is located in "ui\hud\bitmaps\combined\hud_reticles". If you look into them, it contains 14 sequences/indexes, counted from 0 to 13. The first sequence (the 0) contains 4 crosshairs/textures (in the image bellow, some of them are hidden due to the opened tabs), so we can tell that the .bitmap contains 17 textures (ergo, indexes).



In the "CROSSHAIR OVERLAYS" sub-section, you'll see an option called "sequence index". As we saw before, we can reference a max. of 17 crosshairs (in "index terms", from 0 to 16). If you put "17" and compile, you'll get the following error:

#17 is not a valid bitmap_group_sequence_block index in [#0, #17>

That's because you surpassed the max "length" and the engine thinks you're trying to say that #17 is "17", but you can only count to 16. Just like an array in a programming language! BUT, if you put something like 18 or beyond and them compile it, you'll get this error:

crosshair item 0 for weapons\assault rifle\assault rifle references an invalid sequence.

And that's because you're trying to "call" to a index that doesn't even exist. And that's the issue you're having right now with some of your weapons' HUD interfaces. Check the .weapon_hud_interface of all of your troubled weapons and check how many crosshairs or indexes their textures contain. If every interface contains only 1 texture/crosshair, you need to put "0" in the "Sequence index" field.

--------------------------------------------------------------------

- The "the meter definition for..." issue is something you don't need to worry about. It's something related to leftovers from early and old versions of the shield and health meters from the cyborg's HUD. There was a time which they (Bungie) didn't put those elements in a .unit_hud_interface as we know it today, but in an old tag system called ".meter". In case you want them just to see those messages dissapearing from your cmd window, here you have them (replace files and folders in case you need to):

https://www.mediafire.com/file/j92qhj349501gbj/Cyborg%27s%20shield%20and%20body%20meters%20%28H1%20leftover%29.rar

--------------------------------------------------------------------

As for the "Prepare to drop!" issue, that's something related with Open Sauce. You could reinstall it and see if that issue disappears. I can't really help that much with that, sorry.

--------------------------------------------------------------------

If your map isn't showing up in-game, it could mean that your map isn't located in the "maps" folder somehow. For some reason, you're not having full admin privileges, so your map is probably located here:

C:\Users\user name\AppData\Local\VirtualStore\Program files\Microsoft games\Halo Custom Edition\maps . You need to search on the Internet how to show up hidden folders, since "AppData" is a system's hidden folder. Anyways, you can look into this old thread to understand your problem: http://forum.halomaps.org/index.cfm?page=topic&topicID=46138

--------------------------------------------------------------------

And that's all from my part. I hope you understood something. Feel free to ask anything related to this in case you need to know something more
Edited by Isxz on Nov 24, 2017 at 12:29 PM
Edited by Isxz on Nov 24, 2017 at 12:31 PM

 

 
Previous Older Thread    Next newer Thread





Time: Sat December 16, 2017 3:53 PM 219 ms.
A Halo Maps Website