The post says " Game is very demanding on the CPU and benefits from additional cores.[1] Use level of detail decreasing settings and limiting frame rate to improve performance."
The source is from 3 years ago, maybe time to remove?
Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.
Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.
Not editable
Content is available under Creative Commons Attribution Non-Commercial Share Alike unless otherwise noted.
The post says " Game is very demanding on the CPU and benefits from additional cores.[1] Use level of detail decreasing settings and limiting frame rate to improve performance."
The source is from 3 years ago, maybe time to remove?
I have removed it, and rephrased the recently introduced DXVK bullet point.
The CPU demanding nature of both Origins and Odyssey seems to in many ways be due to the design of the engine itself which seem to be designed for modern low-level APIs like DirectX 12 and Vulkan. The Direct3D 11 API seems to be what is bottlenecking the engine. Hell, apparently it seems to use a compatibility layer to turn the native D3D12 calls into D3D11 on Windows.
On my Vega 56, I confirm that DXVK is *the* miracle solution to permanently fix the micro-stuttering that plagued Origins. It also massively improves frame rate in cities like Alexandria and Memphis (Odyssey benefits as well in similar places). Note that, in my case, I had to set the in-game FPS limiter to 60 for DXVK to actually work (FPS would remain choppy otherwise).
Kaldaien indeed suggests that Origins and Odyssey on PC were heavily designed for multithreaded APIs, but were downgraded to run on DX11, which completely kills performance in both games. The DXVK (DirectX to Vulkan) translation layer removes that limitation.
After spending hours trying to get DXVK 2.0 to work with Assassin's Creed Origins, which was crashing on startup, all I had to do was install Vulkan runtime from their website. After that, works like a charm. Maybe add this to the wiki. Also I see you mention chopiness. I had that too at first. Reduced a few settings so that the fps stays over my vsynced refresh rate and it was gone. DXVK seems to struggle very much if your fps is under your refresh rate. I think you also need to wait for the cache to build.
I removed that part of the audio section. I'm not sure why it was part of EAX support, EAX isn't a thing anymore. I really wish articles here would mention windows spatial sound api support.
Ao reinstalar o windows, perdi as salvas. Mesmo copiando as mesmas de outra pasta para a pasta "documentos - Assassin's Creed origins", o jogo sempre começa do início. Como resolver?
The documented location is: <Uplay-folder>\savegames\<user-id>\3539\
Today I want to make a simple bat script to backup this savegame folder, and I observed that in my system the folder "3539" does not exist. My savegame files are in the folder "4923". I use Windows 10 Home, and my game is from Steam version.
Thanks, I've added a Steam row with that ID as well.
It's confusing, sometimes Uplay uses separate IDs between Uplay and Steam, and sometimes they do not. Sometimes I believe they also uses separate IDs on Uplay between different regional version as well.
It makes us less accurate in regards to covering Uplay titles for sure.