
Hell_Jumper_056
Joined: Jan 7, 2010
Halo: Accession
|
Posted: Mar 24, 2014 08:03 AM
Msg. 1 of 5
I finally got around to upgrading to OS. At first I didn't know why I hadn't done it sooner. Then I found out, that it rendered me almost completely unable to compile my map files.... So here's the error's:
tag data 'hs_syntax_data_definition' too large. failed to load... tag data 'hs_syntax_data_definition' too large. failed to load scenario tag 'levels\newmap2\newmap2' need to get the following tags:
### FAILED TO LOAD SCENARIO CAUSE I SUCK (tool plz, stahp)
I can load my maps perfectly in standard Sapien (still can't compile), but not OS. OS gives me this:
03.21.14 17:27:43 a hobo pc 01.01.00.0609 ---------------------------------------------- 03.21.14 17:27:43 reference function: _write_to_error_file 03.21.14 17:27:43 reference address: 401b13 03.21.14 17:27:43 Couldn't read map file './a_hobobeta.map' 03.21.14 17:27:43 *found 2 adapters... 03.21.14 17:27:43 CreateDevice succeeded with refresh rate = 0 03.21.14 17:27:44 Sound card doesn't meet minimum hardware requirements. Disabling hardware option. 03.21.14 17:27:45 Increasing sound decompression buffer size to 1048576 bytes 03.21.14 17:28:08 WARNING: 1 clusters in structure_bsp levels\newmap2\newmap2 have no background sound or sound environment. 03.21.14 17:28:08 local player 0, weapon (0x0), deleted unexpectedly
I spent 2 hours trying to figure out anything about OS's use, but found nothing. I checked the OS website, but it didn't help. It came with a program called 'Open Sauce IDE'. I have no idea what it does, and it didn't come with any description of what it's supposed to do. Any ideas? I really wanna work on Halo again...
Oh ya, there are no scripts in this map either. Edited by Hell_Jumper_056 on Mar 24, 2014 at 08:08 AM
|
|
|

kirby_422
Joined: Jan 22, 2006
Apparently public enemy number 1?
|
Posted: Mar 24, 2014 11:24 AM
Msg. 2 of 5
That's hobo's debug data... We want OS Sapiens debug data. Head over to <username>\My Documents\My Games\Halo CE\OpenSauce\Reports\debug.txt, and tell us what that says about OS sapien. Anyways, use os_tool rather than normal tool.
OpenSauceIDE applies OSHEK, compiles cheape definitions (changes what OSHEK can do. If you had made your own custom build of OS with new tag types ,you'd need to make a cheape that can edit those tags), and has a GUI for a tag extractor which isnt connected yet.
|
|
|

Hell_Jumper_056
Joined: Jan 7, 2010
Halo: Accession
|
Posted: Mar 24, 2014 12:53 PM
Msg. 3 of 5
I just reinstalled Halo and OS seems to be working. OS sapien seems to be working (I'm loving the faster radiosity time). But OS tool is giving me the same error that normal tool gave me. theres nothing in the debug that talks about OS tool, just OS sapien and how its working.
tool still gives me:
tag data 'hs_syntax_data_definition' too large. failed to load... tag data 'hs_syntax_data_definition' too large. failed to load scenario tag 'levels\newmap2\newmap2' need to get the following tags:
### FAILED TO LOAD SCENARIO
which I don't understand. I compiled the map, it worked, then I installed OS, then compiled again and then that error started and won't go away. I changed absolutely nothing in between the time before OS and after.
I've seen 'tag types' before, but I have been unable to find out what that means. Do you Kirby?
Thanks and what should I do next? Edited by Hell_Jumper_056 on Mar 24, 2014 at 01:02 PM
|
|
|

kirby_422
Joined: Jan 22, 2006
Apparently public enemy number 1?
|
Posted: Mar 24, 2014 01:36 PM
Msg. 4 of 5
Quote: --- Original message by: Hell_Jumper_056 I've seen 'tag types' before, but I have been unable to find out what that means. Do you Kirby? tag types directly refers to stuff like gbxmodel (the file extension, and what its for). New tag types OS brings are stuff like project_yellow_globals, shader_postprocess, etc) the hs syntax is the script area that its complaining about. OS does use a larger area for hs, which is why normal HEK would complain, although if you dont actually have any scripts in the map, os_tool with the normal build-cache-file should work fine. You used CMD to enter it, and wrote os_tool build-cache-file <whatever>, right?
|
|
|

Hell_Jumper_056
Joined: Jan 7, 2010
Halo: Accession
|
Posted: Mar 24, 2014 01:57 PM
Msg. 5 of 5
um... I didn't add the os_ at the beginning of tool... lmfao. I looked to see if there was an os_tool but i guess i originally missed, so I figured that the command wouldn't need to be changed. Thanks for everything again kirby!
|
|
|
| |
|
|
 |
|