Sliptip on 14/9/2013 at 11:13
I've been trying to add a new voice schema and I keep getting this in monolog:
Speech token not found for finding flags.
Speech token not found.
Speech token not found.
Speech token not found.
Speech token not found.
INFO: total schema tag count 45 , concept count: 124
INFO: total schema tag value (/ tag state) count 245 (of max 255)
The voice did at first seem to load correctly, until I had to reboot my computer afterwhich the gamsys file wouldn't load at all.
I'm just wondering does anyone know what those errors mean? :confused: I added the voice to the SPEECH.SPC and I can see it under the voice archetype.
LarryG on 14/9/2013 at 15:42
I had that happen to me too after rebuilding schemas a month or so back.
Speech token not found for finding flags.
Speech token not found.
Speech token not found.
Speech token not found.
Speech token not found.
INFO: total schema tag count 45 , concept count: 126
INFO: total schema tag value (/ tag state) count 254 (of max 255)
The end result of this for me is that the OM sounds associated with SwitchType LvFloor2 no longer play with my rebuilt schemas. The sound is fine, and a previous build (2 years older) of the schemas works fine. I suspect that I have run out of tokens, and the DromEd bus driver won't let some schemas onto the bus for lack of tokens.
Looks like sNeaksieGarrett is also having the same issue: (
http://www.ttlg.com/forums/showthread.php?t=124359&p=2204728&viewfull=1#post2204728)
kdau on 14/9/2013 at 18:53
There's a little-mentioned nuclear command, destroy_sound, which erases everything under the Voice and Schema archetypes. Assuming it wipes out the underlying databases as well, a destroy-and-reload might work around this kind of problem, or at least give a more useful error message. The (giant) drawback is that it also gets rid of any properties in the Schema tree that aren't loaded from the schema files (e.g. Attenuation Factor). :erg: Those could be restored manually or by a cleverly arranged DML. So FWIW, if you're ultra-desperate, that option is there, at least to be tested non-committally.
LarryG on 15/9/2013 at 00:10
I might try that. I didn't realize that there was anything not included in the schemas. Attenuation Factor you say? Any others?
I used the Query function of NewDark on Attenuation Factor, and it doesn't look insurmountable to key that in by hand.
[ATTACH=CONFIG]1797[/ATTACH]
kdau on 15/9/2013 at 00:53
Actually, now that I look in more detail, I'm pretty sure that's the only property that isn't in the files. Heh, I figured there would have been more. It's a good thing the list is short, though, because I just remembered that DMLs don't take object names (only numbers, which would change on reload) so manual keying is the only option.
The Play Params and Loop Params properties (the main ones that are loaded from the files) have a lot of flags, some of which don't seem to correspond to anything in the files. It's possible that some of those bits are set in the gamesys, with the reload algorithm keeping them intact. If so, those would be lost with a full wipe. I don't have a clean setup to test this on at the moment, but it seems intuitively unlikely. (Like that ever counts for anything in DromEd...:laff:)
Sliptip on 15/9/2013 at 09:41
This is great actually. I've been meaning to get around to wiping out all those old schema archetypes that S7 will never need!
Having done that though, the warnings still persist. It seems to still be working, so normally I wouldn't care except that when I woke up yesterday none of my mis files would even open. Monolog had all kinds of speech token errors :( . . . fortunately I back up my gamsys file regularly!
One word of warning about destroy_schemas though, you'll also be deleting any sound description links you may have!
R Soul on 15/9/2013 at 13:21
Some schemas also have the property AI > Utility > Sound Value, which is used to state that the schema (and its children) should alert nearby AI. There's an audo_class parameter in the schema files that might set that property, but I haven't checked.
If you upload your schema files someone might be able to track down the error.
R Soul on 16/9/2013 at 21:17
I had a look at LarryG's schemas and found the cause of the error.
In Envsound.spc, one of the tag lines had been commented out because there is an overall tag limit of 256.
The line was this:
//tag WardType AirWard FireWard EarthWard WaterWard StatueMgE StatueMgA StatueMgW StatueMgF
The problem here is that there is no longer a tag called WardType, but there are references to it in the schema files. The easiest solution is to remove the // from the above line at put them after WardType:
tag WardType// AirWard FireWard EarthWard WaterWard StatueMgE StatueMgA StatueMgW StatueMgF
The other way is to find the ward schemas and delete them (or comment them out, or remove the reference to the WardType tag).
LarryG on 16/9/2013 at 22:15
And it worked to fix things, too! I had to get rid of some other tags to drop down below the threshold (curse you 255!), but I did it.
Thanks LOTS RSoul!!
Sliptip on 17/9/2013 at 01:39
Well here are my schema files:
(
http://www.strain7.com/uploads/1/8/3/0/18302951/s7schemas.zip)
If anyone has a chance to look at them I'd really appreciate it!!
I looked for entries like the ones you mention RSoul, but the only "//" lines in the ENVSOUND.SPC that I found didn't fix the problem when I un-//'d them.
I suspect I'm going to have to pick through these really carefully to find the culprit, so if anyone does have a look at these don't spend too much time!
