DOE: Sound Extension

[heyhogan]

Hello !
Trying to get all my extensions setup again for the new FG 3.2. I am having issues with the most excellent sound extension. I have downloaded the new extension (and base) and have just those two turned on. Did get the message

"Ruleset Error: subwindow: Could not find windowclass () for control (swSoundSetupList) in windowclass (wcSoundMasterListsWindow)
Ruleset Error: subwindow: Could not find windowclass () for control (swMiniBoardList) in windowclass (wcSoundMasterListsWindow)
Ruleset Error: subwindow: Could not find windowclass () for control (swAutoSoundList) in windowclass (wcSoundMasterListsWindow)
Ruleset Error: subwindow: Could not find windowclass () for control (swChatSoundList) in windowclass (wcSoundMasterListsWindow)
"
when I had all the DOE stuff turned on (but I am not sure all were updated).

With just the two (base and Sound) turned on, it looks like its working but will not trigger any sounds. Any suggestions on what to do next?

[dulux-oz]

Two issues there:

1) Yes, you don't have all the DOE's updated to their latest versions.

2) Have you turned on the Sounds option in the FG Options Window? (and read the documentation )

If these don't work let me know and we'll get things sorted for you

Cheers

[heyhogan]

Dulux-Oz:

Thanks. I decided to go over the documentation again (I had looked at the old file, not the new one) and noticed the Options setting. That was it. Works now. Thanks! FYI - I am updating the Savage World Supplement and will put a link to your sound extension in the next version of this documentation.

Cheers.

[Salva]

Hi Dulux, im experiencing an issue with the Chat sound.
It looks like it is not linking correctly. Like merging one configuration with the last one.
Happened twice. The first time i had to delete and redo the configuration of the sound.
Pl look at this video:
https://www.dropbox.com/s/l8xo2bbtpr...ure-5.mp4?dl=0
Thank you

[dulux-oz]

@Salva: I'm pretty sure your issue is coming from the "*" in the first Sound Trigger - as I've said in a previous post, the character recognition system isn't that sophisticated and we already know it doesn't like "[", "]", "(" and ")".

Try it without the "*"and see how you go

Cheers

[Salva]

@Salva: I'm pretty sure your issue is coming from the "*" in the first Sound Trigger - as I've said in a previous post, the character recognition system isn't that sophisticated and we already know it doesn't like "[", "]", "(" and ")".

Try it without the "*"and see how you go

Cheers

No luck
https://www.dropbox.com/s/bdpze1gicz...ure-1.mp4?dl=0

Actualization: I deleted all the Chat Sounds and make them all again and seems its working now.
Question: Can you link one chat sound to various different Triggers. In other words: can you have more than one Chat Sound with the same sound string but different Triggers?
Thank you very much

[dulux-oz]

Can you link one chat sound to various different Triggers. In other words: can you have more than one Chat Sound with the same sound string but different Triggers?

Yes, you can, as each ChatSound Entry is a separate record - in the same way that each Character Sheet is a separate record. You can link the same Longsword (Item) record to more than one character, so you can have the same SoundString in more than one ChatSound Entry.

But if you are trying to get two sounds to trigger off the same piece of ChatBox text then no, it won't work, because each ChatBox piece of text is treated as one "thing" and is scanned for the first matching ChatSound Entry - once the system finds a match it stops searching, so one of the Chatsounds will be triggered but not the other(s).

[Salva]

Nice. I had accomplished that and also to make "*string" works but with issues as you know so i wanted to know if there will be any conflict in doing so.
Thanks

[dulux-oz]

Hi Everyone,

I've just placed a new version of the DOE: Sound Extension into the first post (v2.1). This version should help with some of the issue that have been reported around extra AutoSound Entries being created and the ChatSound String recognition code has also been reworked - it now successfully recognizes characters such as "[" and ")".

The ChatSound system now also matches on the longest strings first, so you can have (for eg) "Hit" and "Critical Hit" as ChatSound Triggers and they will be matched correctly (previously sometimes "Hit" would match against "Critical Hit" which, why correct, was not waht we wanted).

As normal, if you find any odd behavior then please let me know

Cheers.

[Trenloe]

The ChatSound system now also matches on the longest strings first...

Nice.