Skip to content

Events

Jump to bottom
fwei-io edited this page Oct 22, 2021 · 1 revision

Here are Futurewei OpenXR-ADK events

OpenXR-SDK Meeting

Date: TBD
Time: TBD
Venue:
Minutes:

Date: CET 2022-03-11 / CST 2022-03-11
Time: CET 9:00AM / CST 4:00PM
Venue: https://welink.zhumu.com/j/180357491
Minutes:

Date: CET 2021-11-25 / CST 2021-11-25
Time: CET 9:00AM / CST 4:00PM
Venue: https://welink.zhumu.com/j/180549643
Minutes:

CANCELED

Date: CET 2021-11-24 / CST 2021-11-24
Time: CET 9:00AM / CST 4:00PM
Venue: https://welink.zhumu.com/j/151894041 \

CANCELED

Date: CET 2021-11-23 / CST 2021-11-23
Time: CET 9:00AM / CST 4:00PM
Venue: https://welink.zhumu.com/j/152628116

CANCELED

Date: CET 2021-11-19 / CST 2021-11-19
Time: CET 9:00AM / CST 4:00PM
Venue: https://welink.zhumu.com/j/172684723

Date: CET 2021-11-05 / CST 2021-11-05
Time: CET 9:00AM / CST 4:00PM
Venue: https://futurewei.zoom.us/j/93902131841?pwd=OVJiTjlDU3R1THJiYVZsVGROQmZMUT09
Agendas:

  • https://github.com/hms-ecosystem/OpenXR-SDK/issues/1
  • https://github.com/hms-ecosystem/OpenXR-SDK/issues/2
    • SDK team replies they are still looking into it.
  • https://github.com/hms-ecosystem/OpenXR-SDK/issues/3
    • Develoepr confirms that the buttons are working now using the new OpenXR mapping paths. The only issue is that left/right controllers are still reverted and FxR is still using a workaround for that. SDK team mentioned it's working in the demo. Develoepr: it could be related to the subaction path issue too.
  • https://github.com/hms-ecosystem/OpenXR-SDK/issues/5
  • https://github.com/hms-ecosystem/OpenXR-SDK/issues/17
    • SDK team explains that is going to be fixed with "Fix the bug of 6dof helmet posture transmission", which was later than other tasks in the plan. Conversation about the priority of the task, and decision to make that task the highest priority, SDK team will update the issue and the estimated times of the plan. Developer explains the progress of the trackpad implementation and mentions some of the issues found:
      • XR_TYPE_ACTION_STATE_VECTOR2F was not working and had to make extra code. SDK team mentioned to try a different path " /user/hand/left/input/trackpad/value" to use the Vector2F.
      • Developer mentioned the values should be between -1.0 and 1.0 instead of 0.0 to 1.0 based on the OpenXR standard. Not urgent since using a workaround is easy to make the conversion.
      • SDK team confirmed the trackpad error range is 0.05, and we need to ignore scrolling values less than that
      • Developer mentioned an issue about only the first controller queries getting correct values for the trackpad. SDK team replied that it's working in the 6DOF demo for both controllers. Developer mentioned that a difference could be that FxR is using different actions with a single subactionpath and the demo is using single actions with multiple subactionpaths. Agreed on testing the demo and confirming if using subactionpaths works
  • https://github.com/hms-ecosystem/OpenXR-SDK/issues/19
    • Developer looked into the low microphone issue, found the source of the problem but the fixes didn't work, added more details on the issue.
  • https://github.com/hms-ecosystem/OpenXR-SDK/issues/20
  • https://github.com/hms-ecosystem/OpenXR-SDK/issues/21
    • SDK team confirmed that it's a bug in the SDK and is already in the plan

Date: CEST 2021-10-28 / CST 2021-10-28
Time: CEST 8:00AM / CST 2:00PM
Venue: https://futurewei.zoom.us/j/91398059719?pwd=cW9Td09pakJ3YkFBOUE2aTl2cGJGUT09
Agendas:

Clone this wiki locally