Jump to content

DoubleYou

Administrator
 View Profile  See their activity

  • Posts

    7,933

  • Joined

  • Last visited

 Content Type 

Everything posted by DoubleYou

  1. DoubleYou
    Thanks! I appreciate the plug. BTW, if you message z929669, TechAngel85, EssArrBee, or Vuud (myself) on the Nexus, we can give you a fancy Mod Author badge.
  2. DoubleYou
    Actually, in your case, you don't need to do the uninstallation. All you need to do is the installation section. No need to mess with your mods. To be completely safe (some of these steps may actually be unnecessary)... Make a backup of your INI files in case things go wrong. In Mod Organizer, disable Automatic Archive Invalidation by clicking the profile button at top, highlighting your profile(s), and unchecking the Automatic Archive Invalidation checkbox. Close Mod Organizer Download the main file. Run the installer. Follow the on-screen instructions. Read any warnings carefully! Once the installer has completed, the Fallout Launcher will automatically run to generate your new INI files. Please ensure that your screen resolution in the Launcher is selected correctly! If using Mod Organizer, copy the generated Fallout.ini and FalloutPrefs.ini files to your \profiles\ directory. Re-enable Automatic Archive Invalidation in Mod Organizer. Redo any custom INI tweaks via the MO INI editor.
  3. DoubleYou
    I do know the problem is real, as I have experienced it myself. And Dyndolod does not harm your save game FYI. Sheson invented the frickin' memory patch. Respect. How clumsy of me to forget about read-only files...
  4. DoubleYou
    Sheson discovered the phenomenon. It's buried somewhere in his big dyndolod thread. Do a thread search and you should find the posts. Still need to add the info to the wiki.
  5. DoubleYou
    Glad it's working now. Disabling autosaves introduces LOD bugs, so no, I will not add it.
  6. DoubleYou
    Version 2.5.1 Added Browse function for setting the Game Path under SetupImproved Game Path detection process slightlyImproved INI Path selection process slightlyIncluded Readme which was left out of last release That should not have an effect, as I check for both normal and Wow6432Node registry keys. If missing, a popup asking the user to select SkyrimLauncher.exe will pop up. Previously, you could select any executable and the dialogue would accept it, so rogue values would work. I have changed this to only accept the SkyrimLauncher.exe.
  7. DoubleYou
    Probably a good idea to increase it. I just haven't gotten around to it. Increase friction and gravity are probably good tweaks.
  8. DoubleYou
    Strange, since the 2.4.1 GetFolder() function is identical to 2.5, so I don't understand how that could have changed. I probably will rewrite it so you can browse to the correct location. spINI should actually exit if the location isn't found as it is, unless it finds a bogus location.
  9. DoubleYou
    If the combat section doesn't exist, clicking the Ultra preset will not add it. This is intended. When creating new INIs, always click Default to load the default values first, as per my documentation. The presets merely update graphics quality presets now, nothing pertaining to functionality like before. This is intended. The other options should be manually chosen if desired different from Default + Preset. It sounds like you probably deleted your INI files or something prior to running spINI. Do realize that the Setup tab allows you to browse and select the correct locations for your INIs. If it doesn't correctly detect the game path, that is more serious. It should prompt you for the game path if not found at startup. I'll investigate. As a workaround, you can simply copy the spINI.ini configuration file from version 2.4.1 to your 2.5 copy and it will use the paths you have there. Or you can manually edit the INI. It's syntax is quite simple: [General] sGameName=Skyrim bCreationKit=0 [Directories] sGameSettingsPath=D:\Documents\My Games\Skyrim\ sGamePath=C:\Games\steamapps\common\Skyrim\ As to adding defaults, it simply is how the program works. If I were to go and remove all default values from the INIs, they would be rather empty looking. Indeed, default INIs are blank INIs, although "true experience defaults" fix some bugs in the actual defaults, which is what the Default INI generation is for: to fix the bugs and to give a basis from which to tweak from. Those removed settings are invalid settings that were removed from the engine, or were misprints from the start.
  10. DoubleYou
    Version 2.5 released. -Improved spINI presets to give a better overall graphical experience. This includes fixes that almost entirely remove Z-fighting on most systems, decrease certain kinds of object pop-in, and other small tweaks. Highly recommended to apply new presets. -Rewrote preset application process, which should fix some rare minor issues the previous preset mechanism had with some GUI settings. -Removed Interior Shadow Draw Distance tweak, since it can cause lights to flicker on/off when set to bad values. -Added code to automatically restrict interior shadow draw distance to be 3000 or less, since high values cause lighting issues. -Added code to search for known harmful settings and correct them. The list of known harmful settings can be found at the bottom of the Skyrim Configuration Settings Guide. -Bugfix: Medium Preset would always use the spINI preset because of a mispelled variable. -Bugfix: If the user changed to Vanilla Presets, and then back to spINI Presets, the vanilla presets would be applied instead of the spINI ones. -Bugfix: In some cases spINI would fail to detect the user's graphics card. -Fixed minor GUI scaling issues. -Binaries are now 64bit to prevent users from running it through Mod Organizer, since doing so causes issues. -Released Source Code. -Redid photos.
  11. DoubleYou
    Or you can ignore Fallout4custom.ini and just use Fallout4.ini. It is only because Fallout4custom.ini was automatically created that it became popular, even though it exists in the previous games.
  12. DoubleYou
    Well, I did confirm that high fInteriorShadowDistance causes lighting issues, and I had some high values given. Next version will remove that issue. ETA unknown.
  13. DoubleYou
    iShadowMapResolutionPrimary and iShadowMapResolutionSecondary do nothing, so yes.
  14. DoubleYou
    I actually have been seriously tempted to use that mod. I wonder if the problem is with the mesh somehow, but that doesn't explain why some have it and some seemingly don't.
  15. DoubleYou
    I have played with fFlickeringLightDistance without end and have never had it change a thing. It's a real shame that what that guy says, that keeping it the same as the other light settings, doesn't fix this.
  16. DoubleYou
    [Particles] iMaxDesired=250 not uMaxDecals. And you're right, they're still there even with vanilla INIs in ELFX. Even with deferred shadows disabled. It seems the smoke flickers between being lit up by the light from the brazier and then being unlit by it. This can be easily seen in your photo of the brazier.
  17. DoubleYou
    If it's outside, it generally can be lessened by lowering the amount of Particles to about 250 or so.
  18. DoubleYou
    The flickering can be lessened by lowering your iMaxDesired under Particles to 250 or so, although it will still remain. I am not quite sure why this happens
  19. DoubleYou
    Did he say what those two places were?
  20. DoubleYou
    I will say that the only on-off lighting I have observed is indoors, caused by fInteriorShadowDistance being set too high. If you have outdoor on-off lighting, something else is at play.
  21. DoubleYou
    Okay, I have found the issue. If you set fInteriorShadowDistance too high, it causes this. Changing it back to the default 3000 fixes it. It doesn't really add too much eye candy to increase it anyway.
  22. DoubleYou
    You should use amd gaming evolved for the video recording I believe, since it uses the GPU to record.
  23. DoubleYou
    Hmm interesting that he would say that 1 is better in general, considering the number of cases we have had lately where it caused issues. And the EnableUnsafeFixes setting is for some other fixes that cause issues with other things, notably the map, when enabled and is separate from the other settings. See the various news posts on his site for details.
  24. DoubleYou
    This is getting off-topic guys.
  25. DoubleYou
    Change it to 0. Don't know why it says to not change it when it definitely must be changed.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.

  I accept