Jump to content

DoubleYou

Administrator
  • Posts

    7,933
  • Joined

  • Last visited

Everything posted by DoubleYou

  1. If you use sResourceArchiveList Enderal settings, you should be able to avoid the dummy BSA and dummy esp archive loading tricks.
  2. Typically when this happens, you simply need to wait for the Continue to appear. The only thing I change for the Creation Kit is, Allow multiple masters, add DLC support, and there was another one that caused the Creation Kit to fail at startup that I can't remember at the moment. I do notice that VSync is off, and I have found that can affect how long it takes for the Continue to appear.
  3. I would guess that your laptop isn't powerful enough for the selected settings plus an ENB. You could try to use a lower preset.
  4. That's what I wanted to see! Even has the right font now!
  5. Version 2.9 -New Tweak: Transparency AA under Basic for Skyrim, Fallout 3, and Fallout New Vegas. -Recommended Tweaks: Added fSkyCellRefFadeDistance:MAIN 600000 to recommended tweaks for Skyrim. Testing will need to be done to see if the same tweak is good for Skyrim Special Edition (been testing in my setup without issue, but need to verify that it actually is an improvement). -Behind the Scenes: If an update to BethINI is available, it will send you to the current game's Nexus page, rather than always to the Skyrim Special Edition Nexus page, if you click OK. -Bugfix/Gui Change: Entirely redid the GUI from scratch so it shouldn't look messed up if the user is using a different font or theme. Also, it looks better, and has less settings floating in mid-air with no apparent reason. Should be easier to program new features too. -Bugfix: In the Custom tab, if the user selected a section, in some cases a setting wouldn't automatically be loaded, and it would allow modification of the entire section, but wouldn't necessarily place it in the correct INI file. Now, if a setting isn't selected, the value field will not populate, and it shall also remain disabled. -Bugfix: The Custom tab correctly showed the current value for a setting only if the game was Oblivion or if the setting was in the Prefs file. Otherwise, it would show the default value. It now correctly displays the current value. -Bugfix/Kinda: The INI files in My Games would be modified to match that of a Mod Organizer profile for Skyrim Special Edition and Fallout 4. This originally was a workaround, because at the time, profile-specific INI files were broken in Mod Organizer 2. This has been fixed in Mod Organizer 2, so no longer is there a need for this workaround.
  6. Not sure what this could be. I checked on my setup, and it worked fine. Even tested Read-only, and it didn't crash. I would like to see a copy of your INI files to see if I can reproduce this with the same INI files. You can always go into the BethINI cache folder and view your previous INI files to see what's changed.
  7. I need more details. What is crashing--the game, Mod Organizer, or BethINI? And which game?
  8. The font you have showing is Courier New. Microsoft Sans Serif is what the GUI was built to use. I can replicate it now, so hopefully I can get it fixed during this cold snap we're experiencing here in Pennsylvania.
  9. I had a report about something like this a long time ago. IIRC, it had something to do with the windows theme. At the time, I provided several files to him to try and fix it, but I think he never responded, so I was left hanging. I'll try and look at it again to see if I can get it fixed. I think in your case, it's mainly because the font makes the letters too wide, causing it to overflow like that. I can probably increase the widths and fix it that way, or see if I can force a specific font.
  10. Version 2.8 -Modified Release Format: Now there are two different files you can download. The standalone version, which is prone to being flagged as a false positive by aggressive antiviruses, and the AHK (Autohotkey) Script version. The Autohotkey Script version requires an up-to-date installation of Autohotkey version 1.1.x. This can be downloaded at https://www.autohotkey.com/download/. -New Feature: Introduced the Custom tab where you can edit any valid INI setting that you so desire, at your own risk. -Behind the Scenes: BethINI's cache folder backup and log files have a much easier-to-read folder name, which makes it easier to know which backup you are restoring when you restore a backup. -Bugfix: The location for Mod Organizer files could be missed if located anywhere other than the default location. This applies to portable and instanced versions of Mod Organizer. Thanks PokemonTotalWar. -Bugfix: Checking for updates is now fixed. -GUI Change: Tree Detail Fade dropdown has been improved to include actual presets instead of the meager "Default" and "Custom."
  11. Upon further review I found a bug in the code where if you had changed the base directory from default, the check I had to find that was coded improperly, so it would always give the default value, which just so happened to be what I was using, so I never noticed. Fix will be in the next update.
  12. Okay, I looked, and there must be something special going on in your case. I use the instanced version of Mod Organizer 2 and it finds it fine. I would like to look at your log file located in the most recent folder in the BethINI Cache folder which should be generated wherever BethINI has determined your game files to be (presumably Documents\My Games\Game Name\BethINI Cache\Date\log.txt. Also if you could tell me where Mod Organizer is installed and where your profiles are located on your computer (presumably %AppData%\Local\ModOrganizer), that would be helpful.
  13. I'm not sure what causes this. Typically it is the antivirus preventing it from loading. An easy fix that has worked in the past: 1. Download and install Autohotkey https://www.autohotkey.com/download/ 2. Inside the BethINI folder, go into the Source folder. 3. Simply double-click BethINI.ahk and it should run like normal.
  14. I doubt that BethINI caused this. A simple way to test would be to go to the Setup tab and restore the Before BethINI backup. I will take a look. In the meantime, you can easily go to the Setup tab and under INI path, Browse and select the correct location.
  15. There are many bogus INI settings that don't do anything, and bNvGodraysEnable is one of them. It probably was a working setting at some point during development, but it doesn't do anything anymore.
  16. In BethINI, under the View Distance tab, drag the Light Fade slider all the way to the right. I can't remember, but I think DynDoLOD has a special thing with that too.
  17. uLargeRefLODGridSize is an unsigned integer, which means it is merely 11, and cannot be 11.11111111111111111... The fBlockLevel0Distance et. al. settings are not necessarily related to fSplitDistanceMult. But they might be. A way to test would be to set the values at zero and test the in-game effects. For example, put fSplitDistanceMult at 4 and all the fBlock distance settings at zero and see if the water anomalies are still present at Winterhold. If so, that would be an indicator that fSplitDistanceMult is not being multiplied by the fBlock distance values, as otherwise the result would be 0 and not 4.
  18. Only time I saw that happen was when an antivirus was stopping it, but it seems you have that covered. Not sure what would cause it. You could install Autohotkey and run the BethINI.ahk file in the Source folder. If that doesn't work, I am not sure what will. https://www.autohotkey.com/download/
  19. How I arrived at a maximum of around 16896 for fMeshLODLevel1FadeDist and similar was through repeatedly changing the value until it had no effect anymore. I don't know if it has a different approximate maximum, be it higher or lower, if you change uGridsToLoad, as I decided it wasn't necessary to investigate since I wanted the value merely for game performance optimization.
  20. You can get a real headache with those settings. It's a buggy system. Believe me, I have tried. I have found that raising fBlockMaximumDistance above like 100000 seems to cause more z-fighting, but that just may be because of my other settings.
  21. Do you need help restoring your original INI files?
  22. https://wiki.step-project.com/Guide:SkyrimPrefs_INI/TerrainManager A value of 4 was chosen for improved LOD detail. Of course, this value is pushing it beyond vanilla values, attempting to bring in more detail and combat z-fighting. If there are places where there are vanilla bugs, like the area you mentioned, changing the LOD settings lower may hide them, at the expense of other areas. I think the value of 4 was only used for ultra. I recommend using high
  23. Don't know which game you are playing, but mostly draw distances, i.e., how far you can see certain things in detail. If you like medium well enough, use it. The goal is to always have good fps. I tried to tweak it so that it would not be bothersome until you get to the low and poor presets, and low really isn't too terrible.
  24. Well, looking at your INI files, nothing really stands out as out of the ordinary. I loaded up your settings on my machine and traveled to Dawnstar and Winterhold and didn't notice any missing water, but I guess I don't really know where to look. If you load up BethINI and go to the Setup tab, there is a Restore Backup dropdown. Click the dropdown and select the "Before BethINI" option. That will reset your INI files to how they were before you used BethINI. See if that fixes the issues you're seeing. If they do, please post those INI files so I can compare them and see what is different. Then we can test to find out which setting(s) is/are causing the problem. If the problem still exists, however, the problem may lie elsewhere. If that's the case, try starting a new game and see if the places are still bugged. If they still are, you may need to investigate any mods you may be using.
  25. Should be an easy improvement. Please post your INI files.
×
×
  • Create New...

Important Information

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