Quest 3 no longer works with Condor 2

[johnr777]

When I purchased my Quest 3 about 5 months ago I was able to access Condor 2 and the software I purchased while using my Rift S.

Today I attempted to access Condor 2 with my Quest 3 but I get the error message ERROR INITIALISING DIRECT 3D.

When using the Rift S I was able to include Condor 2 in my list of libraries which made it easy to start Condor 2. Now when using the Quest 3 I am not able to include Condor 2 in my Meta list of libraries but only software I purchase in the future.

Apparently Meta deleted my Rift S account and all the products I had purchased while using the Rift S. It also appears Meta deleted many other user accounts since early this year.

Have other VR users experienced the same problems as myself?

[Sailabout]

Have a look here: https://www.condorsoaring.com/forums/vi ... hp?t=21191

To fix the "Error initializing Direct3D" issue when trying to use your Oculus Quest 2 with Condor 2, try the following steps:

Disable Oculus Software Before Starting Condor 22

The culprit seems to be the Oculus software running in the background. To resolve this:

Allow the link to the PC when starting your Quest 2, which will start the Oculus software
.
Then start Condor 2. If you start Condor 2 before linking the Quest 2, you will get the Direct3D error
.

[Crakob]

Hi, for me that error occurs, when starting condor without the headset being connected.

I would install the latest oculus software. When the headset is connected (Link or airlink) The oculus software will prompt the succsesfull connnection with "green dots" and your are good to go.

[johnr777]

I have managed to include Condor 2 into my Oculus library by doing the following:

Make sure the short cut for CONDOR 2 is included on your Windows desktop.

Access the Oculus Home Page and select LIBRARY.

Locate FILTERS and click on it.

Locate the OPTION UNKNOWN SOURCES and click on it which now allows CONDOR 2 to be included in the OCULUS APPS.

I also clicked on the options for UNINSTALLED APPS and HIDDEN APPS but I have no idea what they do.

I have been successful in using CONDOR 2 in VR but not always. More experimentation is required to find the correct steps needed to ensure I can activate CONDOR 2 in VR every time.

Hopefully this information may be of help.

Cheers

[FerociousCondor]

Q:
I'm having a hard time with C2 and Q3. For some reason I assuming the latest Q3 update I do have the UNKNOWN SOURCES listed. I installed threethan/LightningLauncher and not able to see UNKNOWN SOURCES but C2 is not listed. What am I missing?

Thx

EDIT:
Got it working. what a PITA! Seems like Meta has moved around setting options in firmware updates. Had to make some adjustment on the Horizon mobile app, Oculus Link desktop app and on the Quest 3. Finally got past the Direct X error.

Do get a message from the Oculus Link that the GFX card is not compatible.

Dell Precision 5540 i7-9850H @ 2.60 GHz (6 core CPU)
Intel UHD Graphic 630
Nvidia T2000 4GB
32GB RAM

[MagicValy51]

Hello everyone,

META QUEST3 works well with Condor2 and Condor3... In fact
When you are experiencing issues - the message that you are getting from Condor2 or Condor3 is "faked" and mean nothing.
To understand what is really going wrong, have a look to Condor's log file located at:

C:\Condor2\Logs\ErrorLog.txt

Here is a example content for illustrating purpose :

"Created Render Target Views.
Oculus Rift swapchains successfully initialized.
Finished initializing DirectX 11.
Creating game objects.
Initializing controlers.
Force feedback initialized.
Initializing TrackIR.
NPClient location: C:\Program Files (x86)\NaturalPoint\TrackIR5\NPClient.dll.
Init_TrackIR_Dll OK.
NP_RegisterWindowHandle failed with error code: 1.
TrackIR initialization failed."

Try to find any error code registered when starting to fly. Note your launch time and check the timestamp within the log file.

You wil discover the real issue with your META QUEST2 or META QUEST3 or PIMAX VR headset :

Almost the time, it's because the META LINK interface is dead.
You need to install or reinstall META LINK framework from META setup (also known as Oculus)
The META LINK is responsible to link your META headset to your PC through USB 3.2 gen2 or WIFI 6/6E or 7 if no USB câble.
When the driver META LINK is corrupted or after an updated that failed, in the Condor2/3's error log file, you are getting the real issue like "MHD is not properly initialized or MHD link failed or MHD is not responding" while getting an error message from Condor3: DirectX failed or error - which is not the real explanation of your issue.

Sometimes, you need to get your META LINK framework to be updated after updating your NVIDIA vidéo driver... If automatic update is not well managed from META QUEST LINK application, you have to update the component manually.

After updating, if you are getting the META Application "Virtual Desktop Streamer" works fine (I mean, your PC is well monitored on Graphics Card,
Codec, Memory, Router Settings, etc...) It means that your PC is well connected to your META QUEST headset and you can use Condor2 or Condor3 has expected.

Good luck