pmalacha

http://forums.nexusmods.com/index.php?/topic/827128-nmm/

See here http://skyrim.nexusmods.com/news/225/ The below in particular: Get the latest NMM version, I believe it has been made available for download just now.

Hi guys. I have patched my Skyrim to the latest 1.8 version. I have also updated SKSE & Script Dragon. When I rebuilt my Bashed Patch I received the following error messages: I'm presuming, and correct me if I'm wrong, that these errors are due to mods not being fully compatible with Skyrim 1.8. Could someone with experience look at the messages and let me know if they look dangerous, or am I ok to continue playing? PLEASE IGNORE THIS >> Another (possible) problem I have is that after the update, my Automatic Variants doesn't seem to be rebuilding the file. When I click PATCH (or close AV window, same effect), the program just closes. It used to display little progress window previously, and I knew when it completed rebuilding the file. This progress window is no longer being displayed. Any ideas? << PLEASE IGNORE THIS And here's my modlist (sorted with BOSS): Thanks

I guess you COULD download the cracked 1.7 update and compare the files. However I DO NOT ENCOURAGE YOU to download pirate software by any means! I myself am going to stick to 1.8 for now and just wait until mods will be updated :armscrossed:

That's ok, no worries. I presume that mods will start to be updated shortly. SKSE and Community Uncapper already are up to date. I recently removed unofficial patches, but now when you say they're up to 1.8 I may install them again and see if the CTDs persist. Thanks for your input!

Thanks for your help guys. I am however pretty sure I've switched off back ups on my Win7 too... :facepalm: Time to live with it I guess. I was actually getting more CTDs while playing last night. It seemed really random and I could not determine which mods are possibly causing issues. I didn't have time to properly investigate this either.

This topic may help you: http://www.gamefaqs.com/boards/615805-/61219496

Bad news possibly... I just got CTD wanting to exchange items with faithful Lydia. It never happened before. I hope it's an odd one! I just want to revert to 1.7.7 for safety, as it was working perfectly fine :/

Hi guys. Yesterday my Skyrim was at 1.7.7 and I could happily play it. Now it's 1.8.15 (I'm presuming Steam auto update, which I was so sure I switched off... :wallbash: ). I would very much like to revert to 1.7.7, but I don't really know how, so any advice would be much appreciated. Thanks in advance.

Ok, thanks for advice. The first attempt can be found here: http://skyrim.nexusmods.com/mods/25887 Enjoy!

Great, thanks for confirming.

Hi guys Just a quick question - I am planning to create a pack of Skyrim themed wallpapers (made of processed screenshot I took in game) and upload the pack on Nexus for people to download and enjoy. Should I include Bethesda's logo on them for legal reasons? Or maybe I shouldn't for the very same reasons? :) Appreciate an advice, as I'm not quite sure and I could not find an answer online... TIA!

Nice one, this is really weird though! However, I have reinstalled my game and started anew. Now I run over 200 mods (long live Wrye Bash!) and so far I did not come across this problem. Mind you, I'm only level 20 or so, haven't got that much time for gaming lately. Shall I ever encounter this issue again I will ensure to try your solution. @blitzen - I like your way of describing things: "Not the most elegant", I lolled at this point :) Peace out, good job, and thanks for sharing :)

no, set f5 to f4. after that, play the game 1-2 hours, then you set f5 again. This issue affects not only the Quick Save but also the auto save, normal save via the menu option, as well as saving using the console command. The save function actually does create a tmp save file. This indicates that the functionality itself runs correctly, however the save process is not completed for some reason. I seriously do not believe that simply changing the config from F5 to F4 and then back to F5 resolves this issue. It definitelly more complex than that.

I will PM you on this, as we're offtop :)