Arlodon

I am late to the party but those are the correct download_depot numbers for v1.6.640 verified by others and myself. The third one down has the .exe you can check properties on and that will confirm also. How far did you get to back up and running? Forward, I see you having trouble with DAR and wouldn't you know it I use OAR. For some reason in my world engine fixes gives me a "trampoline" warning and my game will not run. So I am situationally different and an illustration why it is hard for Nexus techs as much as they know to know all the variables we have applied. I can try to be of help but recommend Leonidas or epinter check what I tell you, they helped me get back to where I was before the update. 1.6.1130 -> 1.6.640 In my bubble I am happy with my results. I also found the Steam community a good resource. Pickysaurus and others from Nexus are working hard over there as well. Good Luck! SKSE plugins https://modding.wiki/en/skyrim/users/skse-plugins Confirmation on Steam archive numbers for using the Steam console: https://steamcommunity.com/sharedfiles/filedetails/?id=3106769503

After downgrading to 1.6.640, the _ResourcePack.esl from 1.6.1130 is still in. Maybe we should use Nukem BEES for that with !.6.640. It may mess up your saves without it. Nukems Backported Extended ESL Support https://www.nexusmods.com/skyrimspecialedition/mods/106441 Downgrading SKSE from 2.2.5 back to 2.2.3 with my BEES and all else... Downgrading all the mods I updated for 1.6.1130. Take out SkyUI SE Difficulty Persistence Fix for 1.6.1130 and downgrade back to SkyUI SE - Flashing Savegames for 1.6.640 ****************Happy New Year!****************** GOT 1.6.640 BACK RUNNING! Running with SKSE64_Loader, got SkyUI, racemenu, and MCM populated. It is all back! (and protected from updates) Thanks Pickysaurus, thanks Nexus Support.

After downgrading to 1.6.640, the _ResourcePack.esl from 1.6.1130 is still in. Maybe we should use Nukem BEES for that with !.6.640. It may mess up your saves without it. Nukems Backported Extended ESL Support https://www.nexusmods.com/skyrimspecialedition/mods/106441 Thanks Nukem! You did this some time ago, wise and quick thinker IMHO. downgrading SKSE 2.2.5 back to 2.2.3 Downgrading all the mods I updated for 1.6.1130. Take out SkyUI SE Difficulty Persistence Fix for 1.6.1130 and downgrade back to SkyUI SE - Flashing Savegames for 1.6.640 **************************Happy New Year!************************ Got my 1.6.640 back up running and all the SKSE mods I had. Got good protection from updates as well. Thanks for all the help epinter. Going on vacation or take a nap... LOL

Thanks for the heads up! Great to know your position on this!

I have downloaded the three 1.6.640 folders with the Steam console, the last, the smallest contained the 1.6.640.exe. I HAD to use the Steam console, No installation directions for Depot Downloader loose files. As soon as each of the three downloads were done I moved them out and away from (D:) > Games> steamapps > content and in to this folder (D:) Skyrim 1.6.640. I am assuming these files are just as good as having downloaded directly with the app Depot Downloader to the 'outside' folder. There they will sit until I make my next move. Think I will stash a few copies of them.

Thanks, for pointing that out! OK, I will give it a try and see how it goes. ( I have Steam cloud services off) Sounds like a clever test plan to me, thanks! Will I be able to use the Creation Kit somehow with this manually managed Skyrim? or will that be sacrificed? I may come to do this like your first suggestion after seeing how to rename the shared folders of different installations of SkyrimSE.exe. I wasn't sure how to rename them and what to do after they wrote their own files for each installation. I guess in your case you have 4 sets of possible renamed bkp files in "%localappdata%\" and "Documents\My Games\". Does that look something like GOG.bkp, 1.6.640.bkp, etc. and you just have to rename the appropriate one back to skyrim special edition to use it? I would think so... for me it would be in consideration of keeping a 1.6.1130 version and a 1.6.640. Just two installations. In case 1.6.1130 becomes the better choice in the future. You have been very kind, hope to not wear you out, I am just about out of questions and just need to proceed and become experienced.

I appreciate all that, though I am thinking I would be weak on swapping game folders. i.e., MySkyrim to Skyrim Special Edition. Windows registry and Vortex already knows the Skyrim TESV/LE folder (and its staging). What if I just use my Skyrim (LE} game folder for 1.6.640? Then I would have a separate set of inis, staging folder and save games. Steam doesn't mess with LE do they? It's not a problem for me to reload the Skyrim LE staging folder with 1.6.640 mods, I only use 388 mods. What is your opinion of going this route instead of another folder unknown to Vortex and the registry?

I am an average user compared to you. If I were to get the 1.6.640 files and put them in a game folder called MySkyrim would Vortex see it as a new game to manage and not try to use the staging folder of SSE? Or do I still need to purge sse from the staging? Then it sounds like Steam still has the possibility of launching from this folder(MySkyrim) though it is outside the library, I do not get this, so you head off Steam with a launch command at Steam.? Or in Vortex using SKSE64_Loader in its command line parameter? Yep, average might be a compliment for me. You have given me more of a sense of confidence to jump in and do it. Pretty sure I can pull off getting the 1.6.640 files, the folders and Vortex and Steam a little sketchy for me to be honest but with copies I can start over if I botch it too bad.

Thank You. This looks similar to this method where it seems I do not have to download the Depot Downloader but it is built in at Steam. The person works in English and Russian and had font difficulty I do not think I would have. What is your opinion of the procedure below? The command lines are different. It may not be using my credentials that Steam would want. This option will require a little effort on your part. The guide offers an option for downloading the previous version of Skyrim (1.6.640.0), but later I will explain how you can download earlier versions if you need it. To begin with, you should press the key combination “Win + R”, and in the window that opens, write: steam://open/console. This will open a console in Steam, which will allow you to download the necessary files. Next we need three commands: download_depot 489830 489831 3660787314279169352 download_depot 489830 489832 2756691988703496654 download_depot 489830 489833 5291801952219815735 Just enter them one at a time to download files you'll need later. Important! Do not enter the next one until the previous has finished loading. When you have downloaded everything you need, go to the folder "steam/steamapps/content/app_489830". There will be three more folders with all the necessary files, which should now be moved to the Skyrim directory, replacing the files. Voila, your mods now work as before and you're (hopefully) happy again.

I currently have Skyrim 1.6.1130.exe, that is my game now. I have read this and then some... https://steamcommunity.com/sharedfiles/filedetails/?id=3106769503 It is not that easy to downgrade, reading posts of those who make the journey. Preliminary prepping for downgrade may be the unknown factor for success. Such as maybe completely uninstall, delete your game folder and contents or rename your game folder and keep it saved and make a new game folder for a clean, new, Steam download. NOT clean the files with SSEEDIT...?? Consider this all questions. Because I have not really done/tried a downgrade to success. I wonder if I am better off waiting with 1.6.1130, then with my mods restored, just protect from future updates. Can we get some opinions from successful downgraders which current method is most likely to succeed and preliminary prepping before using the method? Or maybe just what you experienced downgrading 1.6.1130? Any opinions are helpful such as why not to downgrade at this time.

As far as downgrading, I am currently not so sure I am any safer than staying where I am at. Reading posts about successfully downgrading, well not many to reassure me I can do it. Maybe several tries and which? method will give me the best chance. https://steamcommunity.com/sharedfiles/filedetails/?id=3106769503 Any successful advisors here, maybe chime in?

LOL, that is such cool infornation that faster HDT-SMP is not included in the current 2.2.5 SKSE. I have not accepted 2.2.5 SKSE from Silverlock was really ready for 1.6.1130. There is yet another update to be done. HEY! posted my success getting faster hdt-smp to update to 2.1.0. Small step for mankind... LOL I am currently not running any SKSE mods of course on 1.6.1130, just looking to update them for when the big one comes back, SKSE64 itself. Good luck, Merry Christmas!

2.1.0 is what I am trying to install, I have v2.0.7. Good Job 7531Leonidas!!! GOALLLLLLLllllllllllll!!!!!!! YES... deleting the archive completely and then download anew FIXES ME UP!!! SO thank you.... Merry Christmas! This mod has 1.6.1130 preselected, no red, and the finish button is active, got it done, I am 2.1.0 now! I have an i7 and probably have AVX but have been running without concern for it previously.

You got me! I can't figure it out. What ever happened to known business protocol using tried and tested backward compatibility on a customer base. This update is like a not ready for prime time bad mod we want to disable. OH, tis the season. Merry Christmas to you, lump of coal for MSBethesda.

Each of those steps have been faithfully done. SKSE must load and start the game to menu. It can not. Downgrade is being contemplated thank you.