Closed brad86m closed 2 years ago
Please make an apitrace. https://github.com/Joshua-Ashton/d9vk/wiki/Making-a-Trace
Cannot create a trace file as the games are unable to start when those files are present with the game exe.
I can't reproduce the problem. Either way, please retest with DXVK master.
Doesn't really look like a rendering issue but rather an input issue? I cannot reproduce this on my end either.
I have tried the latest master, no change. Tried everything on my end, including running on a different PC. The issue persists.
Unless you manage to produce an apitrace that can reproduce the issue, there's nothing we can do.
FWIW, I had no issues at all making one. But both the apitrace and the game itself worked just fine without that problem.
I'm having this issue with every AC game before Black Flag. The wrapper works great with other older DX9 games. Works fine without it, so there must be some issue with the wrapper, since it wouldn't conflict otherwise.
Should be in the log file, but I am on Windows.
The log file is completely useless. I need an apitrace.
Damn. I can't generate one as the games refuse to start with it :/
Make sure you disable the Uplay and Steam overlays.
Managed to get apitrace to run with the game, but how do I use DXVK alongside it, since they both have the same dll name ?
You don't need to use DXVK alongside it. Please upload that apitrace.
Done :) I let it go into the gameplay for a few seconds
Compressed and uploaded to MediaFire. Hope that is fine. I do not have access to more premium cloud storage services.
https://www.mediafire.com/file/6do6yvodfb0mo9c/ACRSP.7z/file
Unfortunately, I can't reproduce the problem with that apitrace either.
Any idea what I should be looking at to try and find the cause of the problem ?
Turn off all overlays and disconnect all controllers and other input devices.
Tried all that, except booting the machine without my mouse, which I will try now.
No good. That's on two different PC's with every single input device and USB device disconnected, other than a keyboard.
Input device can be ruled out.
I don't know what your system config is, but I tested AC Brotherhood on my Ryzen + Vega with latest drivers and default DXVK conf file. The game works fine on both Win10 and Win7, I just noted some odd shadow banding here and there.
My system config is I5 2400 / GTX 960 / Win10. And the other computer is a Ryzen 3700x / RTX 3070 / Win 10.
The issue happens with both computers, and considering they are completely different set-ups, the issue can't be isolated to just myself.
Just noticed something in your video.
If you look closely at your minimap in the lower right, you can clearly see the map spinning back and forth. It's not a video buffer bug, the camera is actually moving. Somehow it looks more like an input issue. Some driver or software could conflict with the games, even if the device is unplugged.
Same bug happening with me, both in Windows 10 (only when using DXVK) as well as Manjaro Linux 21.1.3. I'm using the Ubisoft Connect version of the game (Assassin's Creed 2). @doitsujin can we please reopen this issue, because it seems to be happening with DXVK even on Windows 10? I'm using a Geforce 940MX which does support Vulkan, using DXVK 1.9.2
Doesn't change the fact that we cannot reproduce it though.
Please make an apitrace that shows the issue on Windows. https://github.com/Joshua-Ashton/d9vk/wiki/Making-a-Trace
@K0bin added the dx9 api trace for the windows version. couldn't add the dxvk trace because the trace d3d9.dll replaces the dxvk d3d9.dll, but i've added before and after dxvk traces for a fresh installation of the game. also added a dxdiag for my system if thats also required. link : https://github.com/netizener/ac2_trace/releases/tag/1 please ping me if you need any other requirements for this issue to be fixed.
I specifically need an apitrace that has shows the bug. I don't think a Windows d3d9 will do that.
If this is supposed to be our problem then we really need more info here, there must be something unique about your system or game configuration since literally no one else seems to have ever had this issue and no one here can reproduce it. What input devices do you have connected to the system? Which fullscreen mode are you using? Anything else that's different from your average desktop PC? What are your exact game settings?
I'm not going to rule out some window message or cursor nonsense going on (although according to the trace, the game doesn't use the cursor APIs), but unless we can reproduce this on our end, we will not be able to fix this.
Has there been any progress on this ? - I have put together a whole new PC since I first opened this issue, and I get the same exact issue on my latest build.
I was never able to reproduce this.
EDIT: Just installed the game again, still fine.
This is the original assassins creed right? I tried a while a back to look into this but didn't notice anything right in the beginning.
Can you provide a save game? Or does it happen everywhere.
It was mostly about Revelations. That's what was shown in the video in the original post. I tried that and its fine.
Roger. I will try to give it another shot myself.
Has there been any progress on this ?
No, the issue is still unique to your systems.
Has there been any progress on this ?
No, the issue is still unique to your systems.
Unique to a low number of people and their setups, but still an issue nonetheless. There is a conflict between some hardware/software and dxvk.
Ignoring it just because it doesn't affect everyone isn't good. Just leads to other issues that get ignored down the line before people move on completely.
Does it happen everywhere? Should i be able to reproduce it as soon as i get ingame?
Also note i don't think the devs are intentionally ignoring this issue. It's just hard to hunt down a fix when none of them can reproduce it.
Ignoring it just because it doesn't affect everyone isn't good. Just leads to other issues that get ignored down the line before people move on completely.
There's simply nothing we can do when none of us has the problem. We can't investigate something that doesn't happen on our systems.
fwiw this issue seems to also happen for some windows users without dxvk. Try to see if the workaround the devs have posted helps. https://steamcommunity.com/app/201870/discussions/1/3114770913767276898/
But i'm still gonna try and see if i can reproduce dxvk being a trigger of it on my two setups.
Gonna close this as a game bug. If anyone ever finds out what triggers this, I might look into this again but apparently this also happens without DXVK on some systems.
fwiw this issue seems to also happen for some windows users without dxvk. Try to see if the workaround the devs have posted helps. https://steamcommunity.com/app/201870/discussions/1/3114770913767276898/
But i'm still gonna try and see if i can reproduce dxvk being a trigger of it on my two setups.
No issue on my PC builds without DXVK. Only happens once I start using it, which is essential for me since the early AC games are very CPU intensive. Even a 3700x can't hold 60fps in heavily crowded areas. DXVK takes away that CPU overhead massively, by the looks of things.
There is a compatibility issue somewhere that is triggered by DXVK. Sadly, with the issue getting closed, it doesn't look like we will find out the cause anytime soon.
Did you try the work around anyway to confirm it's the same issue? Not saying dxvk can't trigger it 🙂
I did indeed. Renaming or deleting the system detection dll doesn't help. Also, Revelations is the only one that uses this dll file. AC1,2, BH do not use it.
I have tried again to reproduce in assassins creed 1 again both on linux and windows, but i have been unable to. Setup and repro details: Nvidia 960, 516.59 driver, no GeForce experience installed on windows 10 (so no overlay), dxvk 1.9.1, launched both through steam and direct through exe, both dx10 & dx9, two monitors connected and main one i tried switching between 165hz and 60, tested ingame at various resolutions and with vsync on and off, only a mouse connected.
I see this thread which might be the same issue for assassins creed II where people have posted stuff that worked for them. If it is the same issue then varoius things seems to do it for people. Tho might be something else. https://steamcommunity.com/app/33230/discussions/1/3124911622551657021/
Also try latest master since alot has been changed recently https://github.com/doitsujin/dxvk/actions/runs/2736244759
I have tried all the common solutions that have been posted in steam and Ubi forum threads. Nothing has worked outside removing DXVK itself, which is obviously not what I want to do as I need it to relieve CPU overhead, which is a major issue in these games.
Okay. Another new AMD PC build for home, and my Intel/Nvidia based system at work still have the same issue. All computers I have tested since originally opening this issue have been using different hardware, peripherals, and different versions of Windows, and drivers. Same result every time.
This not an isolated problem, and affects anyone trying to run DXVK with Assassin's Creed II,BH,REV (and maybe later titles. I haven't tried them) on Windows.
Linux works fine.
It's hard to analyze if we're unable to reproduce it.
I have a new setup now so gonna give it a quick shot. But don't have too high expectations of the devs spending too much time looking into what seems like a game bug that only happens on Windows.
Edit: tho i see above 1 user had it on Linux so scratch that part.
Any progress on this ?
@brad86m We cannot reproduce the issue, so we can't fix it.
Haven't checked on new setup yet. Will qrite here when I've tried
3546 I have found out what the bug was.
This is NOT the issue. It is still a relevant bug to many people.
The issue is still there sadly there is a conflict between dxvk and the early AC games for some reason...
When using DXVK with Assassin's Creed 1 to Revelations, the image bounces around. 2D elements are fine, but anything 3D goes nuts. Tried some setting in the config, but couldn't find one that worked.
https://user-images.githubusercontent.com/84683672/130040661-3ce0321e-fa8c-462d-bd55-0046ee92f0a6.mp4
Log file: ACRSP_d3d9.log