Increase the precison of Angular Velocity
to make more comfortable the Issue #798 Angular Velocity can't go below 0.4 something (round to 0.5)
But this won't solve the trouble.
For this it would require a fixed for issue #76 Rotations that are transmitted over server lose precision
Fix for Issue:
#711 Add error dialogue if an unsupported filetype is added as a model URL in the create app.
As agreed, the label "Model URL" will indicate now: "Model URL (.fbx, .fst, .glb, .gltf, .obj, .gz)"
The list of file type has been set in Italic.
And the label for Material dialog has been adjust to have the same standard "(Optional)" is also in italic.
Add an audio feedback mechanism
to play confirmation or rejection sound on specific actions that are not visually detectable.
Here for Parent and Unparent (because it not visually detectable in HMD if the action was successful or not)
Fix also a bug where the HMD multiselection could stay active after we return in Desktop mode
Now it is deactivated when the create window are closed.
Add an audio feedback mechanism
to play confirmation or rejection sound on specific actions that are not visually detectable.
here for "Duplicate" (mainly for the HMD use case where the new entity is generated at the exact same position)
Add an audio feedback mechanism
to play confirmation or rejection sound on specific actions that are not visually detectable.
- Duplicate (mainly for the HMD use case where the new entity is generated at the exact same position)
- Parent and Unparent (because it not visually detectable in HMD if the action was successful or not)
Add a HMD MultiSelect button
Since it's impossible in HDM to do a multiple selection
This adds a MultiSelect button (available in HMD only)
When active, the selection in the list behaves like having CTRL pressed
When inactive (default value) the selection in the list behaves as before (on item only)
HMD: Make the 2 buttons visible without scrolling
In HMD, the 2 buttons:
- Open This Domain's Asset Server
- Import Entities (.json)
were not visible without scrolling. people would not even notice their presence
This fix adjust the spacing and the margin to have the entities button on 2 rows when the UI is in landscape mode
this way the button are visible.
Fix a bug about tablet stuck in Landscape
when the create app was open in desktop and you put your VR Headset on,
then next time you open the tablet it was in landscape mode. (because a refresh was happening after the landscape set to false at the closure)
Now the condition is geared to deal with the situation.
Fix: Reset Landscape mode in HMD
In HMD, clicking on the button "Open this Domain's Asset server" is reverting the tablet to "portrait" mode
This fix forces the mode to return to Landscape if from the Asset server we click on the "List" tab.
Fix: Reset Landscape mode in HMD
In HMD, clicking on the button "Open this Domain's Asset server" is reverting the tablet to "portrait" mode
This fix forces the mode to return to Landscape if from the Asset server we click on the "Properties" tab.
This adds the support for 6 new buttons:
Copy-Cut-Paste-Duplicate-Undo-Redo
It adds the automatic toggling of the HMD only buttons:
Copy-Cut-Paste-Duplicate
Remove an unused commented const.
Generate all the material using a centralized function, using an array to store the keys.
Make them deleted by iteration on this array.
Using now defaultFallthrough = true instead of setting albedo to fallthrough.
Replace "materialMappingMode" "projected" for "uv"
Added "ignorePickIntersection": true on the Material entities
This commit includes 2 parts:
1- Re-adjustment in the code to stay aligned with axis/colors/Pitch-Yaw-Roll
It seems that the Overlay 3dCircle was in fast patch to work while the Gizmo Ring is aligned for Axix versus Pitch-Yaw-Roll.
The modification has been done differently and is in fact a simpler solution.
2- Add a Material local entities parented to each tool entity to make the Selection tool "unlit"
This addresses Issue #709 Enhancement: Make create translate "widget" unlit
BUT there is a known issue: The Gizmo Ring are not supporting the Material currently. (an issue has been open for that see #744)
The Rotation rings are then not "unlit", but everything in the code is ready to support it when it will be done.
Gizmo Ring having practically designed for that specific usage, I think we should keep using them.
Other alternatives like using an image or a model would imply to considerable modifications.
We would lose the angular representation (that can't be done with image or model).
The remaining "unlit" issue is very low severity, the widget is still fully functional. So I think it can wait for the support of Material.
