STILL NOT WORKING IN OCULUS QUEST 2!!

[byHMF]

After the Ubisoft logo appears on the splash screen, the game closes by itself, we have mentioned this here before, but there is no improvement, I am trying it today, the game still closes after the ubisoft logo, an update is required for oculus quest 2, the authorities are very irresponsible.
VR game does not work in vr glasses, is it such nonsense?
If you're not going to update or do anything else, give me my money back,
It makes me sad to pay for a game I haven't played, please find a solution now, Please.

[byHMF]

I'll answer before you ask, I start it on Steam VR, it shuts down, I start it on Ubisoft Connect and it shuts down again,
When I see the logo, it closes without any errors.

https://www.linkpicture.com/q/screen_4.png

[byHMF]

Our Oculus program and our headset work together,
https://www.linkpicture.com/q/quest.png

and there is enough power for the graphics
İntel Core i5
GeForce RTX 3060

[Steve64b]

The game works fine for me on Quest 2 (AMD CPU, Windows 10, dual monitors set to ~1080p resolution, Airlink). I have Steam linked to my Ubisoft account & I have installed the latest Ubisoft Connect launcher.

Try looking at the Ubisoft Connect logs to see if they mention an issue? Typically, they are in C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\logs . Probably launcher_log.txt is the most interesting.

I know some older Ubisoft games (Far Cry) have a compatibility issue with newer Intel chips that have more than 4 CPU cores. Maybe try something like Process Lasso to limit the number of cores for this game?

When the game exits, is there any hint in the "Application" log in Windows Event viewer? See https://www.howtogeek.com/123646/htg-explains-what-the-windows-event-viewer-is-and-how-you-can-use-it/

Alternatively, try running Process Monitor with a filter set up to see if the game is trying to access some files/folders that it's not allowed to access? https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

[byHMF]

my launcher_log.txt
https://we.tl/t-752kquSiBn

[Steve64b]

Originally posted by byHMF:

my launcher_log.txt

The launcher log doesn't seem to show any abnormality compared to my log.

I think a trace of Process Monitor could help. Start Process Monitor, press CTRL+L to open the Filters menu, and create a filter: "Image Path contains Eagle Include". Click Add, and start the game.

Process Monitor should log the actions performed by the game, and hopefully somewhere at the end of those actions, you'll find some operations that cause the game to exit.

[Ubi-Keo]

Originally posted by byHMF:

After the Ubisoft logo appears on the splash screen, the game closes by itself, we have mentioned this here before, but there is no improvement, I am trying it today, the game still closes after the ubisoft logo, an update is required for oculus quest 2, the authorities are very irresponsible.
VR game does not work in vr glasses, is it such nonsense?
If you're not going to update or do anything else, give me my money back,
It makes me sad to pay for a game I haven't played, please find a solution now, Please.

Hi byHMF,

I'm sorry to hear that you are experiencing issues launching Eagle Flight on your Oculus Quest 2. I can confirm that the Oculus Quest 2 was released several years after Eagle Flight was released. At the time of launch the following peripherals were only supported:

- Oculus CV1
- Xbox One Controller or PC compatible gamepad
- Microsoft Mixed Reality
- HTC Vive

However, it seems that Steve64b is able to play the game using the Oculus Quest 2.

Thanks Steve64b for your input it's appreciated.

Can you please let us know how you get on with what Steve64b has suggested.

- Ubisoft Support

[Steve64b]

This may be a long shot, but I also found a compatibility issue between recent (2019+) Intel processors and OpenSSL libraries that could be used by Eagle Flight.

A workaround fix for this issue involves setting the following environment variable in Windows:

OPENSSL_ia32cap=~0x20000000

See these links for more info:
Intel article[www.intel.com]
Setting value in Windows Environment instructions[support.gog.com]

[Ubi_TheBerry]

Originally posted by Steve64b:

This may be a long shot, but I also found a compatibility issue between recent (2019+) Intel processors and OpenSSL libraries that could be used by Eagle Flight.

A workaround fix for this issue involves setting the following environment variable in Windows:

OPENSSL_ia32cap=~0x20000000

See these links for more info:
Intel article[www.intel.com]
Setting value in Windows Environment instructions[support.gog.com]

Thanks for sharing this here too Steve64b, appreciate it!

- Ubisoft Support

[BrokenTV]

Originally posted by Steve64b:

This may be a long shot, but I also found a compatibility issue between recent (2019+) Intel processors and OpenSSL libraries that could be used by Eagle Flight.

A workaround fix for this issue involves setting the following environment variable in Windows:

OPENSSL_ia32cap=~0x20000000

See these links for more info:
Intel article[www.intel.com]
Setting value in Windows Environment instructions[support.gog.com]

There is another method; adding this to the launch options for the game.

cmd /c "set OPENSSL_ia32cap=:~0x20000000 && %command%"

[The_Decompiler]

Originally posted by Steve64b:

This may be a long shot, but I also found a compatibility issue between recent (2019+) Intel processors and OpenSSL libraries that could be used by Eagle Flight.

A workaround fix for this issue involves setting the following environment variable in Windows:

OPENSSL_ia32cap=~0x20000000

See these links for more info:
Intel article[www.intel.com]
Setting value in Windows Environment instructions[support.gog.com]

Incredibly, this was the only solution for me. Thank you very much

[Steve64b]

Welcome! :)

I wish developers like Ubisoft (or even publishers like Steam) could pay more attention to compatibility issues like this, and roll out actual solutions for them. Instead of having all kinds of generic 'troubleshooting' wizards that don't do much to begin with.

[MATRAUX]

Originally posted by Ubi_TheBerry:

Originally posted by Steve64b:

This may be a long shot, but I also found a compatibility issue between recent (2019+) Intel processors and OpenSSL libraries that could be used by Eagle Flight.

A workaround fix for this issue involves setting the following environment variable in Windows:

OPENSSL_ia32cap=~0x20000000

See these links for more info:
Intel article[www.intel.com]
Setting value in Windows Environment instructions[support.gog.com]

Thanks for sharing this here too Steve64b, appreciate it!

- Ubisoft Support

Hey Ubi_TheBerry, istead of posting workaround, what about to fix the f.cking game? Are you really program developer of Ubisoft?