#THE ASCENT DIRECTX 11 OR 12 HOW TO#
#THE ASCENT DIRECTX 11 OR 12 PC#

#THE ASCENT DIRECTX 11 OR 12 PC#

Memory, and specifically VRAM, as well as data movement (due to the non unified nature) on the PC side can be quite lacking versus the PS5 (or XSX) at this point still even if the other performance metrics are higher. The PS5 version supposedly was updated with specifics to take advantage of the higher memory of the PS5 and the SSD/storage framework. My understanding is the PC version is based on the PS5 version. They'd already shifted to UE4 for other projects, such as Kingdom Hearts 3. I think Square's own Luminous engine was considered hard to work with (and therefore more labor intensive) especially for the design side. Some other random thoughts on some of the comments regarding this.

#THE ASCENT DIRECTX 11 OR 12 HOW TO#

How to add DXVK async to your game ( DXVK is a DX11->Vulkan wrapper that bypasses the shader compilation of the game and allows asynchronous, stutter-free shaders to work)Ģ) Download the dxvk-async-1.9.2.tar.gz fileģ) You need to copy the files d3d11.dll and dxgi.dll from 圆4 folder into Final Fantasy VII Remake -> End -> Binaries -> Win64ĭon't have FF7 Remake yet but something to look into regarding the stutters. There are two options to do this:Ī) add '-dx11' in your epic store launch options for the gameī) open epic_emu.ini from Final Fantasy VII Remake -> Engines -> Binaries -> ThirdParty -> EOS and add ' -dx11' after AppName=FFVIIRemakeIntergrade -> so it looks like AppName=FFVIIRemakeIntergrade -dx11, save the. It is now possible to fix the stuttering issues in FF by making the game run in DX 11 mode and adding DXVK async to the game, a Vulkan wrapper that bypasses the shader compilation of the game, allowing for asynchronous shaders to work.ġ) Make your game run in DX11 mode, otherwise this won't work. if Epic can't figure it out, and developers using their engine knowingly release products which have these issues. Other developer and other engines are largely solving this.

This is NOT expected behavior from games and is NOT something PC gamers should EVER accept. I've already stated I'm willing to wait for a process to 'warm up' the game and create a cache. then these guys can figure out a way to make that happen the first time I play something. If I can make a shader cache and the 2nd time through it's perfectly smooth. I don't care who has to do the work to solve this issue. Imagine where this industry would be if developers just simply accepted things as they were? Man, what a depressing world that would be. Developers LITERALLY solve issues every single day and work around things that documentation says 'isn't possible'. then they are knowingly screwing over their customers, and absolutely need to be called out on this. and if Epic and Developers KNOW that they aren't going to fix it. People are going out and spending REAL money on new hardware in an attempt to fix these issues. something being stated in their documentation is not the same as an announcement to the public about the current state of their engine on PC. you know that 99% isn't 100% right? Nobody is asking for a perfect game which doesn't ever dip a single frame ever.Īnd no.

so I don't want to hear Epic's excuses.īesides.

The ascent directx 11 or 12