What's New in Vuforia Studio 8.3.3

[tmccombie]

Vuforia Studio

• Support for Spanish locale
• Model sequences can be applied at design time
• Bug fixes and minor improvements

Vuforia View

• Support for Spanish locale
• HoloLens:
  • Support for model-based tracking
  • Support for sequence animations created with Creo Illustrate 4.1 and later
• Windows:
  • Support for spatial tracking
    • NOTE: Currently only the Microsoft Surface Book and Microsoft Surface Pro 4 are supported.
• Bug fixes and minor improvements

Experience Service (On-Premises)

• Support for Spanish locale for the installer
• Model target generation as a service (Beta)

[ClayHelberg]

Thanks, Tara. Can you give a little more information about this item:

• Model sequences can be applied at design time

It's not clear to me what that means, or when I would want to use it (or not). Thanks.

--Clay

[ClayHelberg]

Also, a big THANK YOU to the dev team for getting Hololens support for newer versions of Creo Illustrate!

[tmccombie]

Hi Clay,

This feature allows you to view your model during design as it will show in the experience based on the sequence selected. It is a check box found under the sequence selector for the model.

 model loaded into Studiosequence applied at design time

Hope this helps! 

[jmikesell]

As best i can tell there is now a checkbox under "Sequence" for Model widget items that says "Apply sequence at design time" If you check this the component visibility defined in the sequence is applied in the design 3D view, but not any animation steps in the sequence.

All my sequences start with the parts in the same position so i'm not sure if you had Step 0 defined with parts in a different position maybe the parts in design would go to that location when you picked that sequence?

[ClayHelberg]

It does, thanks!

[ClayHelberg]

Thanks. I had found the control in the Studio UI, but wasn't sure what the effect was. I think I get it now.

--C

[jmikesell]

This seems like it will be helpful for checking imports from Illustrate and possibly for when trying to pick internal parts to apply ModelItems too. Now if we could just get grouping and hiding of objects in the "Tree" like in Creo...

[ClayHelberg]

Yes, I was actually wondering if this feature might solve the problem I described in https://community.ptc.com/t5/Studio/Position-of-modelItem-is-wonky/m-p/565101

As for modelItem grouping, yes, it would be very helpful to have a BOM-like tree control to choose from. However, I've been able to get pretty far by hacking the "Component Occurrence" property. It's a hierarchical path to the part in the assembly, so to get ancestor sub-assembly for a specific part, just start deleting path components from the end of the path, and it will select higher "groups" or assemblies. For example, if your modelItem selects a part with Component Occurrence "/5/1/2", you can select the direct parent by removing the "/2" from the end, resulting in "/5/1". For a deeply nested, part, you can keep working your way up the tree until you get to the level you want.

You can also take a more direct route: in Creo Illustrate, select the subassembly you want to create a modelItem for, and open its Part Properties and check the Attributes panel. There should be an entry called "sBOM ID Path", which gives the string you need to reference this subassembly in within the assembly. You should be able to paste that into the modelItem Component Occurrence field and have it pick the right subassembly.

[jmikesell]

Yes i too have figured most of that, but finding the path from the sBOM properties is great. I had just been counting places (starting at 0, not 1) in the tree. However i have also found this can get you into problems as it will allow you to assign two ModelItems to the same part which will cause odd/unpredictable behavior. You can also assign one ModelItem to a sub assembly and another to a component in that sub assembly which will also cause buggy behavior. Actually just assigning a ModelItem to an assembly does not seem to be supported well, it works for visibility, color, position; most things except for Click Action. Which is unfortunate if you want to treat a sub assembly as a unit part in your experience.

I'm going to go comment on your other post i have seen similar and might have some insight.