DoubleYou Posted April 1, 2020 Author Posted April 1, 2020 Default is 0.06 and 0.05, so my high preset is 10 times better. ;)
TechAngel85 Posted April 1, 2020 Posted April 1, 2020 On 4/1/2020 at 9:07 PM, DoubleYou said: Default is 0.06 and 0.05, so my high preset is 10 times better. ;)Ah! Missed those zeros. I guess I was just expecting to see them at 1.1 and 1.0 like in the shots.
DoubleYou Posted April 1, 2020 Author Posted April 1, 2020 Maxing out settings causes too much of a performance hit. Limiting draw distances is key to improving performance.
Chopsicles Posted April 5, 2020 Posted April 5, 2020 (edited) On 3/30/2020 at 10:23 PM, DoubleYou said: 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.Hi DoubleYou, first off, thanks for all your work. Can you help me understand this a bit better? I would really like to be able to follow where the grass values end up and how they are calculated.If I set Grass Fade to 18.001 (the 1 is so I could follow my change), I end up with fGrassFadeRange=13501 in the ini file. Now if I add 4000 to that, it's not 18.001.. So that has me confused. Using BethINI Standalone Version-4875-3-3 Here's my entire grass section, for reference: [Grass] bAllowCreateGrass=1 bAllowLoadGrass=0 bDrawShaderGrass=1 fGrassFadeRange=13501 fGrassMaxStartFadeDistance=7000.0000 fGrassMinStartFadeDistance=0.0000 fGrassWindMagnitudeMax=125 fGrassWindMagnitudeMin=5 iGrassCellRadius=2 iMaxGrassTypesPerTexure=15 iMinGrassSize=60 Edited April 5, 2020 by Chopsicles
DoubleYou Posted April 9, 2020 Author Posted April 9, 2020 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.
DoubleYou Posted April 9, 2020 Author Posted April 9, 2020 Updated the download to remove the BethINI.ini file.
elraymundo Posted April 14, 2020 Posted April 14, 2020 I'm using MO2 (2.2.2.1) to mod Skyrim SE, and when I run LOOT from MO2, I get a pop-up window that says: Mod organizer is attempting to write to "skyrim.ini" which is currently set to read-only. The pop-up gives me three options:Clear the read-only flagAllow the write once (The file will be set to read-only again)Skip this file I haven't seen this message when I've modded the game before. This is a 100% fresh install, and the only thing I can think of that I did differently was I downloaded, installed, and ran the STEP BethINI file. The instructions for installing BethINI say to "prevent changes to the INIs, check the 'Make INIs Read-Only' box," which I did. Based on that last sentence, my hunch is that I should choose "Skip this file" when I launch LOOT and see the pop-up, but I'd like to confirm that before I spend hours installing mods. Many thanks for any help!
DoubleYou Posted April 14, 2020 Author Posted April 14, 2020 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.
elraymundo Posted April 14, 2020 Posted April 14, 2020 Ok, thank you!! That helps me a ton. I didn't want to go through all the STEP mods and then find out I did this part wrong. So just to make sure I have it right, it would be ok to go back into the BethINI app and uncheck the “Make INIs Read-Only†box? (As a more permanent option to choosing the second option in the LOOT window, as you said.)
DoubleYou Posted April 14, 2020 Author Posted April 14, 2020 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.
brandonpotter0 Posted April 15, 2020 Posted April 15, 2020 AM curious, but not sure if this has been answered already but... Will there eventually be Fallout 76 Support now that it is on steam?
Greg Posted April 15, 2020 Posted April 15, 2020 On 4/14/2020 at 9:56 PM, DoubleYou said: 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.When I saw that prompt after running BethINI, I mistakenly assumed you were recommending setting the INI files to read-only and clicked it. It didn't take long to regret that decision because Mod Organizer prompted to save the INI files every time I exited the game so I've since reverted these to writable. It's been a while since I ran it, but I don't remember seeing any text explaining that it's not recommended unless I completely overlooked it.
DoubleYou Posted April 15, 2020 Author Posted April 15, 2020 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.
DespicableMind Posted April 18, 2020 Posted April 18, 2020 Now that Fallout 76 is finally becoming what most would call a proper Fallout game, are you at all looking into adding it to BethINI? I truly can not play Bethesda games with it now, and so it would be fantastic to be able to tweak the game to a far more enjoyable state. Many thanks for all of your excellent work with BethINI! :)
DoubleYou Posted April 18, 2020 Author Posted April 18, 2020 Fallout 76 is solely an online game. Internet in my rural area is not capable of supporting online gaming at the moment, so there is no real way for me to test it. Also, I am not sure how INI tweaking may not cause problems with the anti-cheat mechanisms of the game.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now