Illusion Walk

You dont have to print and put up new markers. use the marker generation tool and put in the marker numbers and data of the markers you have and then just use the new json. i m just getting a new question: we always made a json for mbsa and another json for mbdp/mbrl. should these markers be created in one go so that they are in the same json file?

Hi @VIVE_Sally, sorry for our last weeks post, but it seems your post was still invisible at that moment. We ve been trying to get logs with the Vive Business Console (VBC_1.08.16_PUBLIC) that you linked, but there is a login error occuring wich says we should contact the support. VIVE Business 1.0.0.15 & Vive Business+ console 2.4.0.23 are not able to get log data from the HMD? Can you help with the login error? Can you also specifiy the process wich we should do? creating a new map and then linking mbsa and then copying the logs?

Another week without an answer or solution for the mbsa topic. @VIVE_Sally

so we got the cameras calibrated now. we had to factory reset because otherwise it wouldnt work. we used the command adb logcat | find “LIVEK” thanks for the help

thanks ChrisMa130. do you have any ways to work around mbsa? @VIVE_Sally any updates on the MBSA?

hi sally, thanks for your replay! out goal is to get a specific point of the playarea with a specific point of our unity scene and the orientation aligned perfectly. doing this manually is not perfect enough. and as i said, the mbsa feature seems to do nothing. we did multiple runs of trying mbsa with different setups and a lot of different scanned maps. we also tried 1 marker or 2 marker setup. the 2 red lines are 2 marker setup. the 1 orange line is 1 marker setup. the versions of everything: pc_sdk: 0.12.1 focus 3 rom: 6.0.999.972 unity: 2021.3.31f1 vive business streaming pc: 1.15.11c vive business streaming hmd: 1.0.21.14 vive mobile app: 2.0.45 steamvr: 2.7.4

Alright, so after even more tests we could not get mbsa to work in any way. with the pc_vr_sdk we re able to get the headset into passthrough so the unity -> sdk -> vive business streaming -> hmd connection seems to work. we re using the example code from XXX and we tried a setup with two and with one ArUco for the mbsa: { Debug.Log("[Start]"); VS_Init(); string key = "PLAYER00InitMA"; //string setting = "{\"marker1\":{\"id\":88,\"behavior\":0,\"size\":0.28,\"pose\":[0.7071,0,-0.7071,0,2.181,1.6,18.162]},\"marker2\":{\"id\":89,\"behavior\":0,\"size\":0.28,\"pose\":[0,0,1,0,-2.566,1.6,2.817]}}"; string setting = "{\"marker1\":{\"id\":66,\"behavior\":0,\"size\":0.28,\"pose\":[-0.7071,0,0.7071,0,-2.34,1.6,2.628]}}"; key += setting; bool result = VS_WVRGetParameters(0, key); Debug.Log("key = " + key); Debug.Log("VS_WVRGetParameters result " + result); /* VS_WVRSetParameters(0, key); */ } it seems that our unity scene is always aligned with the steamVR scene, so these two 0/0 points are always exactly in the same position. our expected outcome would be that the mbsa is aligning the unity or the steamVR 0/0 (or both) with our room, but that does not happen. or expected outcome could also be that the mbsa is setting the 0/0 of the map to the mathematicaly corred position by the data of the aruco json, but this is also not happening. we ve been following these tutorials: https://business.vive.com/us/support/vive-lbss/category_howto/setting-up-marker-based-scene-alignment.html https://business.vive.com/us/support/vive-lbss/category_howto/marker-based-scene-alignment-apis-(pc-vr).html https://forum.htc.com/topic/14254-lbe-feature-marker-based-scene-alignment-update-on-2024522/

can you set it to an own group on the business+ website?

we re also having crashes in unity and in builds with the new update. if we deactivate openXR Hand Tracking in the project settings the crashes disappear.

hi Sally, thanks for your response. Even with the adb logcat | find “LIVEK” command no data of the calibration progress will show up. - waiting for device - 08-28 16:52:31.806 2529 2529 D LIVEK : BOOT_COMPLETED listened 08-28 16:52:31.827 2529 2529 D LIVEK : batteryPct 88.0 level 88 scale 100 08-28 16:52:34.949 2529 2529 D LIVEK : batteryPct 87.0 level 87 scale 100 08-28 15:54:34.272 2529 2529 D LIVEK : batteryPct 86.0 level 86 scale 100 here is the output of adb logcat | find "‍_calib_data.json"‍ 08-28 16:56:43.316 1948 2251 D HDtools : read_from_file: file name = /mnt/vendor/mfg/Final_calib_data.json 08-28 16:56:43.318 1948 2251 D HD : HMD calibration file: /mnt/vendor/mfg/Final_calib_data.json, size: 42581 08-28 16:56:43.318 1948 2251 D HDtools : read_from_file: file name = /mnt/vendor/mfg/Final_calib_data.json 08-28 16:56:43.333 1948 2251 D HDplay : [player_init] json: /mnt/vendor/mfg/Final_calib_data.json 08-28 16:56:45.912 3068 3068 I FeedbackConfig: hmd_json = /mnt/vendor/mfg/Final_calib_data.json 08-28 16:56:46.720 3217 3217 D HDtools : read_from_file: file name = /mnt/vendor/mfg/Final_calib_data.json 08-28 16:56:46.721 3217 3217 D EYEjniso: HMD calibration file: /mnt/vendor/mfg/Final_calib_data.json, size: 42581 08-28 16:56:46.738 3231 3297 I LIPD : HMD calibration file: /mnt/vendor/mfg/Final_calib_data.json, size: 42581 not sure if the calibration is really needed, or just a thing nice to have.

yes we are doing pcvr with unity. it seems that mbsa is doing nothing for the map center, as i would have expected. we re working right now with centering the map manually with the mobilephone-app, so that the map 0/0 is the same as our unity 0/0.

So we re testing the vive focus 3 right now and want to also use the ultimate trackers. in the vive business + console you can not get the map onto the trackers, because it says you can n ot enroll them because you dont have seats left. support is not able to tell me how to get seats. is there another way of getting the map onto the trackers right now? thanks!

Hi We re trying to set up a LBE Map in our playspace of about 25 x 20 Meters. There are 8 collums in our playspace and we re using 28 ArUcos for MBDP with laser measured distances. 1 additional Marker is used for MBSA and is placed on one of the collums. After creating the Map you have to set the Map center manually with holding the HMD at the center before you can use the MBSA? Shouldnt that be without any impact, as the MBSA overwrites the map center afterwards? I tried setting the Map Center and direction at another place then our normal 0/0 point before setting the MBSA and it did make a difference though, and everthing was shifted and tilted even after using MBSA. In this case i m wondering how should i be able to get the center point right manually as one degree change will make a big difference in 25 meters of playspace and just holding the headset in the right way wont be a solution. Also we re having huge differences in map quality, sometimes we get a map nearly perfect alligned with the real world, and sometimes more then a meter of difference. Is Marker Based Scene Alignment not supposed to reset the Map 0/0 Position? Why are we giving the Json of the MBSA the exact coordinates of our 0/0 in Unity then? What is the right workflow to center the map correctly and have it align with the collums? One other thing we re having (but where i think this should not be the cause of the problem) is that we have over 1000 ArUco Markers on the ceiling. These Markers are in a 5x5 pattern and not in a 4x4 pattern like the VIVE Markers. Still we re getting like between 10 and 15 warnings while scanning the map that the distances of the json seem to be wrong. But we ve had great Maps even with these warnings, so i dont think this is related to the wrong alignment. Thanks for any help

Hi, we re trying to calibrate the cameras of our focus 3 headsets, as they seem to be not calibrated. we re following this guide. https://business.vive.com/us/support/vive-lbss/category_howto/calibrating-the-cameras-on-the-primary-headset.html we re getting the message: HD : "HMD calibration file: /mnt/vendor/mfg/Final_calib_data.json, size:" so the cameras are not calibrated, but we can not get any further. Sometimes we get an unsuspected EOF end of file, sometimes not. however no calibration process will start. Any help would be appreciated thanks!

Hello, how did you solve the "software conflict" with OpenXR? We also don't have any visible hands in the example project above.