Fil

Hi, are you using the XR interaction toolkit?

Some news about this topic? If the disabling of the logs is not possible today, could you inform us, if this option is planned in the next wave SDK release?

I'm also interested in a solution to disable these logs. And please no, filtering the logs is not a solution 🙂 FYI: In my case, the logs are only shown in the editor. I built an "in scene" log console in my app and the wave related logs are not showing up, when running on the Focus 3.

If the step above helps regarding the quality then you should simplify the geometry in your scene (mostly reduce the polygons) or deactivate some post processing features. I would suggest not to unselect "dynamic resolution" for your productive app because framerate drops could induce VR sickness.

Hi, Under "Project Settings / XR Plugin Management / WaveXRSettings" you can find the setting "adaptive Quality Mode". If the dynamic resolution is on and your scene is too complex to render so the framerate would go down too much, the resolution will be reduced then. Choose Customization mode and unselect the dynamic resolution:

I got a feedback from the vive support team. It was due to a bug in the DMS server backend. Apps with APK levels higher than 27 were succesfully checked by the manifest checker but were rejected afterwards during the submitting process. It is now fixed and apps with apk level higher than 27 can be uploaded and pusblished.

I am not part of the OpenXR Beta program, so I cannot really help you. But the most probable problem in my opinion is that some packages or examples have unregistered cross dependencies. You should try downloading all OpenXR related packages (also for Android although you are developing for Windows). You should also try importing the other examples (Facial Tracking and HandTracking examples). Perhaps the missing scripts are located there.

Ok I got a feedback from the support team and they solved my problem. If you have also the problem that your WIFI MAC Address has changed: forget your current WIFI, in which you have the problem Reconnect to the WIFI and set "use Device MAC" instead of "use randomized MAC" before you confirm the connection Now the used Wifi MAC Address is the "native" device Mac address Unfortunately, setting "use device MAC" on a wifi you are already connected with doesn't set the MAC Address to the "native" one. Sounds like a bug for me.

I reported the issue the way you said @C.T.. But I don't get any infos, not even an email to inform me, that a ticket has been created. Is this normal?

It seems I don't get a copy per email of my report. Unfortunately, I have to wait until it has been processed by HTC.

Thanks, I reported the issue. As soon as I get a copy per mail (I assume I will get it), I can transfer the logs to you. For Info: This is not important to have this setting valid for all networks or not. The important aspect is to have the "static" headset MAC address remaining the same over time/over update.

For info: The setting "privacy" where I can change from randomized MAC to Device MAC is specific for each Wifi network, it is not a general setting of the headset. How can I get the logs from the headset?

I'm 100% sure that the MAC Address is changing. We need to whitelist it in the Wifi MAC Filter in our Corporate Guest WIFI in order to access the Internet. I already needed to rewhitelist the device twice with a new MAC Address because the address had changed. I supposed then that it was after each update (but it could possibly happen after a certain amount of time, I'm not completly sure about this point). A MAC Address change is a big issue for a business device.

Hi, By uploading corporate content using the device management system, I get an undefined error (see attached picture). The apk manifest check runs successfuly and I am able to "submit" my app. But then I'm getting the error, unfortunately there is no error code or error description. Does someone has some tips?

Thanks for your reply. I know, that we need to set to "Use device MAC Address" in the connection settings. The problem is that the device wifi MAC address is changing after each update. So the fixed IP is not the same anymore and it gets rejected by the MAC address filter.