Hi,
I tested some sequences on the HoloLens and think some sequences steps which are working on other devices (Android) still causes a problem on the hololens.:
- sequences generated with new versions of Creo Illustrate e.g. 4.1 or 4.2 but I suspect in same cases that the best results are achieved with the version 3.0 or 31.
- the pulse, and the shake effects, the unscrew and the fade out affects could causes very often problems when they are used in a step with more other effects. Mostly these effects will not work or will cause a wrong transformation of components. Therefore, such steps should be tested also on the end device
- some times problem occurs when the size of the thingmark does not have the correct size in mm and does not match the size of the scanned thingmark. Actually often this is used to have an additional scale of the model but this could cause problems for the correct display of the sequence steps
- On the HoloLens seems that is better to extract the .pvi file and to upload it to the project Upload directory explicitly ,especially when we want to change the figure via scripting
- in some cases, expectably on the HoloLense we can help with JavaScripts. For example for the door rotation we can use some script where we can move the rotation axis of hinge via relation (it is the Creo Defautl Csys is no coincident with the desired rotation axis) and use the setInerval function:
$scope.view.wdg[modelItem]['rx'] = angle1 ;
$scope.view.wdg[modelItem]['y'] = 0.0 - l_door*Math.sin(angle1_rad);
$scope.view.wdg[modelItem]['z'] = 0.0 - l_door*(1.0-Math.cos(angle1_rad));
So the sample code (tested on the holoLense device is the following)
// $scope, $element, $attrs, $injector, $sce, $timeout, $http, $ionicPopup, and $ionicPopover services are available
//$scope.app.params['virtual_slider1']=0;
var timerId = -1;
var down=false;
var g_door_angle=0;
var modelItemCounter=0;
var animate_model_items =
{
"modelItem-1": {
"angleIncrement" : 1,
"minAngle" : 0,
"maxAngle" : 90,
"timingInterval" : 20,
"duration" : 12000
}
};
$scope.app.playReset = function () {
if (timerId > -1) { clearInterval(timerId);}
down=false;
g_door_angle=0;
modelItemCounter=0;
};
$scope.app.playStep = function () {
// debugger;
var m_items=Object.keys(animate_model_items);
number_objs=Object.keys(animate_model_items).length;
if(modelItemCounter >= number_objs) return; //start new loop
{ console.log(" number_obj="+ number_objs);
console.log(" m_items["+modelItemCounter+"]="+ m_items[modelItemCounter]);
console.log(" object["+modelItemCounter+"]="+ animate_model_items[m_items[modelItemCounter]]);
$scope.testAsm(m_items[modelItemCounter],animate_model_items[m_items[modelItemCounter++]]);
}
};
////////////////////
$scope.testAsm = function (var_arg1,var_arg2) {
// var_arg1 modelItemVar
// var_arg2 modelItemObj
ray_call_interval_count=0;
if (timerId > -1) { clearInterval(timerId);
console.log("ClearInterval");}
timerId = setInterval( function ( modelItemVar,modelItemObj) {
//var current_angle = $scope.view.wdg[modelItemVar][modelItemObj['rx']];
if( g_door_angle <= var_arg2['minAngle']) down=false;
if( g_door_angle > var_arg2['maxAngle']) down=true;
$scope.$apply((function (a1,a2,a3) {
console.log("apply a1="+a1);
if(a3)
g_door_angle= g_door_angle - a2['angleIncrement'];
else
g_door_angle= g_door_angle + a2['angleIncrement'];
$scope.setAngle(g_door_angle,a1);
})(modelItemVar,modelItemObj,down) //apply inline function
);//applay funciton
console.log("call_interval g_door_angle="+g_door_angle);
}, var_arg2['timingInterval'],var_arg1,var_arg2); //end of interval
setTimeout( function () {
var a1=var_arg1; //arguments to inline function
clearInterval(timerId);
console.warn("started the timeoutfunction for "+ a1);
} , var_arg2['duration']);
};
/////////////////////////////////////////////////////
$scope.setAngle = function (door_angle,modelItem) {
var angle1=door_angle;// $scope.app.params['virtual_slider1'];
var l_door=0.999;
var angle1_rad=angle1*Math.PI/180.0;
$scope.view.wdg[modelItem]['rx'] = angle1 ;
$scope.view.wdg[modelItem]['y'] = 0.0 - l_door*Math.sin(angle1_rad);
$scope.view.wdg[modelItem]['z'] = 0.0 - l_door*(1.0-Math.cos(angle1_rad));
};
The coplete HoloLense Project is uploaded on this link
Hi Allan,
I did interpret you message only as comment and overlooked the second part. I
Yes this is an issue what we have to report. So ,could you please, provide asimple project which demonstrate the issue so I will report it to PTC R&D.
If this is to much work for you than, please, let me know , so I will prepare my version of a project.
For example I tested it with a my door model and the sequence (created with Illustrate 4.0, Pay attention that 4.2 is strongly not supported on HoloLens on Mobile the most things generated in Illustrate 4.2 seem to work for example mechanism animation !!! see animate1 and animate2) so in generally it was working on the HoloLens but did not follow exact the original sequence on the HoloLens (on a mobile device the same is working fine)
So some of the component are incorrectly shown by offset. I know that here the reason is using some shake and pulse effects. When I try to use ONLY! (transformations - rotate and translate) in this case the most things are working fine - also on HoloLens. But I had problems to fade out modelitems, so I used additional some scripts to make the modelitems invisible when new step event - so something like:
$scope.$on('newStep', function(evt,arg) {
console.debug("console.debug: $scope.$on -> newStep:".concat("started") );
var getStepRegex = /\((\d*)\//;
$scope.message = getStepRegex.exec(arg)[1];
...
// here is the $scope.message is string with the step number
// check it and decide which Items should be set to invisible
...
...
});
So according to the release notes for the new version that just came out (8.3.3.3744) sequences created in Illustrate 4.1 and above are now supported with the HoloLens. See here. Hooray! 
I've not had a chance to try it yet as I'm out and about and don't have the HoloLens with me, but I thought I'd post it here as I know there are a few people who have also encountered this problem and it looks like the developer I spoke to at LiveWorx who was working on the fix is done.
Hey Allan,
Good to know! I will be trying importing some sequences very shortly. I have no doubt that this will work, thanks for the heads up! It'll make life a little bit easier now too!!
Regards,
Brian
