Have you also disabled Steam Overlay?
Overlays use injection to show additional information on game interface and usually they choose to inject graphics related API so they can directly draw content above game.
RTSS and other tools that can show content above game also use this type of injection, except NVIDIA Share (it is powered by GPU driver functions). There is no way to control these tools' injecting orders since all tools detect and inject by themselves.

U can use ProcessExplorer to see all DLL files loaded by the game, and maybe u will find something weird.

For example, the image below shows DLL loaded by a game. Except all system files and files in game folder, other files are loaded by 3rd softwares. In my image, RTSS and Nahimic are loaded. To see whether these 3rd softwares lead to problems, u can use Windows Sandbox (can be enabled in control panel, will create a temporary stock Windows with no 3rd software) to test.

Yes, I did try with steam overlay disabled too - did not help. Weirdly enough, AC Odyssey (I guess pretty similar to Origins) works very good with both Steam and Uplay overlays on the same exact system and its variables. Will try ProcessExplorer shortly - thanks! :)

Update:
ProcessExplorer did not show anything different vs launching AC Odyssey. Same dlls, not really anything third-party.

Update:
ProcessExplorer did not show anything different vs launching AC Odyssey. Same dlls, not really anything third-party.

Have you installed today's 1.60 patch of AC Origins released a few hours ago? Install and try again.
Today's patch seems to use a newer version of VMProtect and Denuvo that the executable file size changes a lot.
After update i tested both overlay and non-overlay with DXVK, everything works well on my Windows PC.
Maybe it's ubi's bug instead of DXVK's.

Can't update yet - they cancelled the update until something will be fixed. Can't test anything because of this.

Can't update yet - they cancelled the update until something will be fixed. Can't test anything because of this.

Seems that the newer Denuvo has some compability issues. Console's update isn't cancelled. Wait a few days and see whether ubi will fix it and release again.

Still waiting for Ubisoft to push the Steam ver. update.
Meanwhile I did manage to test the same scenario on pretty similar specs machine with different environment - 3900X, 3080Ti, Windows 11, older GPU driver version. Motherboard manufacturer is ASUS vs my MSI. The results are exactly the same - game fails to start.

Strange that Ubiconnect overlay would force vsync. I don't have any issue with Freesync unlocked.

Have you tried editing your dxvk.conf file?

dxgi.syncInterval = 0
d3d9.presentInterval = 0

I did try to play with dxvk.conf settings and just tried the lines above - did not help. Monitor still stuck at 144hz.
One interesting thing though, is that both fullscreen and borderless-window modes don't work with freesync - 144hz. Completely windowed mode though, the one with borders etc. works with freesync. As soon as I press ALT+ENTER to force fullscreen -monitor returns to 144hz. Also, as mentioned before, all this works only if Uplay overlay is active. Otherwise game does not start in any mode.

Update:
ProcessExplorer did not show anything different vs launching AC Odyssey. Same dlls, not really anything third-party.

Have you installed today's 1.60 patch of AC Origins released a few hours ago? Install and try again. Today's patch seems to use a newer version of VMProtect and Denuvo that the executable file size changes a lot. After update i tested both overlay and non-overlay with DXVK, everything works well on my Windows PC. Maybe it's ubi's bug instead of DXVK's.

I'm using 1.6 on my steamdeck and this version has broken AC: Origins it seems to have issues with Win 7 machines, so not sure if issues with dxvk or bad release?

If you play the game now, it will hang at random places and you have to force quit the game.

Posted bug here with log https://github.com/ValveSoftware/Proton/issues/928

Probably not related to DXVK. On Ubi forum, several people complain that the last patch (with the super useful "Assassin's Creed Franchise" store shortcut) has broken Win7 support.

Probably not related to DXVK. On Ubi forum, several people complain that the last patch (with the super useful "Assassin's Creed Franchise" store shortcut) has broken Win7 support.

Think you right, but is there any config in dxvk that can make the game run more like its not on windows 7? I think the default pfx in proton are windows 10 based, but maybe there is something the real windows 10 does that we can configure dxvk to do? if anyone know?

Updated the game - still the same behavior. Does not work without overlay. Works with overlay, but monitor does not catch the Freesync state or something - stays at 144hz and because of this the game is not really smooth. Eh, had such high hopes for the patch.

Can any of you check if anything has changed with dxvk master in relation to this issue? Alot of changes have been made since.
You can grab a build here https://github.com/doitsujin/dxvk/actions/runs/2940494057

Note you need relatively up to date drivers to use it

Still does not work for me. The same behavior as before - stuck on splash. When using with UbiConnect overlay ON - the game still does not work with freesync either. I can set it to 90fps lock and my monitor would still report 144hz refresh rate.

There is definitely something happening with the overlay. I got these observations:

1. When I try to use the attached build in other AC game, Odyssey, the overlay is really buggy. Basically if I open overlay within a game and close it - it technically gets closed (not clickable etc.), but it is still being shown within the game. Also the game shows a notification about controller being connected as an overlay message - after timeout it disappears, but with the dxvk build it technically disappears, but practically "last frame" of it continues to be drawn on screen even if it is no longer interactable. Never had any AC Odyssey issues with DXVK before.
2. I did try to delete the GL dlls of the Ubisoft Connect and run AC Origins. With overlay off, as expected, same behavior of being stuck on splash screen. With overlay on - the game loads, still stuck at 144hz freesync, but the overlay has exactly the same behavior as in AC Odyssey - after any interaction, last state of overlay keeps being shown after technically being closed. Not sure if it makes sense and if it can lead anywhere.
   Thank You to anyone, who dedicated time to this. :)

There is definitely something happening with the overlay. I got these observations:

1. When I try to use the attached build in other AC game, Odyssey, the overlay is really buggy. Basically if I open overlay within a game and close it - it technically gets closed (not clickable etc.), but it is still being shown within the game. Also the game shows a notification about controller being connected as an overlay message - after timeout it disappears, but with the dxvk build it technically disappears, but practically "last frame" of it continues to be drawn on screen even if it is no longer interactable. Never had any AC Odyssey issues with DXVK before.
2. I did try to delete the GL dlls of the Ubisoft Connect and run AC Origins. With overlay off, as expected, same behavior of being stuck on splash screen. With overlay on - the game loads, still stuck at 144hz freesync, but the overlay has exactly the same behavior as in AC Odyssey - after any interaction, last state of overlay keeps being shown after technically being closed. Not sure if it makes sense and if it can lead anywhere.
   Thank You to anyone, who dedicated time to this. :)

seems that the overlay keeps rendering at a high framerate, cause the freesync failure and continuous drawing.
this may also explain why fps is lower when overlay turn on in R6S on my laptop, even in native vulkan. (at least the performance downgrade has existed since the new version of overlay)