
ptowery
Joined: Aug 28, 2007
oify
|
Posted: Nov 30, 2012 11:44 AM
Msg. 1 of 3
trying to run tool build-cache-file What does it mean if tool should be returning with this: tag data 'hs_syntax_data_definition' too large. failed to load scenario tag 'levels\test\banshees_tmap\banshees_tmap' tag data 'hs_syntax_data_definition' too large. failed to load scenario tag 'levels\test\banshees_tmap\banshees_tmap' need to get the following tags:
### FAILED TO LOAD SCENARIO.
Cache pack file bitmaps hits: 0 for 0.00M Cache pack file bitmaps adds/misses: 0 for 0.00M Cache pack file sounds hits: 0 for 0.00M Cache pack file sounds adds/misses: 0 for 0.00M Cache pack file loc hits: 0 for 0.00M Cache pack file loc adds/misses: 0 for 0.00M
But it returns with this: Failed to read data file header bitmaps ### FAILED TO OPEN DATA-CACHE FILE.
Failed to read data file header sounds ### FAILED TO OPEN DATA-CACHE FILE.
Failed to read data file header loc ### FAILED TO OPEN DATA-CACHE FILE.
### FAILED TO LOAD SCENARIO.
Cache pack file bitmaps hits: 0 for 0.00M Cache pack file bitmaps adds/misses: 0 for 0.00M Cache pack file sounds hits: 0 for 0.00M Cache pack file sounds adds/misses: 0 for 0.00M Cache pack file loc hits: 0 for 0.00M Cache pack file loc adds/misses: 0 for 0.00M
And for sure nothing is wrong with the source files, it's on tool's end. Edited by ptowery on Nov 30, 2012 at 11:47 AMEdited by ptowery on Nov 30, 2012 at 11:48 AM
|
|
|

kirby_422
Joined: Jan 22, 2006
Apparently public enemy number 1?
|
Posted: Nov 30, 2012 12:10 PM
Msg. 2 of 3
First one, you've made a scenario (or, updated the scripts in sapien) with part of OSHEK.
Second one, you're using a mod-set with OS_tool, and are giving it invalid options.
|
|
|

ptowery
Joined: Aug 28, 2007
oify
|
Posted: Nov 30, 2012 12:54 PM
Msg. 3 of 3
Quote: --- Original message by: kirby_422 First one, you've made a scenario (or, updated the scripts in sapien) with part of OSHEK.
Second one, you're using a mod-set with OS_tool, and are giving it invalid options. Okay, I'm running a command through tool, and I am wanting to get the os error seen in the first window but what I get is what's in the second window. I want to know what instance something like that would happen. I should always get the Error in the first window. But I get the error seen in the second Window.Never mind, I had to manually set Tool's working directory. Edited by ptowery on Nov 30, 2012 at 01:16 PM
|
|
|
| |
|
|
 |
|