Live2sculpt

I had to focus on some RL schedulling, but still have this project on the table.

So I'm planning on tackling this via editing the alpha channel in the associated normal. Not actually sure what to expect of an alpha channel these days. It just looks like a specular texture in grayscale. I don't see how it would provide information for a baked ambient occlusion effect.

This is probably childs play for someone here. I'm just doing a bad job of coming up with the right words to seek out the answers for myself. So I'll just post pictures here and hope someone can nudge me in the right direction. I'm retexturing Mobiusbelmont's Winter Overhaul for myself, and the bright white landscape got me focussed on the ugly gray fades that eminate from the edges where the snow texture abuts a form like a boulder, a wall, or a clump of rocks (it's all over really, but most apparent there). I'd almost beleive that it's AO effect gone out of control if I hadn't shut AO off. What is it? (pics) https://imgbox.com/fSd9TAPf https://imgbox.com/pASaztpg https://imgbox.com/1qaNi4hq And what are these glowing spots on the landscape? Are they related? (pics) https://imgbox.com/0nOzPwShhttps://imgbox.com/gczJUL7whttps://imgbox.com/oDdAPP2f I'm hoping they are are some sort of global diffuse or normals effect that I can adjust with a few lines using BethINI, but I could use a nudge in the right direction. Thanks for any tips!

Sometimes, depending on circumstances, launching Skyrim through Steam, instead of your mod organizer, could begin with a fresh resetting of your graphics etc.. I assumed that these changes would be found in the usual ini files found in the documents folder. So I backed up my ini files before starting up through the Steam launcher, but when I restored my ini files and went back through my usual mod organizer, some of the graphics settings remain altered. Clearly my assumption is mistaken. What else does the Steam launcher alter besides the Skyrim press.ini and Skyrim.ini in the documents folder?

Thanks. Understanding that distinction helped me catch up on the state of things and make my corrections.

Thanks. So when you say "Ignore ABSOLUTELY EVERYTHING about "AE" or "SE"" you're referring to the version description on Silverlock, "Preliminary AE build 2.1.4" and to just focus on the runtime number given "(runtime 1.6.342)" ?

I'm confused. SKSE64 2.1.4 is for AE, isn't it? What if you're still using SE? Should 2.1.4 work for SE as well? I don't want AE. But I'm getting this same error when trying to use 2.0.2 or 2.1.4. (I think I just started modding just as Bethesda updated again.)

Thanks good people. Perhaps my problem actually lies in what I'm now learning is a recent tumult of the sudden upgrade to AE, and a popular need to revert to SE. That was unexpected, and I'll look into that too. I had hoped the time I spent away from Skyrim would see Bethesda finally STOP messing with it, and screwing with community modding. But I guess it's still going on.

When I first started up Vortex, it was giving me guff warnings about my running it via my Administrator profile (first time I ever saw something like that). So, JIC my problems somehow stem from installing SKSE while in that state, I'm going to back up, change my profile to user, reinstall the game, manually install SKSE64, then reinstall Vortex, and try modding again. Are there any other things I might be better off installing manually rather than letting Vortex manage it? Like Papyrus perhaps? TBH, I'm not filled with confidence about Vortex now. I was prepared for a simpler "User friendly" program. Me being better off installing SKSE manually first isn't a good start.

OK. I assumed that maybe Vortex knew how to manage the SKSE files automaticaly. IMO it should not even pretend to auto-manage the SKSE install if it's not 100%. Manual install of SKSE is old hat. But how exactly does one instruct Vortex to open using the loader.dll?

Thanks. But the mousover to "Make primary" currently reads "not configured". It is gtreyed out. Smells like a noob user error to me.

Not my 1st day modding, but it IS my 1st day trying Vortex. I thought Vortex had installed SKSE64 correctly. There are 5 SKSE64 files (dll, exe, txt, dll, txt) present in the game's root folder. Clicked "Install" click "deploy", etc. Still, I'm greeted with SkyUI Error Code 1 "SKSE is not running". It's been a couple years since I used this stuff. Is this a known error or some kind? Am I forgetting to do something? Have I used Vortex incorrectly? I'm assuming I'm not supposed to manage SKSE64 manually like in the old days, but I just don't know. And I'm far too busy with RL to deal with modding hassles like I once did... the reason why I'm trying out "user friendly" Vortex in the 1st place. I hope this is a simple head-smack "but of course" fix. Thanks in advance for any tips.

My problem too. Evidently from Springtime Overhaul. A great mod in every other respect.