Jump to content

DoubleYou

Administrator
 View Profile  See their activity

  • Posts

    7,933

  • Joined

  • Last visited

 Content Type 

Everything posted by DoubleYou

  1. DoubleYou
    If there is no text appearing at the top left, it isn't ENB. If you have an image adjustment that takes a second to realize itself, perhaps you are using an injected visual graphics mod?
  2. DoubleYou
    Does ENB show up when you run the game from there (directly launching the skse64_loader.exe)?
  3. DoubleYou
    Wow. Using Fallout 4 ENB on SSE. That's messed up. There is a SSE version of ENB now. Can you provide a screenshot of your game directory?
  4. DoubleYou
    I think I only have a prompt if the INI files already are set to read-only by the user. I can't remember what the prompt says, but it probably assumes that the user had them set to read only for a reason. I don't think I have any written documentation suggesting that one way is better than the other. Many people feel more comfortable with them set to read only. I find it more of a hindrance.
  5. DoubleYou
    Are you sure you are modifying the correct game directory? At the time of my posting, it wasn't noted what game was being modded, and I wouldn't be surprised if you have Skyrim and Skyrim Special Edition installed and are modifying the wrong one and therefore not getting the expected results.
  6. DoubleYou
    Right. Setting the read only box is only for people who are afraid some other program is going to modify your INI files against your will. The main problem I have with the practice is that if you change your in-game settings (say you up the difficulty to Legendary), the setting won't be able to stick across successive launches because the INI files are set to read only. Only case where I would recommend using it is if you are using the Enderal Launcher, or it's older Oblivion Nehrim cousin, as otherwise it makes a lot of incorrect changes.
  7. DoubleYou
    I personally recommend against setting them to read only, but that is up to the person. I can't imagine LOOT harming your INI files, so I would choose the second option.
  8. DoubleYou
    My guess is you didn't delete the d3d9.dll file for enb.
  9. DoubleYou
    I always open the console when I open the ENB editor so I don't start killing people. You need to use the secondary mouse to activate the ENB controls. I don't know if this is possible with a controller. As for the polluted water, you could turn off Particle effects by setting iMaxDesired to 0 under Particles in SkyrimPrefs.ini. But you're not going to want to do that. Did it happen in vanilla, or only after modding?
  10. DoubleYou
    Updated the download to remove the BethINI.ini file.
  11. DoubleYou
    The 18001 number is the sum of fGrassStartFadeDistance in your Prefs INI file and fGrassFadeRange in the main INI file. It is coded to place 75% into fGrassFadeRange and 25% into fGrassStartFadeDistance. 4000 plus fGrassStartFadeDistance equals fMaxGrassStartFadeDistance in the Prefs INI. Since any valid value in the Prefs INI overrides the setting in the main INI file, BethINI does not change the setting in the main INI file, which is how you have a setting of 7000 showing there. The fMaxGrassStartFadeDistance only controls the in-game grass slider in the in-game settings, so it is only important that it be equal to or greater than fGrassStartFadeDistance. The light fade slider is coded similarly.
  12. DoubleYou
    Maxing out settings causes too much of a performance hit. Limiting draw distances is key to improving performance.
  13. DoubleYou
    Default is 0.06 and 0.05, so my high preset is 10 times better. ;)
  14. DoubleYou
    I released a new release, and I forgot to delete the BethINI.ini from the archive, and it was set to Oblivion. Face-palm. Delete the BethINI.ini file from the update. I'll try to fix that asap
  15. DoubleYou
    I just tested it and it seemed to work fine. I coded it to set fGrassMaxStartFadeDistance 4000 higher than fGrassStartFadeDistance. I do realize that the way I set up the grass fade calculation is confusing, because I rely heavily on fGrassFadeRange, since it doesn't suffer from the bugs produced from pushing fGrassStartFadeDistance beyond the iGrassCellRadius. I may separate these two controls and set them to their calculated maximums to avoid issues.
  16. DoubleYou
  17. DoubleYou
    Okay, so seeing how messed up Fallout New Vegas INIs are, I decided to clean them up a bit. I have gone through the Fallout_default.ini, which is applied to both Fallout.ini and erroneously to FalloutPrefs.ini at Fallout Launcher startup (most annoying) and removed all the erroneous settings and all lines that are not different from the default. The result is given below: Fallout_default.ini As you can see, I've added comments throughout to tell of the changes from the default values. Most of these changes are assumed to be fixes (a large number of them are at least) and are recommended to be in everyone's Fallout.ini. What I recommend Edit your Fallout_default.ini file in the Fallout New Vegas directory to have only the following within: This will cause the Fallout Launcher only to apply these necessary changes to the Fallout.ini at startup. Unfortunately, this doesn't stop it from erroneously copying these to FalloutPrefs.ini initially, however, copying the default FalloutPrefs.ini below and tweaking it to My Games\FalloutNV and then applying your preset will allow you to have only the necessary lines. FalloutPrefs.ini
  18. DoubleYou
    In my research with Skyrim INI settings, I figured it would be fun to apply what I've learned to Fallout New Vegas. From this I have created a the following, which is a comprehensive list of all valid settings for Fallout New Vegas (any settings not listed here are invalid and not recognized by the game) along with their default values, with floating point values estimated to four decimal places. I have also added relavent comments left by Bethesda from the Fallout_default.ini file and some of my own. It is not recommended to use these as your INI Files! Well, actually, on second thought, I totally recommend everyone replace their FalloutPrefs.ini with the one given here and selecting your Fallout Launcher preset again, as the default INI generation mechanism makes a royal mess out of the FalloutPrefs.ini file. Extra: Unfortunately in Fallout New Vegas there is no equivalent to SkyrimCustom.ini in Skyrim, so any INI settings that you do not want to get overwritten by the Fallout Launcher or Steam should be loaded as a plugin INI or Mod Organizer INI tweak. No matter what, even if you set Fallout.ini to Read-only mode, Fallout Launcher will take control of Fallout.ini and force most if not all of its "default" settings from the Fallout_default.ini file. Please note that these values and settings are not the same as the Fallout_default.ini in the Fallout New Vegas game directory, which is copied as your default Fallout.ini file at startup. These are the default settings that are hardcoded into the game itself if the setting is not specified to be some other value. In the case of the FalloutPrefs.ini, most of the defaults are determined by the values assigned when pressing the Defaults button in the in-game settings. The rest were gathered from the saveini command with a blank INI with three exceptions. With three exceptions. Those three exceptions are the following, which are required to exist in the Fallout.ini for Fallout New Vegas not to CTD at startup. It is assumed that the default settings for these three settings are erroneous, and therefore the values from Fallout_default.ini were used. These three settings are: [Archive] SArchiveList=Fallout - Textures.bsa, Fallout - Meshes.bsa, Fallout - Voices.bsa, Fallout - Sound.bsa, Fallout - MenuVoices.bsa, Fallout - Misc.bsa [Fonts] SFontFile_2=Textures\Fonts\Monofonto_Large.fnt SFontFile_7=Textures\Fonts\Baked-in_Monofonto_Large.fnt Without these settings, Fallout New Vegas will CTD at startup. It should also be noted that four settings also had to be added to the FalloutPrefs.ini in order to satisfy the Fallout Launcher that it needed to detect game settings, or are only used by the Fallout Launcher and therefore reproduced here, as they do not affect the main Fallout New Vegas game in any way: [Display] sD3DDevice="AMD Radeon HD 8650G" ;This is the name of my video card, which would be the name of your video card. This is the only setting required for the Fallout Launcher not to run its detection. [Launcher] bEnableFileSelection=0 bShowAllResolutions=0 uLastAspectRatio=1 ;These three setting are only used by the Fallout Launcher, and these are the defaults. They have been changed in the FalloutPrefs.ini below to their most desirable values. Now here are the default INIs: Fallout.ini FalloutPrefs.ini
  19. DoubleYou
    Try changing Decal Fade to low.
  20. DoubleYou
    Version 3.3 -Bugfix: BethINI could take forever to load if it was not installed into its own directory.-Bugfix: BethINI could not locate Mod Organizer's profile directory for Fallout New Vegas in some cases.-Bugfix: Changing the game between Enderal: Forgotten Stories and Skyrim in the Setup tab was broken.-Gui Change: The Disable Precipitation setting under the Detail tab has been colored red, since it has been discovered that it can cause CTDs. Its description now also reflects this fact.-Gui Change: Changed the Gamma tweak under Visuals to be a slider.-Gui Change: Tweaked positioning of controls in the Mouse Settings section under UI.-Gui Change: Added new Console section under UI and moved/added controls to it. Also renamed controls to remove the word "Console" from them, which was the main reason to move them to their own section.-New Tweak: HUD (Color) under UI for Fallout 3, Fallout New Vegas, and Fallout 4.-New Tweak: Damage HUD (Color) under UI for Fallout 4.-New Tweak: Subtitles (Color) under UI for Fallout 4.-New Tweak: Pipboy (Color) under UI for Fallout 3, Fallout New Vegas, and Fallout 4.-New Tweak: Subtitle Speaker Name (Color) under UI for Skyrim and Skyrim Special Edition.-New Tweak: Power Armor Pipboy (Color) under UI for Fallout 4.-New Tweak: VATS Target Light (Color) under UI for Fallout 4.-New Tweak: Item Highlight (Color) under UI for Fallout 4.-New Tweak: Power Armor Item Highlight (Color) under UI for Fallout 4.-New Tweak: Wire Connection Highlight (Color) under UI for Fallout 4.-New Tweak: Input Text Color (Console) under UI for Skyrim, Skyrim Special Edition, and Fallout 4.-New Tweak: Output Text Color (Console) under UI for Skyrim, Skyrim Special Edition, and Fallout 4.-New Tweak: Selection Color (Console) under UI for Fallout 4.-New Tweak: Sun-Shadow Transitions under Detail for Skyrim Special Edition.-New Tweak: Brightness under Visuals for Skyrim Special Edition.-New Tweak: Contrast under Visuals for Skyrim Special Edition.-New Tweak: Saturation under Visuals for Skyrim Special Edition.
  21. DoubleYou
    After looking back at earlier posts, it may be the decal quantity settings you need to tweak. Try setting it to medium and see if that fixes it.
  22. DoubleYou
    What game are you playing? Not all games have the same INI settings. I would select poor preset and set texture quality to low under the Detail tab if my presumption is correct. Otherwise, it might be something else. I think I have troubleshooted this problem earlier in this thread.
  23. DoubleYou
    True. That is the main incompatibility. Other problem would be that I could not test if anything works, especially for my custom presets. Of course, I could go barebones and just have vanilla presets.
  24. DoubleYou
    This is caused by the Texture Quality setting. If textures lack the required mipmaps, it does what you describe. Changing texture quality to low fixes it.
  25. DoubleYou
    I don't have the VR version and I don't know what all is different. They probably are largely the same, but I wouldn't run BethINI on it, as it probably would blow up. However, what you could do is go inside the presets folder of BethINI and take some of the values I have in there for the settings you want. For instance, BethINI High preset setting for the settings you questioned are as follows: [TerrainManager] fBlockLevel0Distance=46443 fBlockLevel1Distance=69665 fBlockMaximumDistance=92887 fSplitDistanceMult=1.0890 fTreeLoadDistance=46443
×
×
  • Create New...

Important Information

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

  I accept