-
Posts
7,933 -
Joined
-
Last visited
Everything posted by DoubleYou
-
[Fallout 4] Modding and Mods Wishlist
DoubleYou replied to Genius384's topic in General Fallout 3 Discussion & Support
But then I wouldn't be able to be shocked by the words proceeding from my mouth! -
Losing up to 12fps in average after applying the STEP INI Guide - why?
DoubleYou replied to elwaps's question in General Skyrim LE Support
Not sure if there'd be a difference when you decided to tweak the ENBoost settings. That thread is huge. Basically you got to test it like you're doing and figure it out, as it seems to be extremely system specific. -
Losing up to 12fps in average after applying the STEP INI Guide - why?
DoubleYou replied to elwaps's question in General Skyrim LE Support
You probably need to play with the ENBoost memory parameters a bit to gain back performance there. The mods in STEP aren't as taxing as you might think, and there are a lot of performance-boosting mods included. I think at one point I concluded that running STEP Baseline was about the same as running Vanilla + HRDLC. I run it on an APU with relatively little performance drop. -
Losing up to 12fps in average after applying the STEP INI Guide - why?
DoubleYou replied to elwaps's question in General Skyrim LE Support
Well, the STEP Recommended Changes and the Other Useful Changes are two different animals. I suggest you start merely with the Recommended Changes before going onto the Other Useful Changes. Think of the later as tweaks that are in a "testing" phase. Probably the one that would tank your system the most, which I thought I made clear as causing a rather severe performance drop, is the Reduce decal fade tweak. Also, I see that in every case you seem to have a minimum near 60. That's optimal. You shouldn't be trying to get more than 60fps out of Skyrim. -
[Fallout 4] Modding and Mods Wishlist
DoubleYou replied to Genius384's topic in General Fallout 3 Discussion & Support
ControlMap_Custom.txt is stored in Documents\My Games\Fallout4 by default. -
You can increase Grass Fade distance beyond 7000 without popping if you use the fade range setting.
- 10 replies
-
- SKYRIMLE
- configuration file
-
(and 1 more)
Tagged with:
-
Humph! And I thought my browser cache had gotten corrupt somehow... I got a lot of coding done at least
-
This weekend??? That's a stretch. Maybe next week or the week after. I'm writing code for a mod, trying to figure out a few Fallout 4 tweaks, and trying to see where 2.2.9.2 is at.
-
That probably can be tweaked with some of the INI settings in Fallout.ini as well. For example, the settings below: [General] uiMemoryLevelBufferSize=10485760 uiMemoryLevelIdle=104857600 uiMemoryLevelIdleCritical=26214400 uiMemoryLevelLoading=419430400 uiMemoryLevelNumPasses=3I will note that I alt-tabbed and found I was using over 12 gb of RAM (good thing I have 16 GB!).
-
My laptop is definitely on the low side of things, and it isn't a big deal.
-
There would be no difference unless you have more than 4 threads, as 4 is the default value. It would need to be tested on both a legitimate quad-core with hyperthreading and a legitimate 6 or more core processor to confirm. I guess we might as well leave it out, since most users don't have more than 4 threads.
-
Because ENBoost screenshots should be used. There is no evidence to confirm or deny that Skyrim can use more than 4 threads. It is true that it detects the number of threads your cpu has in rendererinfo.txt but it doesn't appear to change this setting accordingly. There is a small performance impact ime with the water reflections tweak.
-
INI tweaks I think that would be great to add to the STEP recommended changes. See here for details: https://wiki.step-project.com/Guide:Skyrim_Configuration_Settings Skyrim INI [Camera] fMouseWheelZoomSpeed=10 [Display] bAllowScreenShot=0 fLightLODRange=50000 [General] iNumHWThreads=4 ;Set this to the number of CPU cores, multiplied by 2 if hyperthreaded [Grass] fGrassFadeRange=10000 iMinGrassSize=40 [MapMenu] fMapWorldYawRange=400 fMapWorldMinPitch=0 fMapWorldMaxPitch=90 [Water] bReflectLODLand=1 bReflectLODObjects=1 bReflectLODTrees=1 SkyrimPrefs.ini [Display] fMeshLODLevel1FadeTreeDistance=6144 fMeshLODLevel2FadeTreeDistance=4096 fTreesMidLODSwitchDist=8192 [Trees] uiMaxSkinnedTreesToRender=200 [Water] iWaterReflectHeight=1024 iWaterReflectWidth=1024
-
https://wiki.step-project.com/Guide:Mod_Organizer#Installing
-
Hmmm... never noticed anything like that. I'll add it back in the next version.
-
It cleans out useless settings, sorts them, and removes most settings that are the same as the default value in Fallout4.ini. Some of them I took out cause if you change them, you would only produce buggy results (screensplatter setting, for instance, causes CTD if off, probably... that's how it was in Skyrim). I took out the mouse scaling settings because people should be adjusting lock sensitivity, not mouse scaling, typically.
-
FALLOUT4 Fallout 4 Default Values for All Valid INI Settings
DoubleYou replied to DoubleYou's topic in INI Tweaking
It seems there are some experimental multithreaded rendering settings included: Fallout4.ini [Display] bMultiThreadedRendering=0 bMultiThreadedRenderingDFL=0 bMultiThreadedRenderingFWD=0 bMultiThreadedRenderingPPLD=0 bMultiThreadedRenderingPPM=0 bMultiThreadedRenderingUNP=1 bMultiThreadedRendering toggles any or all of the bMultiThreadedRendering- settings, which is disabled by default. Testing each of these out, I found the following: bMultiThreadedRenderingDFL disables a bunch of objects, improving performance tremendously, but making the game unplayable simply because you can't see much. bMultiThreadedRenderingFWD disables, at a minimum, all the glass panes in the windows. It probably disables other effects, but that was all I noticed. It comes with a slight performance increase, but invariably is a buggy setting. bMultiThreadedRenderingPPLD causes weird flashing of the lights, which is unbearable. bMultiThreadedRenderingPPM kills the game. You can't move, and everything is all graphically messed up. bMultiThreadedRenderingUNP seems to be the only one that doesn't cause buggy graphics. I can't see a performance improvement, however, so it might just be internally disabled. So, if there is any performance improvement available by means of this discussion (which remains to be found), it will be with this setting (since bMultiThreadedRenderingUNP is set to 1 by default): Fallout4.ini [Display] bMultiThreadedRendering=1 Please experiment and see if this doesn't cause issues or improve performance somehow. -
I know the bug, but it only presents itself if the registry key hasn't been entered yet. My new version that I'm working on will fix that.
-
FALLOUT4 Fallout 4 Default Values for All Valid INI Settings
DoubleYou replied to DoubleYou's topic in INI Tweaking
s and str are the same, no differences. Quotes are not necessary to all strings. C-prefix is new and takes an integer value, but I am not sure if there is not some other significance to it. -
FALLOUT4 Fallout 4 Default Values for All Valid INI Settings
DoubleYou replied to DoubleYou's topic in INI Tweaking
saveini works for the prefs file when you have FalloutPrefs.ini blank in Fallout 4. This behavior is the same as Skyrim, but did not happen with some of the older games. -
FALLOUT4 Fallout 4 Default Values for All Valid INI Settings
DoubleYou replied to DoubleYou's topic in INI Tweaking
Just in case anybody was buying some of the horrible INI tweaks being thrown around the net... bMouseAcceleration is a bogus settingDon't use that magic fps tweak being popularized on redditThe salt and vinegar chips was a joke -
FALLOUT4 Fallout 4 Default Values for All Valid INI Settings
DoubleYou replied to DoubleYou's topic in INI Tweaking
Just in case anyone was wondering... Toggle Screenshots Skyrim.ini [Display] bScreenshotToFile=0 0 is off. 1 is on. Default is 1. Screenshots use Printscreen key. Screenshots are saved in PNG format to the game directory, unless you change that using the same setting used in Skyrim... probably. I'll leave you guys to figure out what this setting probably does... haven't tested it, but it looks obvious. [Display] bScreenshotToClipboard=0

