Quest2: unable to launch FlexSim

[chanykE2WUT]

[ FlexSim 22.2.2 ]

Hi I just gotten my Quest2 lately it was running fine in Win11 till 16th Sep where an update was launched (Meta Quest Build 44.0). Since then I am unable to launch FlexSim within the Quest2. Those that has Quest2, have you encountered any issue?

Regards

David

[philboboADSK · Accepted solution]

I have a Quest 2 and I just updated it to test whether everything's still working correctly.

When I upgraded, it changed to using a Meta account instead of a Facebook account or an old Oculus account.

After getting everything updated with regards to the account, I found that Oculus Link (now called Quest Link) was not appearing in the Quick Settings in the headset anymore.

To enable Quest Link (via cable or Wi-Fi "air" link):

From within the headset, go to Quick Settings, then push the Settings button in the upper-right corner, then push the System button in the upper-left corner, and then press Quest Link in the list just below Keyboard. Enable the Quest Link toggle, and then either press the Launch Quest Link button there, or press the Quest Link button that now appears on Quick Settings after it is enabled. (See Use Quest Link with Meta Quest 2 or Meta Quest | Meta Store)

Once Quest Link was enabled and I was able to access the Oculus Rift content on my PC, then FlexSim's VR Mode worked as normal.

Does this help solve your problem or are you having some other issue connecting?

[chanykE2WUT]

@Phil BoBo I am able to do it on Win10 but not on Win11. Any input?

When I press the Launch in the headset environment, I see the three white dots. The three dots kept animating the loading process.

David

[philboboADSK]

Are you using a USB3 cable? Are you using Quest Air Link? What does it say in the Devices section on the Oculus app in Windows? What does it say in the Notifications? Usually errors appear there.

Have you tried restarting your computer or updating your drivers? This sounds like a configuration issue, not a FlexSim issue.

Try searching the internet for solutions to try, such as: How to Fix Quest Link Not Working Shows 3 Dots when VR Cable is Connected to PC - YouTube or PSA for those facing the 3 dots issue with oculus link : OculusQuest (reddit.com)

[chanykE2WUT]

@Phil BoBo I have done that are needed, but it is still not launching. There are a few comments in the video that you shared, they are seemingly having issue with Win11 in launching application within the Quest2 too. They were commenting it could be the Win11 driver issue.

For your info, my system is

Acer Nitro 5 ANS17-41-R241 R7-5800H

graphic card is nVidia GTX3600

Regards

David

[philboboADSK]

I don't think the issue is with Windows 11 specifically or with the Quest 2. I tested it on a Windows 11 machine without any trouble:

Again, this isn't a FlexSim problem, and it doesn't seem like an OS problem to me. Figure out what you need to adjust about your computer's configuration in order to get Quest Link to work. Once that's working, I'm sure FlexSim will also work just fine.

My guess is that it is an issue with the integrated graphics on the CPU conflicting with the Nvidia graphics card. I'd try installing whatever the latest graphics drivers are available for the laptop from Acer's website. Don't rely on Windows Update or Geforce Experience software for your drivers; try getting the drivers directly from the laptop manufacturer for both the integrated CPU and the dedicated GPU.

[Jacob_White]

Hi @David Chan, was Phil BoBo's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

[chanykE2WUT]

@Jacob W2 the answer provided did not help to solve my problem, so I am not sure if the case should be closed. If there is nothing that can be done with the problem outstanding, then I will close it.

David

[chanykE2WUT]

I managed to solve the issue by updating the AMD driver. So the case is finally close

David