More information:

It seems there are two distinct issues.

No1:

It seems like NatlinkStatus::getLanguage returns zzz, and reports this error:
getLanguage: Warning, no model specification string for key 2 1 found in "Base Acoustic" of inifile: C:\ProgramData\Nuance\NaturallySpeaking15\Users\josh\current\acoustic.ini

At first glance, this doesn't make sense, as the acoustic.ini file has this section:
[Base Acoustic]
2 1=UK English | BestMatch IV

The acoustic.ini file in DPI 14 had this section:
[Base Acoustic]
0 1=UK English | BestMatch IV
2 1=UK English | BestMatch IV

The 2 1 key seems to exist in both.

I've tried manually returning "enx" as the language instead of zzz, but it had no effect.

No2:

Enabling debug callback, I can see the following error whenever there's a recognition which has no effect:

Traceback (most recent call last):
File "C:\NatLink\NatLink\MacroSystem\core\natlinkmain.py", line 577, in beginCallback
(cbd, checkAll, checkForGrammarChanges)
natlink.NatError: A SRERR_VALUEOUTOFRANGE error occurred calling ISRResGraph::GetWordNode from ResObj.cpp 186.

I couldn't figure out much more about what this means.

Any ideas?

This, together with inabliity to change the microphone icon color and blank Command Browser reported in other posts, is reason enough to stick with DPI 14, unless and until fixes or workarounds are found. 

Switching back to Ver. 14 sounds a little drastic when you consider that you are giving up the Deep Learning engine and double speed dictation. You can easily eliminate the microphone color problem by using the new auto collapse Modern microphone icon view. Admittedly, we are having some issues with getting Dragon to recognize some of our personal commands because Dragon doesn't like abbreviations such as DS-7000 but we assume this is a bug that will be fixed.

-------------------------

Forum Mission Statement
Trial Downloads
Dragon/Sales@KnowBrainer.com 
(615) 884-4558 ext 1

 

At least for me, Natlink not working is a HUGE deal. Pretty much my entire workflow depends on it. I would switch back to 14 were it not for the very fast response by a natlink dev.

It's a huge deal for me, too. Did you get it to work? If so, how?

 

Not a bug, it's by design. Enter "DS 7000" as written form, and change the printed form under properties to "DS-7000".

 

-------------------------

No need to buy if all you want to do is try ...

DragonCapture KB Download (Latest)
DragonCapture Homepage

Nice catch Rüdiger. We hadn't considered these changes to be deliberate. For example, the only way we could get our DS 7000 Hyperlink command to work was to change its name to DS seven thousand Hyperlink; including applying lowercase to “seven thousand” because it didn't work in Title Case.

-------------------------

Forum Mission Statement
Trial Downloads
Dragon/Sales@KnowBrainer.com 
(615) 884-4558 ext 1

can you give some examples of non-recognized utterances?

The code looks like the problem might be an inadequately sized word buffer.