downloading old version isn't working
I'm in the process of downgrading to 0.8.3.3 but when I put the command into the console it isn't working. It seems stuck at the downloading part?
28 Replies
That's almost entirely a Steam issue? From prior experience though, I would suggest waiting it out. It doesn't give progress updates during the download (it is ostensibly a developer feature).
I'll keep an eye on it. It should let me know when it is done downloading, though- right?
But it does look like I put the command in correctly?
Yes and yes.
Alright, I did the steps, but when I tried to open it Steam immediately tried to update.
>docsearch have two versions
This is the best result I got from the SMD :
https://docs.ficsit.app/satisfactory-modding/latest/Development/UpdatingFromSml34.html#_switch_to_visual_studio_2022
Upgrading from SML 3.4.x to 3.5 :: Satisfactory Modding Documentation
The contents of this page will change frequently! Keep your eyes on the #modding-info-feed discord channel to be notified when updates are m...
Hmph, nope.
Oh, I'd seen it in an anchor, I guess those aren't indexed. Anyway: https://docs.ficsit.app/satisfactory-modding/latest/faq.html#HaveTwoVersions
Frequently Asked Questions :: Satisfactory Modding Documentation
You can find answers to frequently asked questions on the modding discord (and about modding in general) here. Consider using your browser...
Alright. I don't need two copies, but the shortcut argument likely is what I need.
Well, no, because without taking a copy out from Steam's directory, Steam is still going to update it. The
-NoSteamClient arg just means it doesn't log in to online services through Steam.Ah. I see.
Well, I also got this
I'm not entirely certain. I'm not going to tag in the usual suspects specialists, as I don't want to pressure them into responding to something they've already clearly noted is an unsupported action. That said, if you drop your debug log here, I'll see if I can work something out.
I think, however, that perhaps Satisfactory is falling over the AMD FSR upscaler there, potentially due to it not existing in the older version of Satisfactory? If that's the case, it could be simply that your engine.ini calling it is the problem.
Try this, as a quick test: navigate to
%LOCALAPPDATA%\FactoryGame\Saved\. Copy and paste the entire Config directory somewhere very safe (that is not within the Satisfactory file structure at all), and then delete the original one. Once you start the game again, it will allow the engine to recreate the necessary files with the appropriate includes for the version of the game that you're playing.
If that works, we can look at copying across the necessary settings from your old Config directory to get you back to where you were.
To be clear, I don't have first hand experience with this error and I am troubleshooting as we go. It is entirely possible that this module is being called from elsewhere.
[Unfortunately, I'm not sure if the configuration files also have the possibility of a common hierarchy (like step 6 does for the save games), so you may need to undo anything you do here if you go back into the original Steam version. As such, keep that backup of the Config directory, as you may need it again later.]Well, none of that did anything. Same error.
Which exact debug file do you need?
>debug
We need more information to help you. Before launching the game again, open the Mod Manager and use the "Generate debug info" option, then send the zip file produced in #help-using-mods. This ensures that your help request won't get buried and forgotten in other, non-help channels!
If you need to access older log files, see https://docs.ficsit.app/satisfactory-modding/latest/faq.html#Files_Logs
Oh, that one.
-# Responding to
Key Details for SMMDebug-2025-01-30-19-02-08.zip triggered by @Devil's AdvocadoOh, I probably should've seen that coming. Those modules are some of the first things to load, so there's not much to the log.
I did have a look through patch history though. FSR was well established by that time, and the last update to it I can see was before your 0.8.3.3 build.
Do
FactoryGameSteam-FFXFSR3Settings-Win64-Shipping.pdb and the .dll version actually exist in D:/SteamLibrary/Steam/steamapps/content/app_526870/depot_526871/FactoryGame/Plugins/FSR3/Binaries/Win64 ?Those files exist three times on my computer. In the depot, in the install that I've followed the instructions on (as you'd expect, since it's a copy of the depot) and in my recycling, probably from the up to date install I deleted.
It doesn't seem like the depot download works... Would a different instance work better?
I can't say that I've come across issues before with this depot, but this is not exactly a common thing that is attempted either, heh. I would say that it's certainly worth trying a different manifest. I know .3.3 was the latest U8, but .3.2 and even .3.0 might be worth a try. You could also try the latest U8 Experimental version, 0.8.3.1.
An alternative approach might actually be to try a version from before when FSR was even introduced in the first place. It was added in 0.8.2.4, so still well within the U8 era. Try 0.8.2.3?
Alright. I'll try .3.0 first...
How do I figure out which manifest is .3.0?
Dates.
Official Satisfactory Wiki
Category:Patch notes
PS: I had a look, and there are other methods involving modifying Steam's manifest file for the game that will temporarily stop Steam from updating your current install, but 1) if you get the manifestid wrong in the manifest file, congrats, you just nuked your current Satisfactory install; 2) you have no control over when Steam decides it is going to overwrite the manifest file itself and resume updating (hope for months, plan for hours); 3) it is even less supported than the already not-supported method above; 4) the page detailing the process is off-site, so I cannot and will not be linking it. You can search it out, but only do that if disk-space is at a premium for you. You'll be entirely on your own, and I cannot vouch for the method personally (but it does pass a general sniff-test). I will not be elaborating further.
I had recently had my install nuked and eventually I won't need this install. I'm fine with this being my only install for now.
Sorry this has been slow, I got sick. Thank you for keeping up with this.
Still, it shouldn't really matter; once I take the file outside of the steam folder it won't attempt to update it, right? Simple enough.