DoubleYou
-
Posts
7,933 -
Joined
-
Last visited
Everything posted by DoubleYou
-
Maybe I am confused, but I thought the idea of the Havok Fix mod was to dynamically alter fMaxTime to match your framerate. My FPS tweak is for applying the havok tweak to a set fps. So you would use one or the other, and not both. It does not act as a framerate cap. Now, you can use it in combination with iFPSClamp, which forces the game speed to that particular framerate, but you cannot use it with a dynamic framerate, so you would not use it with the Havok Fix mod.
-
This is the result of setting texture quality to poor. Incorrect mipmaps on textures not working well. Increasing the texture quality to low or using optimized textures should help.
-
I checked, and that line would have to have already been there. Now BethINI does copy settings placed in Fallout4.ini into FalloutCustom.ini, but only if Fallout Custom.ini already exists.
-
I will check, but that line shouldn't be there unless the user put it there specifically.
-
Shadow bias can be adjusted under detail
-
https://forum.step-project.com/topic/8963-fallout-new-vegas-default-values-for-all-valid-ini-settings/ This link lists all valid INI settings for Fallout New Vegas. They don't all necessarily do something, however.
-
Lol. I'll look into it and see what I can do, time permitting. It being summer, RL is getting in the way of any coding. I have a script that I use to do this already, so the main thing will be how best to integrate it into the GUI without it seeming out of place. It might be best as it's own standalone tool. Called INI Sorter. Add a compare functionality to it and it can just be a general INI file tool. I would probably need to figure out a way to support comments if I did that.
-
I could do that.
-
papyrus PapyrusCompiler Will NOT Run Under Any Circumstances; Even Post-Patching
DoubleYou replied to PunkN's question in Creation Kit Support
PapyrusCompiler.exe is a command line program. So if you double-click it, it will behave as you say. And yes, that is normal behavior. Also, as long as you are running the newest version of Mod Organizer, there should be no need to patch it, as Mod Organizer now can run 64-bit. Just in case you want to verify the integrity of PapyrusCompiler.exe, I have added the CRC32 hashes from my installation below... CRC32 of PapyrusCompiler.exe before patching: 7FB75A28 CRC32 of PapyrusCompiler.exe after patching: 68C8F9FE -
Fallout 4: Fallout4.ini and Fallout4Prefs.ini questions
DoubleYou replied to Infeksion's question in General Fallout 4 Support
The Fallout4Prefs.ini you found in the game folder is not used by the game. It serves as a baseline INI file for the Fallout 4 Launcher when it creates your INI files. You should also have a Fallout4_Default.ini (I might have the filename slightly wrong) in your game folder that is used by the Launcher as a baseline for the Fallout4.ini file you are having trouble with. Please ensure that file exists and is not blank. If it doesn't, let me know. That would cause your Fallout4.ini to not populate correctly. -
Okay, so this is a vanilla shadow distance issue after testing. Bethesda's implementation of shadows has always been buggy. You can try a number of things to combat it, after some testing: 1. Increase the shadow bias (fShadowDirectionalBiasScale). This will generally lessen the effect, but not much. A value of 1 was used in comparison to 0.15 (my preferred) and 0.3 (vanilla preset value). 2. Hit the Remove Shadows checkbox for a huge performance gain and entire elimination of the buggy Skyrim shadows! LOL. Not recommended. 3. Change the Detailed Draw Distance value (fFirstSliceDistance). Vanilla presets set this to 2000. Default value is 1250. BethINI High is 2800. BethINI Ultra is 3500. None of these values eliminate the effect, but you are less likely to notice it the farther you push it away from you. Of course, if you set this to 0, you will hardly notice it at all, as you would have to be right up next to it for the shadows to be at all detailed. But then all your shadows look like crap. Alternatively, push the value out to, say, 8000, and I couldn't position myself to see the issue at all. at 4000 I couldn't find it either, but you seem to have to be at just the right spot to find it at higher values. 4. Exterior Draw Distance (fShadowDistance) does play a role in this. For instance, if you put it at the same value as Detailed Draw Distance, the issue will be exacerbated. Best to put some distance between the two. Hope this helps. Personally I use BethINI High settings and could barely find this issue. I had to look pretty hard and line it up just right.
-
Are you using ENB? Or Reshade? That doesn't look like vanilla shadows that I have ever seen.
-
BethINI does not bypass the Skyrim.ini file, and if you make those tweaks, they should work. You may try to apply these tweaks via the Custom tab. If it doesn't work, you may have a plugin-loaded INI that could be overwriting it. Or if you have a SkyrimCustom.ini with alternate values, you may need to change those. Please note that if you use Mod Organizer, your INI files in Documents\My Games will not be used.
-
That game setting cannot be set by using INI files, which is why you didn't find it in the Custom tab. I know the mod page says they work, but I just tested it and they don't.
-
What build are you on now?
-
Okay. That is a possibility, because the functions that are failing are core Windows functions GetPrivateProfileString and WritePrivateProfileStringA. I am on Windows 10 Pro version 1809. Edit: Actually, GetPrivateProfileString is working just fine because it is reading the INI files correctly. Just the writing to the INI files is broken, WritePrivateProfileStringA.
-
That log file is extremely disconcerting. It seems that a huge amount of code that should be getting executed, and that is assumed to be getting executed, is getting completely ignored. BethINI should never have worked before this time if this is the case. Are you saying that BethINI has worked for you before, Diana? If so, did you check your INI files to verify that it worked? Can you use one of the older versions of BethINI successfully? Try version 2.9. It's possible that it could be a problem with Autohotkey's updates, but I can't imagine what. At least the check worked and alerted you of the error. What version of Windows are you on, and what anti-virus are you using?
-
I need to see your INI files. Please post them in spoilers: [spoiler] contents of INI file [/spoiler]
-
The setting is valid as such, but it will be overwritten by the value in SkyrimPrefs.ini. See here: https://wiki.step-project.com/Guide:Skyrim_Configuration_Settings#SkyrimPrefs.ini
-
I think you are confused. Skrim_Default.ini is only used in the creation of your INI files by the Launcher. So whether or not anything is in it is irrelevant. fLightLODStartFade is best in SkyrimPrefs.ini, or else the value in it will be overwritten.
-
After further review, I don't know what is causing that. I thought I had made a mistake, but everything seems to be working on my end. Are you sure you are pointing to the correct INI files?
-
I answered the grass fade question already. I use fGrassFadeRange to extend from the fGrassStartFadeDistance, so there is no need to extend fGrassMaxStartFadeDistance to 18000 or whatever, because that is where the grass starts to fade, and fGrassFadeRange populates grass beyond this starting distance, causing a gradual transition while moving entirely free from grass pop-in. And actually fGrassMaxStartFadeDistance merely sets the max value of the in-game slider in settings and has no real effect on the game, although obviously if you had it less than fGrassStartFadeDistance and then opened in-game settings and adjusted the slider, that would be bad. You will notice that I use the same method for light fade, as it works the same way.
-
I might have mistakenly removed that. It doesn't affect game play, just helps make the files more readable. Thanks for the report.
-
It doesn't have it. I am not sure if it needs it.
-
Version 3.2 New Tweak: Eye Environment Mapping under Detail for Oblivion, Fallout 3, and Fallout New Vegas.Unlocked Tweak: Light Fade under Detail for Oblivion.New Feature: BethINI now allows the user to decide whether or not BethINI will modify Custom INI files. The feature will only show itself if a Custom INI file is found, and if it has not been setup already, prompt the user to decide if they want it modified at startup.Bugfix: Due to reports of the invalid settings auto-detection running wild and deleting perfectly valid INI settings, I have added a routine to auto-detect if the auto-detection is bugging out, disabling this feature. I have also added a toggle for it, called "Auto-detect Invalid Settings," in the Setup tab. This should fix this bug, for which I have yet to be able to find the cause.Bugfix: The statusbar did not display everything that it was supposed to display.Bugfix: The "Please Wait: Loading" message was turned off before startup was completed.Bugfix: The main GUI elements could be used before startup was completed. They now will be disabled until startup is finished.Bugfix: If the user clicks the close button at the Choose Game dialog box while using the Autohotkey Script version, the script now will close correctly.
