doitsujin
Assassin's Creed 1 through Revelations bouncing image issue
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
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.
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.
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 ?
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
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.