what makes sequence took long time to load on HoloLens?

[nqwifly]

I've created animated sequence using Creo illustrate consists of 20 steps. I've managed and controlled the model transparency via Creo, such that I made all the parts transparent except for the animated one. It worked perfect as expected in preview, mobile and HoloLens. Only one issue appear in hololens, it took long time to load sequence, about 30 seconds! (in mobile phone takes a second).

Why it'd take that long time? how to reduce this time? the only option I have now is to download the experience to offline, which will cut the time to the half. but what if I want it online?

Any help or recommendations?

Thanks

[whity]

Did you apply the cad-optimizer? You recieve 4 Versions of the pvz-file. The ones you don't need should be deleted because they are downloaded every time the experience is loaded.

[nqwifly]

Yes, I used the lowest quality deleted the other ones. 30 seconds took for the low quality one to load.

[whity]

Then maybe your model is too big. How many megabytes does it have? You could try to remove parts that you don't need.

[nqwifly]

The PVZ file is 319 KB, I believe this consider as small. can I remove parts via Creo illustrate?

[whity]

This is indeed very small. Seems like the renderer of the HoloLens has an issue with the oppacity. Maybe you should ask PTC for help.

@RolandRaytchev : Has PTC experienced this issue? The HoloLens needs 20 seconds to load an a pvz that is 319KB. There are transparencies made in Creo. The tablet version of the experience loads much faster.

[nqwifly]

Thanks Whity to raise the issue.

I've just made a test on Javascript to printout the performance time the model sequence takes to load.

var t0 = performance.now();


$scope.$on('modelLoaded', function(){
var t1 = performance.now();
$scope.app.view.Home.wdg["3DLabel-1"]["text"] ="model loaded: "+(t1 - t0);
});


$scope.$on("sequenceloaded", function (evt, arg) {
var t2 = performance.now();
$scope.app.view.Home.wdg["3DLabel-1"]["text"] ="sequence loaded: "+ (t2 - t0);

});

model loaded: 2555

sequence loaded: 18651

[RolandRaytchev]

Hi @whity,

I could not find any general issues for the HoloLens related to load time .  

And I do not think that the issue is related to model size but it could  related to pvi sequence or to the textures.

So maybe we can test, where we will remove in Creo illustrate the figure and then see what the loading behavior  – if it is better or not. If it is still not performant enough for such small model – so problem is reproducible, then we could have some issue with the model- e.g. texture etc.  So far I know there is currently an  issue with the texture display on the HoloLens as reported in the  post In this case we can try to simplify the model by removing of textures or components. It is possible that there is component with wrong geometry or we have an error in the structure where the HoloLens render is more susceptible to such errors, but in this case,  we have to check more detailed the particular model (pvz)

Also, it is possible that the issue is causes by the sequence. There is often sequences which are working in preview and on other mobile devices but they are not correctly played on the HoloLens. I had a case with model (pvz) which has very complex pvi -(containing very long sequence)  where we have some loops on loading and it take a very long time but in generally  the problem occurs already in the preview mode

[nqwifly]

Thanks for the reply. During the day I can pinpoint two observations:

- LoadSequence time varies, sometimes it takes up to 20 seconds and other times takes 10 seconds.

- I indeed observed weird behaviour in animation between preview and HoloLens, one of the parts should be transparent and it didn't. It kept shown to the end. (can this be resolved?)

I'll try a pvz file without sequence inside and will let you know.

[nqwifly]

Hi @RolandRaytchev 

I was checking the log file for another issue and found that, is it normal?

could be "Error: No sequence found in pvi" cause the delay?

2019-04-30T20:43:52.410+03:00 [Debug] javascript - No sequence found in pvi.
2019-04-30T20:43:52.411+03:00 [Debug] javascript - pvidoc is...
2019-04-30T20:43:52.418+03:00 [Debug] javascript - <parsererror xmlns="http://www.mozilla.org/newlayout/xml/parsererror.xml">XML Parsing Error: syntax error</parsererror>
2019-04-30T20:43:52.419+03:00 [Debug] javascript - js animation engine - parse sequence failed: 
2019-04-30T20:43:52.419+03:00 [Debug] javascript - Error: No sequence found in pvi.
2019-04-30T20:43:52.421+03:00 [Debug] javascript - Error: No sequence found in pvi.
   at parseSequence (https://****I removed the link****/extensions/js/sequence.js:171:13)
   at request.onreadystatechange (****I removed the link****/extensions/js/sequence.js:249:25)
2019-04-30T20:43:52.426+03:00 [Debug] sequence - Loading and parsing pvi [****I removed the link****/content/projects/genskill%20manual/app/resources/Uploaded/PFCU_Low/l-Creo%203D%20-%20PFCU.pvi]
2019-04-30T20:43:52.427+03:00 [Debug] default - trying to download [****I removed the link****/content/projects/genskill%20manual/app/resources/Uploaded/PFCU_Low/l-Creo%203D%20-%20PFCU.pvi]
2019-04-30T20:43:53.275+03:00 [Debug] sequence - Now parsing step: [1] of [19]
2019-04-30T20:43:53.276+03:00 [Debug] sequence - Now parsing step: [2] of [19]
2019-04-30T20:43:53.380+03:00 [Debug] sequence - Now parsing step: [3] of [19]
2019-04-30T20:43:53.489+03:00 [Debug] sequence - Now parsing step: [4] of [19]
2019-04-30T20:43:53.546+03:00 [Debug] sequence - Now parsing step: [5] of [19]
2019-04-30T20:43:53.578+03:00 [Debug] sequence - Now parsing step: [6] of [19]
2019-04-30T20:43:53.604+03:00 [Debug] sequence - Now parsing step: [7] of [19]
2019-04-30T20:43:53.626+03:00 [Debug] sequence - Now parsing step: [8] of [19]
2019-04-30T20:43:53.645+03:00 [Debug] sequence - Now parsing step: [9] of [19]
2019-04-30T20:43:53.859+03:00 [Debug] sequence - Now parsing step: [10] of [19]
2019-04-30T20:43:54.088+03:00 [Debug] sequence - Now parsing step: [11] of [19]
2019-04-30T20:43:54.113+03:00 [Debug] sequence - Now parsing step: [12] of [19]
2019-04-30T20:43:54.132+03:00 [Debug] sequence - Now parsing step: [13] of [19]
2019-04-30T20:43:54.178+03:00 [Debug] sequence - Now parsing step: [14] of [19]
2019-04-30T20:43:54.199+03:00 [Debug] sequence - Now parsing step: [15] of [19]
2019-04-30T20:43:54.235+03:00 [Debug] sequence - Now parsing step: [16] of [19]
2019-04-30T20:43:54.288+03:00 [Debug] sequence - Now parsing step: [17] of [19]
2019-04-30T20:43:54.333+03:00 [Debug] sequence - Now parsing step: [18] of [19]
2019-04-30T20:43:54.451+03:00 [Debug] sequence - Now parsing step: [19] of [19]

For testing the model without sequence, I've tested it and it's faster than the one with sequences. However, the sequence now became much better (it loads with maximum 10 seconds) and I don't know what's the reason is.

Still animation in HoloLens has an issue, many parts don't change their transparency as set on Creo. I don't know if I should post a new issue for this.

Thanks a lot.

[RolandRaytchev]

Hi @nqwifly,

actually the message "no sequence found in pvi" is when we try to call an sequence in a model widget where the assigned pvi file does not have such sequence. In the UI is this not possible but when we set the properties with javaScript we can get such status. For example, we set the 'sequence' property to a sequence which does not exist. Or the 'sequence' property is already set and we change the model source to another pvi which does not contain the sequence set in 'sequence' property 

Another possible reason is that in the project the original file was changed or replaced in the file structure of the project.

What is then the situation when we create new experience project with only one model widget and e.g. one button to call – e.g. playAll  or play (one step) – what is the performance in this case?

I had one situation where the HoloLense was very slow to load the project. The problem was the environment - noice or some electromagnetic radiation which will disturb HoloLens sensors and affected the tracking. When we try  to read the experience in an enviornment without interferences it was working. I do not believe that this should be the issue here, but it is still helpful when we try to test a particular experience on different environments so to  ensure that there are no some unexpected interferences

-to the other point -transparency- Yes I think is some think we need to consider in a new thread, but please check first with the latest date code /8.4.3 - I think there are some fixes in the vuforia  view also for the HoloLens.