TextBoxInputFile.Text = RegistrySettings.Read("InputFileName") I then remade the hotbars and ui just to see if what would happen, logged out, exited the game completely and logged in again just now., and it had turned to default yet. RegistrySettings.SubRoot = "Software\\Company\\App" Game is not saving settings Earlier today everything was working fine, but when i logged in an hour or so ago, my char(s) hotbars, settings and ui had reverted back to default. Re: Saving reshade settings Post by Midknightprince ยป Sun 6:17 pm Something to note: when you get this thing running you have to let it load up before you start messing with any keys, and that goes for the startup of dfu proper. Private static void ShowErrorMessage(Exception e, string Title) ShowErrorMessage(e, String.Format("Reading registry ", KeyName.ToUpper())) If the RegistryKey exists I get its value If the RegistrySubKey doesn't exist return default value RegistryKey sk1 = rk.OpenSubKey(_SubKey) Public static string Read(string KeyName, string DefaultValue) Private static string _SubKey = string.Empty Private static RegistryKey baseRegistryKey = Registry.CurrentUser SOLVED FFXIV Reshader Doesnt save settings. Every time I load up the game I have to redo the tutorial and.
FF14 RESHADE SETTINGS NOT SAVING INSTALL
Here is the code: public static class RegistrySettings I followed the install guide for Reshader 3.0 and am having issues with it saving my settings. Save it to a place you can access easily like My Documents. This will save your current interface settings as a. Click the 'Back up' button and then in the new window that opens, select 'Back up' again. To avoid getting crazy with this I decided to use the registry - the most fundamental way to keep app settings for an app. To back up interface settings, open the Final Fantasy XIV launcher and select the 'CONFIG' button on the bottom navigation bar. Save and then immediately Reload and it still would not retain the values on subsequent runs (probably related to when I stopped debugging could not identify the root cause) - very frustrating, likely there is an underlying bug but I cannot prove it. Using Visual Studio 2013 - there is nothing I could do to make it work reliably, I would call Save and it did not save.