Hi @Sandy_Gunner ,
I checked the reported issue to PTC R&D and see that related issue were reported and R&D is aware about this requirements but after deep check - there are currently some plans for improvement and development - but they are not classified as urgent because according to R&D team there are currently sufficient techniques to work around with loud enviroment.
2 strategies' to improve the current behavior in the current release:
>> R&D statement about how to use better the voice command:
There is no specific improvements that can be made for the HL voice command recognition. Some further information:
- The log shows low recognition quality on some of the basic key phrases, this could be an indicator of several things: Unusual pronunciation by the user, noisy environment that causes trouble for the microphone, or a faulty device.
- Custom voice commands might have lower confidence than the standard key phrases so it might help to test out variants that fit the user pronunciation and are easier to recognize for the HL.
- In general the voice recognition Microsoft provides on the HL is not on the same level as the current services from the Google Assistant or Apple’s Siri. This might lead to a higher expectation than the device can deliver.
>> Design ;
- so when you start on HL2 , then the view app will go by default to scan mode - scan thingmark or QR code to open a project
- the project have a start View where you have buttons to navigate -you can use the mentioned api:
- app.fn.navigateToScanMode() to navigate back to scan mode
- $scope.app.fn.navigate(View_name) to navigate between views e.g. :
//navigate to Home view
$scope.app.fn.navigate('Home');
// navigate to View named CHAR2DVIEW
$scope.app.fn.navigate('CHAR2DVIEW')
- window.open(url) e.g to open an experience:
$scope.openUrl=function()
{
// let url= "https://www.bing.com/"
let url="https://xxxxxxo.studio-trial.thingworx.io/ExperienceService/content/projects/bla/index-desktop.html?expIndex=0#/Home"
window.open(url)
// some related points
// window.inf.allowIntent(url)
// window.location = url
}
- Here also statement from the R&D team to the last issue reported this year "Discovery and Development of voiceless command alternatives for HoloLens" - some point are already implemented further are under dev and possibly will come next.
- Description:
As a second step in offering alternative ways for navigating in the View app using HoloLens, the task is to couple the system navigation logic with buttons (until now it was solely voice commands). It is still a partial integration, meaning further improvement with long-range plan
- Scope of dev
Based on the developments from reported Ticket w: Investigate Microphone setup for Voiceless commands
, the process should cover further steps:
//I think this is planed improvement below I did not check if this is already part of the current 9.15 functionality /did not tested yet
Attach customers expected functions to the created buttons:
Library - Opening Library and its content
Downloads - Showing experiences that got downloaded to the device from the Library
- NOT Scope
Within above sections, all Experiences should be presented as buttons, that upon being clicked, open the experience. When opening the experience, hide the selector menu Within the experience, show a button “Close” which leads back to the originator menu (Library / Downloads) serving as a “Back” button - not required
- Implementing a floating panel - this is already down
- Implementing a hand gesture as main trigger
- Final UI design
- Idea: Use a floating panel for the buttons
Logic:
Step 0: Deactivate Microphone (or make sure that it is deactivated)
Step 1: Open View App
Step 2: Scan specific QR Code that triggers the functionality
Step 3: Once you close the app, functionality is automatically disabled
