FAR (Fix Automata Resolution)

[Kaldaien]

Special K[wiki.special-k.info] features NieR: Automata specific tweaks and features (collectively known as FAR) created by Kaldaien with contributions from various individuals. For years these tweaks were essential to fix various issues the Steam version of the game suffered from, and many of these features and fixes made their way into the game officially following an update to the game released by Square Enix on July 15, 2021.

With the current state of the game Special K is no longer as essential though it still features improvements to the latest version of the game that some may find beneficial:

• Enables much faster loading times.
  
• Can improve the frame pacing of the game and eliminate micro stuttering.
  
• Decrease the global illumination below that of the lowest setting of the game for a major performance improvement.
  
• As well as various other minor fixes and features that improves the overall rendering pipeline and latency, such as Nvidia Reflex integration.

For updated information please see the Special K wiki:

https://wiki.special-k.info/SpecialK/Custom/FAR

Uninstall outdated versions of FAR

The legacy version of FAR (v 0.7.0.23) is not compatible with the new updated Steam version, and the game will fail to launch if left in the game folder. The files related to FAR needs to be removed manually from the game folder, so please remove them from the game folder. This is most easily done by removing any and all files that is not shown in the below image.

• This is how a fully cleaned out folder looks like after the game has been launched once:

https://steamcommunity.com/sharedfiles/filedetails/?id=2559265741

• If the game has not been launched yet another executable along with some batch files will also exist in the folder.
  
  
• Only GOTY owners have the Wallpaper folder.
  
  
• Validating game files or uninstalling/reinstalling the game through Steam will not remove third-party files, such as FAR, from the game folder.

These are the files and folders related to older versions of FAR:

Name	Type	Comment
dinput8	Files	Remove any file with dinput8 in its name. These are the main components of FAR.
FAR.ini	File	Holds NieR: Automata tweaks config.
d3d11_shaders.ini	File	Holds outdated shader config for the outdated custom ReShade of FAR.
Version	Folder	Holds non-functioning auto-updater version data.
logs	Folder	Holds FAR diagnostics logs.
ReShade	File/Folder	Any file or folder with ReShade in its name is related to FAR's outdated custom version of ReShade.

[Aemony]

โพสต์ดั้งเดิมโดย 25 Baam:

hi Kaldaien, can you help me take a look at my logs? A brief history, I installed the mod a few weeks back, it worked great, but I did not have time to play. So i tried again recently, but I was asked to auto update but I think i clicked cancel or something, and the mod did not work upon the game starting up.

So i tried reinstalling the mod, but with the auto install, each time it would ask me if I would like to install, I click yes, but after a while, it would ask me if i would like to auto install. This repeated in an endless cycle.

Then i tried to install it manually, there doesn't seem to be any problem. But when I start the game, the mod does not seem to work. I have tried the ingame keybindings, but nothing showed up. However, when i used the auto-installer again, it shows that the mod is installed, and gave me an option to uninstall.

The logs are as follows:
https://pastebin.com/f8Zkjza4
https://pastebin.com/RKEVetKW
https://pastebin.com/KXkkVpMD

There is no crash log.

Thank you so much!

See the below:

โพสต์ดั้งเดิมโดย Aemony:

You have both the old version of FAR (dxgi.dll) as well as the new version (dinput8.dll) installed in the folder of the game at the same time. That's why it doesn't start.

Remove dxgi.dll from the game folder.

[Aemony]

Btw Kal, if you remember way back I reported that the game for some reason picks interlaced scan mode on my HTPC. Apparently enabling "Force Override" for fullscreen mode solves *that*
problem as well.

So not only does Force Override solve the issue with sub-native being stretched to the desktop resolution in Windows, but it also solves the issue with interlaced scan being used on certain configurations.

This game is a party of fullscreen mode bugs. >_<

I've been trying to find a common denominator but it's hard. I assume your fullscreen override fixes whatever bug the game have with querying the monitor for modes it supports and should use.

I'll probably have to remake the whole issue on the fullscreen issue(s) on my guide to document all my findings...

[Aemony]

Okay, wow, the fullscreen mode really is broken: http://i.imgur.com/I1hDyjU.jpg

So basically despite the fix in FAR (Unspecified instead of Stretched) the game will always output to the resolution that is configured for the monitor in Windows.

So if you have display scaling disabled in the display drivers, and lower the resolution of Windows to say 1600x900, and set the game to 1920x1080 in fullscreen mode the game will (despite FAR) output that 1080p framebuffer to 1600x900.

In my example I'm using 1920x1200 (a 16:10 format) in Windows and sets the game to 2560x1440 (16:9). The game then very clearly outputs the 2560x1440 framebuffer to the 16:10 1920x1200 format, which gets centered on my monitor (GPU/display scaling disabled).

*sigh*

I am not entirely certain how to document this issue along with the few fixes that exists (1. lower desktop resolution in Windows to match, 2. use Force Override option in FAR). >_<

[Aemony]

Are you fucking kidding me? /

So, Kal... Are you aware that you solved that desktop output resolution issue for NieR:Automata in SpecialK 0.8.33 ? It outputs correctly in that version and later, which it doesn't in the unmodded game nor when using the official FAR 0.7.0.11 version.

And here I've spent the last two hours relearning everything I know of that issue, only for you to have already solved it 3 versions of SpecialK back. And in a much better way than enabling ForceFullscreen...

โพสต์ดั้งเดิมโดย Hued:

-snip-

Download the latest version of Special K and rename its SpecialK64.dll to dinput8.dll and throw that into the game folder and remove your dinput8.ini while you're at it. No need to use ForceFullscreen=true any longer.

[¯\_(ツ)_/¯]

dinput8.log : https://pastebin.com/PsEjFrw2
modules.log : https://pastebin.com/KkC5j8Zk

FAR works (I think) but I can not open the FAR hud (if you see what I mean)
And my pro switch does not work, while at the launch game everything worked

Sorry for my english

[Aemony]

โพสต์ดั้งเดิมโดย Linkdu69003:

dinput8.log : https://pastebin.com/PsEjFrw2
modules.log : https://pastebin.com/KkC5j8Zk

FAR works (I think) but I can not open the FAR hud (if you see what I mean)
And my pro switch does not work, while at the launch game everything worked

Sorry for my english

What the heck?

08/18/2017 22:33:09.594: [ Module ]  ( 0000000180000000h + 07368704 )   -:< _DllMainCRTStartup                                               >:-   D:\SteamLibrary\steamapps\common\NieRAutomata\DINPUT8.dll
 ----------------------  [File Ver]    Special K Modding System  0.8.25

[....]

08/18/2017 22:33:09.598: [ Module ]  ( 0000000002150000h + 02682880 )   -:< D3D11Dev_CreateTexture2D_Override                                >:-   C:\Users\Loic\DOCUME~1\MYMODS~1\SpecialK\SpecialK64.dll
 ----------------------  [File Ver]    Special K Modding System  0.6.34

A) Your version of FAR is outdated.
B) You have a really old version of the global injector of Special K installed as well, that's also injected into the game. I assume this is using the now legacy AppInit_DLLs method of injection to inject itself into the game.

You basically need to do this:

1. Remove the path to the Special K DLL files from these registry keys:
* HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs
* HKLM\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs

2. Remove the global injector of Special K entirely. If you want to use it, reinstall the latest version through the updated automated installer which you can redownload from this thread.

3. Remove FAR entirely by removing all files and folders until only these remain: https://steamuserimages-a.akamaihd.net/ugc/808804068655852551/1CC119D2F8F8A2C2AD9519FA15027333A263C31D/

4. Reinstall FAR by redownloading the automated installer and installing FAR through it.

[¯\_(ツ)_/¯]

A&B >
It's possible, I have not played for a long time
I will try thank you

[Aemony]

โพสต์ดั้งเดิมโดย Linkdu69003:

A&B >
It's possible, I have not played for a long time
I will try thank you

Honestly, it's a surprise your Windows 10 Creators Update haven't blown up in your face. Special K v0.7.x have an issue where its DLLs injected into every application through the AppInit_DLLs method caused all elevated applications to crash.

So you couldn't even sign in to Windows 10, since the sign-in screen itself imploded.

So it's really important you do step 1 !!! Otherwise you will most likely have a broken Windows 10 if you ever install the newer version of the global injector in the future.

[¯\_(ツ)_/¯]

Just ... Where can I find those key in the registry? x)

โพสต์ดั้งเดิมโดย Aemony:

Honestly, it's a surprise your Windows 10 Creators Update haven't blown up in your face. Special K v0.7.x have an issue where its DLLs injected into every application through the AppInit_DLLs method caused all elevated applications to crash.

So you couldn't even sign in to Windows 10, since the sign-in screen itself imploded.

Seriously ? O_o

โพสต์ดั้งเดิมโดย Aemony:

So it's really important you do step 1 !!! Otherwise you will most likely have a broken Windows 10 if you ever install the newer version of the global injector in the future.

Ok, thanks ^^

[Aemony]

Copy/paste the below addresses and throw them into the address bar in regedit (like this: http://i.imgur.com/4ewGl2M.png ). Then hit enter and you'll be at the right place.

* HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows
* HKLM\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows

The registry keys are called "AppInit_DLLs" in both places, and should have SpecialK's DLL files contained within. Please note that other DLLs might also be contained within (separated using a semicolon ; I think), but if so leave them and only remove the SpecialK paths.

The paths in question most likely look like this for you, which needs removal:

* For AppInit_DLLs in HKLM\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows:
C:\Users\Loic\DOCUME~1\MYMODS~1\SpecialK\SpecialK32.dll

* For AppInit_DLLs in HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows:
C:\Users\Loic\DOCUME~1\MYMODS~1\SpecialK\SpecialK64.dll

[¯\_(ツ)_/¯]

Ok thanks ^^


It reminds me something

On each of my games it sometimes happens to me to have the alert sound of MGS then the game that plants

This may be the cause

[¯\_(ツ)_/¯]

Ok, i remove all of this, i reinstall FAR now

[Aemony]

It's very likely. Special K v0.6.34 is a really old version (we're at v0.8.35 now) and through the AppInit_DLLs keys it got injected into all applications that were started on your PC. There's no telling how many issues that caused.

Luckily you didn't experience the issue where the v0.7.x version completely broke the Creators Update. We've had a couple of people who experienced that issue where you basically need to boot into Safe Mode and either remove the Special K "My Mods" folder in My Documents completely, or remove the entries from the registry.

It's good that you're removing those paths from the registry before updating, as you would otherwise get in a situation where you couldn't even launch RegEdit without it crashing because it tried to inject the newer version of SK into it :)

[¯\_(ツ)_/¯]

Oh thanks a lot, it works now <3
I remove the SK folder and those 2 registry keys

Know i just need to connect my controller but i think i can do alone ^^

Thanks a lot dude, you probably save me and my windows x)

[¯\_(ツ)_/¯]

Soooo... It don't work x) can you help me ?
I use x360ce, I configured it well, I use xinput 1.3 64 bit and I use Rehoock xinput in FAR but it don't work :/

Do you think you can help me ? It worked perfectly in April