Not compatible with World of Warcraft 11.1.0

[Wanny]

This worked flawlessly with World of Warcraft up until the actual standard release (11 0.7), but I'm testing version 11.1.0 and it makes the game crash.

Checking the Errors folder, the txt file says this;

---

<Exception.IssueType> Exception
Crash
Exception.Summary:
0xC000008E (FLT_DIVIDE_BY_ZERO) at 00007ffb91a3a4c9
(DBG-OPTIONS DBG-ADDR<00007ffbe39822f9>("sapi.dll") <- DBG-ADDR<00007ff6f037e035>("WowT.exe") <- DBG-ADDR<00007ff6f0362cb6>("WowT.exe") DBG-OPTIONS<>)

---

When I saw sapi.dll I knew what's going on. Uninstalling the adapter stops the game from carashing

[BelegCufea]

Seems to be fixed in 11.1.0.58999.

Moreover, it worked with ONLY Online (Edge) voices enabled in previous versions (Narrator natural voices disabled).
But let's hope Blizz will not break it again in next version or on release ...

[BelegCufea]

FYI Works fine in release of WoW 11.1.0(59466).

Can be closed AFAIK.

[eltreum0]

Seems to crash again on 11.1.7 (60520) PTR and Mists of Pandaria Beta

disabling local narrator voices also fixes it like mentioned before

[gexgd0419]

I want to know the current status with the latest version.

[eltreum0]

seems to work without a problem in world of warcraft 11.1.7

[lemieszek]

back to issues with 11.2

[JyanseiCoding]

can confirm, not working in 11.2

[gexgd0419]

Could you provide more details about it? For example, error logs, or dump files?

Could you confirm whether this still happens with the latest release version v0.2.6?

[lemieszek]

I went through SAPI & WoW logs and found nothing. My guess is this time it is on Blizzard side, they only list "native" voices:
But my voices options all inconsistent all over the system 😅

More info

Adapter	TTS App	Voices
Windows Speech Settings	Windows Narrator Settings	Windows Speech Properties

World of Warcraft:

C_VoiceChat.GetTtsVoices()
[1]={
  voiceID=0,
  name="Microsoft Hazel Desktop - English (Great Britain)"
},
[2]={
  voiceID=1,
  name="Microsoft David Desktop - English (United States)"
},
[3]={
  voiceID=2,
  name="Microsoft Zira Desktop - English (United States)"
}

I've submited bug request to Blizzard, lets see.

[Kalrell]

Hi I noted this issue with the current World of Warcraft release, 11.2. release build 62438.

Initially I thought it might be down to not updating this adapter in forever, but I can confirm this still happens with the latest release version v0.2.6.

As above, voice lists seem inconsistent across the system.
But I'll post mine for completeness.

Windows Speech and Narrator seem the same.
But Time & Language, and World of Warcraft have different voice lists.

Speech Properties

Narrator Settings

Time & Language Settings

World of Warcraft Text to Speech Config

Hope this is useful, however I fear it might be game related and upto Blizzard to fix instead of you fine folks.

[gexgd0419]

Starting from v0.2.4, offline Narrator voices will no longer be loaded into Narrator itself on Windows 11, or specifically, Narrator.exe and SystemSettings.exe. Because Narrator on Windows 11 already supports natural voices on its own, and loading another natural voice library can cause some problems. For online voices, and on Narrator on Windows 10 or earlier, nothing is changed. Not sure if this problem has to do with this feature. You can try if this problem happens with v0.2.3 or earlier version.

The Speech setting in Time & Language Settings lists only OneCore voices. As this adapter does not support OneCore, it's not listed.

[BelegCufea]

Sadly, it seems Blizzard has completely cut this program off in WoW. None of the versions I tried work (tested v0.2.6, v0.2.5, v0.2.3, and even v0.1).
The SAPI voices are clearly installed correctly, as they appear and work in the included TTS application (as mentioned above in Kalrell’s post).

It may be because of the frequent crashes during PTR phases, with players reporting them to Blizzard without realizing they were caused by NaturalVoiceSAPIAdapter incompatibility. :-(

I tried looking through multiple logs to find more information about where the problem lies, but unfortunately with no success. Since I don’t think gexgd0419 plays WoW, we seem to be doomed. It was nice while it lasted.