Hi Bryan,

I hope that I am not talking out of place.

 

Although I have yet to purchase a voice-based version, and therefore don't have access to the installation processes, it seems that some are having problems with voice navigation with the software.

 

Perhaps a simple test procedure or improvement on existing would enable users to ensure they can use the product basics more easily?

Although I have yet to purchase a voice-based version, and therefore don't have access to the installation processes, it seems that some are having problems with voice navigation with the software.

 

I've been making voice programs for a long a time.

 

The only problems are:

 

1. They don't have their speech recognizer to English - US (but that won't be a problem since you have an English version of Windows, even if it's the Brit version).

 

2. The occasional user has run System Mechanic, which mucks up Windows speech recognition for 3rd party people. That's out of our hands. They usually fix it by re-installing their OS. I always tell people to avoid running those system cleaners, etc. They often do more harm than good.

 

3. The occasional user will just have a bad microphone.

 

But check this out anyway... it'll show you how to setup voice.

 

http://www.support.fs2crew.com/help/manuals/default.aspx#pageid=speech_recognition_setup

 

 

 

Reported issues with voice control itself are actually very rare, which is surprising given its complexity.

 

Remember these are support forums. 95 percent of our users will never post here because they have no have issues.

 

Cheers,