Talus Speech -- NWNXFFspeech.dll And Me

[Blacksting]

I have been wanting to get away from NWNX-FF forever and I just can not seem to. My last hurdle is to get the NWNXFFspeech.dll to work with NWNX2 (2.5). Has anyone used Talus (that is the base for the speech dll) with NWNX2? If so what is your solution?

[Manuel]

Talus was designed specifically for use with NWNX. I've never used FF but I'm guessing he just took the WinPcap dlls which are needed for Talus and renamed them.

Why not just download and install the original version?
http://nwvault.ign.com/Files/scripts/data/1076555382000.shtml

It's not difficult to setup and I've played on several NWN servers that use NWNX and Talus together.

[Blacksting]

The FF version does not even use database calls to "store" the chat. It is held internally by NWNX which means you can run the NWN script function at less than a second for each SPEECH call without even taxing the system. It also automatically configures for a network card and is a .dll attached to NWNX (no separate exe running which is great for "automated" server reboots.) I could go back to using what is analogous to the stone age from the iron age but I am trying to bring NWNX 2.5 in to the iron age .

[JeroenB]

I you are comfortable with it you might want to translate the talus sources to a NWNX plugin Than you have the same functionality but then completely in one plugin. I would think about using a thread in which you keep track of the communication.

[Manuel]

[Blacksting]

Thankfully all the heavy lifting has been done already. The FF source code IS Talus written for direct communication with NWNX. Unfortunately, Fast French acting the way he does, made the plugin incompatible with the official NWNX. What my job will be (or maybe someone closer to "official") is to find out what differences FF code has and fix them so the FFSpeech.dll compiles and works correctly with NWNX2 (and someone official may have a better chance of seeing those differences quicker than I.) Right now it loads as a module fine. The choosing of a NIC works just fine. It does not "sniff" anything though with NWNX2. Nothing is sent to the log.

[JeroenB]

If you can send me the sources then I might have a look at it.
Email: jeroen@nwnx.org

[Blacksting]

http://nwvault.ign.com/Files/other/data/1057237614460.shtml

[Blacksting]

Since the new odbc probably uses changes to the madhook (why the name change?) this could possibly be the "difference" that FF and NWNX2.5 have at the moment since FF still uses the old mad hook lib.

[JeroenB]

This was my first look ever at FF's code. It looks horrible

I think I can better rewrite the complete module with input fom the original Talus Listener source code. That will be an easier and better way to go I think.

[JeroenB]

You guys mind if it just uses the database? That way I can leave Lanthar's code as much intact as possible. But if you really insist, I can have a look what I can do.

[JeroenB]

Look here

[Manuel]

Damn. You fellas are fast.
_________________
I only know enough to be dangerous.

[Blacksting]

I like running the "does speech exist" check at about 0.2 seconds. Having the database calls probably means I have to bump that up to at least 1.0 seconds. This does not cause a huge burden but I probably will head down the road of making the whole process internal. The way FF does it is by concatenating the sniffed packet data to a global buffer. Then OnRequest dumps that buffer back to NWN.

In any case... at the moment... the nwnx_speech.dll crashes every time. Am I the only one that is having this problem?

[JeroenB]

Are you sure you are using the right network interface? Like I suggested in the documentation, you should start up Talus Listener and see what number you should put in the configuration file. If the error still comes back, please show me the contents of the nwnx_speech.txt file in your log directory.