Halde

You are amazing, Auto Parallax fixed it entirely, thank you very much!

Hello all! I have an issue with some specific meshes, namely farmlonghouse01.nif, farmhouse05destroyed02.nif and farmhouse06destroyed02.nif all in Winterhold. I found another one hours of play back, but it didn't bother me, as I thought it was a one off, so I left it, can't remember where though. These houses are lightblue-greyish in a monochrome colour. The only two mods I have that does something with these meshes are SMIM an Flickering Meshes Fix. In the console it said that Dyndolod.esp was the last change for two of them, and the other was Better Dynamic Snow.esp that was the last change. I've been trying to figure out what is causing it, mainly by searching on different forums, but couldn't find anything that was causing this. I should note I am not doing an exact STEP guide, but I hoped I could seek help here anyway. I have multiple mods not in STEP, and I'm also using Rudy ENB SE for Cathedral Weather. However the only mods, according to the console information, that does changes these files are mods within STEP, so I thought it might be something I messed up along the way. So far I've tried turning off some mods, that had no impact, (Skyrim 202x). I've tried messing around with enb setting, setting EnableTerrainParallax=false (was =true), also no effect. Someone said it could something with bEnableImprovedSnow=0 (normally =1) in Skyrimprefs.ini, this change also did nothing. Multiple times I've run into people saying it might have something to do with parallax (not my specific issue, but something similar), however I'm pretty sure I don't have anything in parallax, except Skyrim 202x which had nothing to do with the issue. I hope you can help me! PS: I couldn't figure how to do screenshots on my keyboard, which is why these are not attached, and I didn't attach a complete modlist, as I thought it was too much to ask for someone to go through that. I will provide if asked of course. I merely thought, that if someone had a good idea was this would be, I could try troubleshooting further. Sincerely ~Halde

Thank you, I didn't get this. Wiki seems to be down atm, but will check it once it's back up

Hi! Basically title, is this possible? I went through the section in the OSD of the .ini, but it didn't seem to give the option to change the key. It's not possible for my laptop to produce the hotkey, due to it using left shift for the insert key. ~Sincerely Halde

About Embers, yes, reinstalled the mod to make sure. I will try reducing particle lights!

I should note that I'm running ENB and thus the post-processing part of the guide. Been running with Light preset. I've tried changing to Milk Drinker, with no or very minor change in fps.

Hi all! Issue is pretty much in the title. It's mainly noticeable with fire, such as many candles, or the cooking fire in inns, and especially Flame Atronachs, due to often being up close to them, also I summon them myself. I play in 1st person mode, and if up close my fps drops to about 10. I'm running about 100 fps most of the time in the open world. This fps drop also occour if close to freezing FX such as the crystals that Ice Wraiths leaves on the ground. There may be other effects, but not so far. It's noticeable that normal camp fires and flames in the torchbowls (I don't what their called, they appear for lighting purpose in many place, for instance the entrance to Whiterun, made of metal). Maybe this is just because of the scale of the flame. Also casting Flames, Firebolt and having fire in hands doesn't affect fps noticeably. Is this just Skyrim? I'm running a laptop, but with a RTX 3070 TI (with MUX switch), so I believe I should be able to run everything smoothly on that account, but perhaps not. Hope someone can help call this. ~Best regards Halde

I just assumed that due to the file name starting if po3.

Yes, I did install the correct version, there is only one page, where i choose the topmost choice, which is the newest version.

Hi all! Hope you're not feeling like I'm spamming lol. I've been getting this error (see screenshot) when I launch SKSE, during benchmark testing. I also got this my previous install (which wasen't pristine, so I started over). Now I can start the game, and test fps and such without a problem. But since is error is not adressed in the guide, I'm thinking I'm doing something wrong or I missed something. I assume it has something to do with powerofthreeTweaks. As I said it's not posing a problem atm, but I don't know if it will be critical down the line. Hope this can be cleared! ~Sincerely Halde

Ah ok! Great thank you! I have been tinkering with it now, and I'm experiencing a vast fps increase when lowering preset. From the high to medium 15-20 fps. So this is great Thanks <3

Sorry if I was unclear. I'm following the guide per the letter, and my understanding is from the above copy-pasted step from the guide, that when benchmarking, I should change the Bethini presets, if my average fps is not at or above 120. Furthermore, after changing the presets, and this is the key sentence, I should go back and change the setting according to the instructions given in the "Bethini Baseline Configuration" step, THEN test the new benchmark. So this is where I first assumed, that the Bethini presets changes way more settings than the "Bethini Baseline Configuration" actually changes, thus giving more performance if changing to a lower preset and then changing some of the settings back according to the "Bethini Baseline Configuration". Now, just to be sure: you say below the photos, but there are settings described above the photos in the "show/hide" menus of the "Bethini Baseline Configuration" - is it these and only these that should be changed after selecting a lower preset and then disregard the rest of the settings presented in the photos? Also in the guide, the sentence I mentioned seems to have been replaced by: and otherwise repeat all of the BethINI Setup instructions in their entirety. Personally this would draw me to the same conclusion as the other sentence, but maybe I'm just slightly moronic in this regard. Thank you both for the answers - I greatly appreciate it!

Hi all! So I'm benchmarking my game atm before postprocessing, running somewhere between 90-130 fps in the exterior worldspace. I've been fiddling around with Bethini, started the first benchmark without changing it from the beginning of the guide. Then I went medium, since i thought fps was a bit low in somewhere. Then to low. As instructed I changed the setting as per the instructions after setting the presets to medium and then low. I couldn't register any change in fps from the high preset to the low preset I ended with, leading me to believe, that I misunderstood the following: Selecting a preset in BethINI makes changes to many settings, so ensure all BethINI settings match those in the instructions, particularly for Basic, Detail, and Visuals tabs I understand this, that I should, when i hit the "Low" preset, change the mentioned settings back to the instructed settings within the "Low" preset. Considering I went from the initial high preset through medium to low, without any noticeable changes in fps, it leads me to believe that I have in fact misunderstood this sentence in the guide. Also I wanted to ask, in some of the old guides, there were a guide to the settings in Nvidias control panel 3D settings. I haven't been able to find anything similar for the current guide, is this me missing something? I have a MUX switch on my laptop, which I use when gaming to run everything on my 3070TI, but other than that I haven't messed with anything in there except Ultra low latency and v-sync as per the guide. Hope you guys can help me with the right understanding of these things!

My screen is 240hz though, so shouldn't vsync synchronize to that cap if it was disabled?

Btw, I did encounter a little issue when testing, I forgot to mention. I couldn't remove the fps cap of 60 for some reason. I did the change in display tweaks sse first, it showed constant 60 fps, then I went to bethini and changed the fps in there to 300, which also didn't do anything about the cap. This is not otherwise something I have been interfering with, so not sure where the 60 cap is coming from?