3/4 Black screen glitch

[dragonvale]

Hi all,

in attached image a glitch that occurs when I go from one cell to another but only in Windhelm area and only few times atm.

Someone have experienced the same glitch? Any clue on how to solve this?

Thanks

[Ark of Truth]

Which mods do you have installed? and have you been alt tabbing at all?

[dragonvale]

Which mods do you have installed? and have you been alt tabbing at all?

Plugins order added.

 

The only mod without plugin I've installed that make changes in Windhelm is "Enhanced textures detail (UV-tweaks)" http://www.nexusmods.com/skyrimspecialedition/mods/992/? but this problem occured even with this mod uninstalled.

 

And no, I never use alt-tab.

[Ark of Truth]

Well its not a mod which is causing the issue. Have you tried backing up and then deleting the relevant ini files?

[winny257]

I had a very similar problem, Picture was divided in the middle, right was suddenly left and vice versa.
A few days later my graphics card was broken! 

 

But in your case it is something different, because the compass is fully visible at the top.

[dragonvale]

@ winny257

Ok, first thing first, let me touch something (I'm sorry for your card)

I really don't think that this glitch is due to my GPU (Asus GTX 750 Ti 2GB OC updated with the latest driver) for the fact that, like I wrote previously, this happens only in Windhelm and in the bridge outside, and only when I go from one cell to another. Moreover, if i load the glitched autosave sometimes the glitch disappear.

 

@ Ark of Truth

Are you talking about the two ini file in My Documents? I'll give this a try.

 

Just for curiosity, I've read on steam that a user solved the same glitch by uninstalling a mod that was causing conflict with Candlelight. Do you know what he mean??

[dragonvale]

OK. Like Ark of Truth suggested, I've deleted INI files in My Documents but it didn't work.

I was going inside and outside the Palace of the Kings and the glitch reappeared.

 

But I have discovered a very, very strange thing.

The glitch occurs ONLY when I go from one cell to another cell ( automatic autosave )

but if I press F5 (quicksave) and F9 (quickload) the glitch disappear.

Then I started to think that It could be a problem related to the autosaves and it seems I was right.

In the attachments there's a screen with 3 saves (quick, manual & auto) open in ReSaver and there are a lot of Active Scripts, Function Messages and Suspended Stacks shown in the Autosave that disappear making a manual or a quick save.

 

Can anyone more expert than me (almost all of you ) explain what the hell is goin' on???

[yatol]

as if the problem was scripts

cwmapactivator... just some civilwarstuff you will always load entering windhelm (or the other cities)

dlc1serana... some stupid script for when serana is following you (that script should be in a quest, )

terminated xxyyzzzz... that script do nothing, game kill it

ms11... you aren't doing ms11 or you have done it script have nothing to do and suicide itself

 

50 scripts that's nothing

it's the oncellattach of dyndolod

1934 in that building...

 

nmm? rename data folder to _data

copy paste skyrim bsa in a new data folder

load the game with only skyrim esm and go check windhelm

then copy paste _data folder and check

then enable a few esp and check

will be faster to find out where is the problem like than than messing randomly with things to add new problems

[dragonvale]

nmm? rename data folder to _data

copy paste skyrim bsa in a new data folder

load the game with only skyrim esm and go check windhelm

then copy paste _data folder and check

then enable a few esp and check

will be faster to find out where is the problem like than than messing randomly with things to add new problems

Many thanks for pointing me to the right solution.

I'd installed an old Skyrim vanilla armors replacer - nif files converted for SSE and .esp loaded and saved with SSE CK - but I've find out that the gauntlets meshes of the stormcloack's armor were not converted properly, causing this black portion of screen.

This is why it only happened in Windhelm. Reconverting these two meshes fixed the problem.