I'm trying to hack together support for 1.6.1130+ for my UI overhaul and I'd rather not start from scratch recreating the menu... Are all the changes here to support various versions in the SystemPage actionscript? If so, are permissions open for that segment? Thanks in advance.
Edit: Also, for whatever reason, copying and pasting that entire section to test throws an error CURLY_CLOSE expected but COLON found on the loop2 line of the new code, at least in JPEXS. Not sure what the easy way around that is.
Using the vanilla skyui journal fix, and on a fresh mod list with only skyui and this mod installed, I still see $SaveGameMissingCreationsCheck . The property isnt being properly assigned even though its in the translation text file. any ideas on what could be causing this? im on 1170
EDIT: full uninstall and reinstall fixed it. steam must have fucked up upgrading to 1170 completely or something
Happy to say it works for me. I only chose the first option... no patches. If you have the "flashing save game mod" disable it before d/ling this since it's included in this mod. Thanks for this... playing novice you don't even need armor after a while... : )
I did follow your guide. It didn't work (at first), but I did finally discover the problem, which was Vortex was saving loadorder.txt and plugins.txt to the wrong folder. I have no clue why it was doing that. I removed all things Skyrim from my computer, then deleted the skyrimse profile folder from %appdata%\roaming\Vortex, and that seems to have solved the problem.
I now have 1.6.1170 running with SkyUI 5.2SE and the MCM is back. Thanks.
At the time, I was troubleshooting, which is why I uninstalled Skyrim. Turned out it wasn't necessary, as the problem was a corrupted Skyrim profile in Vortex. Not sure how that happened.
I do not know what to do. I installed this mod, but the difficulty level does not change. I move it to Legendary, but when I try to hit an enemy I realize that his amount of health is that of the Novice level, and in fact when I return to the Menu the difficulty is set to Novice.
EDIT: I was sure I had done everything according to the rules, but I was wrong: I loaded the mod between SkyUI and NordicUI, and not after these two. Now it works, the difficulty level no longer resets. Now click the endorsement
The question as to whether the flashing save game fix is included in your patch along with the difficulty persistence fix has come up in a few locations including here. Could you please post a sticky with a definitive answer. "I think so" doesn't quite cut it when you're trying to diagnose an issue. Thanks again.
Give Feedback
89 comments
I'm trying to hack together support for 1.6.1130+ for my UI overhaul and I'd rather not start from scratch recreating the menu... Are all the changes here to support various versions in the SystemPage actionscript? If so, are permissions open for that segment? Thanks in advance.
Edit: Also, for whatever reason, copying and pasting that entire section to test throws an error CURLY_CLOSE expected but COLON found on the loop2 line of the new code, at least in JPEXS. Not sure what the easy way around that is.
The property isnt being properly assigned even though its in the translation text file. any ideas on what could be causing this?
im on 1170
EDIT: full uninstall and reinstall fixed it. steam must have fucked up upgrading to 1170 completely or something
If you have the "flashing save game mod" disable it before d/ling this since it's included in this mod.
Thanks for this... playing novice you don't even need armor after a while... : )
I now have 1.6.1170 running with SkyUI 5.2SE and the MCM is back. Thanks.
Seems to be compatible with v1.6.1179 (GOG) but not with 1.6.1170 (Steam)EDIT: I was sure I had done everything according to the rules, but I was wrong: I loaded the mod between SkyUI and NordicUI, and not after these two. Now it works, the difficulty level no longer resets. Now click the endorsement
The question as to whether the flashing save game fix is included in your patch along with the difficulty persistence fix has come up in a few locations including here. Could you please post a sticky with a definitive answer. "I think so" doesn't quite cut it when you're trying to diagnose an issue. Thanks again.