SMM can't find ficsit.app

For some reason starting up SMM gives me an error showing it can't connect to ficsit.app. This is where I would make a post about this right? Oh, and here's my debug as well.
38 Replies
Muppet Burrito
Muppet Burrito•3d ago
I don't think the debug ended up posting either time, but if you can pop it in here we can see what we can do to help 🙂
McCovican
McCovican•3d ago
If SMM (Mod Manager) can't connect to SMR (ficsit.app), then indeed you'd be unable to update the problem mods. SMR is up and running however. I'd suggest the problem could be with your PC networking setup, or your internet provider then.
FICSIT-Fred
FICSIT-Fred•2d ago
SMM Version: 3.0.3
Game: CL 273254 from epic
Path: `E:/Games/SatisfactoryEarlyAccess/Engine/Binaries/Win64/`
SMM Version: 3.0.3
Game: CL 273254 from epic
Path: `E:/Games/SatisfactoryEarlyAccess/Engine/Binaries/Win64/`
-# Responding to Key Details for SMMDebug-2025-04-22-10-28-38.zip triggered by @awesome02
awesome02
awesome02OP•2d ago
That's wierd though, because my setup should not be interfering with it at all. Or at least it never has before. Plus if I were to click on the icons that lead to the support sites those work fine.
Acxd
Acxd•2d ago
:SusgeSquad:
{"time":"2025-04-22T04:28:41.331045-06:00","level":"WARN","msg":"failed to get metadata for installation","path":"c:\\Program Files\\Epic Games\\Satisfactory"}
{"time":"2025-04-22T04:28:41.331045-06:00","level":"WARN","msg":"failed to get lockfile for debuginfo","error":"failed to validate installation: did not find game executable in C:\\Program Files\\Epic Games\\Satisfactory"}
{"time":"2025-04-22T04:28:41.331045-06:00","level":"WARN","msg":"failed to get metadata for installation","path":"c:\\Program Files\\Epic Games\\Satisfactory"}
{"time":"2025-04-22T04:28:41.331045-06:00","level":"WARN","msg":"failed to get lockfile for debuginfo","error":"failed to validate installation: did not find game executable in C:\\Program Files\\Epic Games\\Satisfactory"}
>manualmove
FICSIT-Fred
FICSIT-Fred•2d ago
SMM queries the APIs of the EPIC and Steam game store apps to determine where your game is. If you moved its location after installation manually, your installer client will not know where it is. You will need to reinstall your game through your store client so that it is in a known location. This will not affect your saves.
McCovican
McCovican•2d ago
CL 273254 🤨
awesome02
awesome02OP•2d ago
That's even more odd, because I re-installed it through Epic.
Acxd
Acxd•2d ago
Idk, try launching the game once, exit it and then restart SMM
awesome02
awesome02OP•2d ago
Well, the strangest thing is happening. I tried starting it after re-installing it and now it just crashes. Looks like I'll need to keep digging.
McCovican
McCovican•2d ago
Post the factorygame.log (or -backup.log) from that crash if you can please. >logs
FICSIT-Fred
FICSIT-Fred•2d ago
It has been attached to this message. -# Responding to Crash found in FactoryGame.log triggered by @awesome02
McCovican
McCovican•2d ago
>rhiborked
FICSIT-Fred
FICSIT-Fred•2d ago
There are a few things to try if your RHI is causing crashes. 1) Try switching your RHI. If you're using DX11 or DX12, switch to the other. If you're using Vulkan, try DX12 before DX11 2) Try verifying your game files. 3) Update/reinstall your graphics drivers 4) Try disabling hierarchal Z-buffer occlusion in the game's graphics settings. 5) Try tuning your graphics card's clock down, especially if has been overclocked (by you or the vendor) For more info, run one of the following bot commands by sending it as a chat message: >dx11 >dx12 >vulkan >verifyepic >verifysteam
awesome02
awesome02OP•2d ago
>dx11
FICSIT-Fred
FICSIT-Fred•2d ago
To force the use of DirectX 11 with your game, add the -d3d11 or -dx11 argument to your game's launch arguments.
awesome02
awesome02OP•2d ago
Well, now it loads lol. Now then to figure out the rest. Looks like starting it still doesn't let SMM see the install properly.
McCovican
McCovican•2d ago
Okay, so. Don't need to hand-hold, excellent. Seems part of SMM still thinks the game's at E:/Games/SatisfactoryEarlyAccess and it's an old pre-1.0 version. Guessing you had one there at some point or another? Best bet might be to make sure that folder doesn't still exist (I'm guessing it doesn't), then nuke all of SMM's profiles. Probably some old v2 profile data making it in there. Just delete these directories: %appdata%\satisfactorymodmanager, %appdata%\ficsit, %localappdata%\satisfactorymodmanager, and %localappdata%\ficsit, then reinstall SMM.
awesome02
awesome02OP•2d ago
Yeah, before Satisfactory was updated to 1.0 I still had my 0.8 profile. I'll try deleting those and see what happens. It still fails to read my install.
FICSIT-Fred
FICSIT-Fred•2d ago
SMM Version: 3.0.3
Game: WindowsClient CL 385279 from Epic Games
Path: `c:\Program Files\Epic Games\Satisfactory`
Command Line: cmd /C start com.epicgames.launcher://apps/CrabEA?action=launch&silent=true -epicapp=CrabEA -epicenv=Prod -EpicPortal -d3d11 -epicusername=majodu -epicuserid=e6139975487746f98d8ea545eaf5d929 -epiclocale=en -epicsandboxid=crab
SMM Version: 3.0.3
Game: WindowsClient CL 385279 from Epic Games
Path: `c:\Program Files\Epic Games\Satisfactory`
Command Line: cmd /C start com.epicgames.launcher://apps/CrabEA?action=launch&silent=true -epicapp=CrabEA -epicenv=Prod -EpicPortal -d3d11 -epicusername=majodu -epicuserid=e6139975487746f98d8ea545eaf5d929 -epiclocale=en -epicsandboxid=crab
-# Responding to Key Details for SMMDebug-2025-04-22-16-32-52.zip triggered by @awesome02
awesome02
awesome02OP•2d ago
At least there's not as many errors as before though lol.
McCovican
McCovican•2d ago
Okay, progress. It has actually picked up the install now, it has a valid profile in SMM, and has the correct version & path. No crash in that log either. The only error there is that SMM didn't manage to read the EGS manifests, but since it still created a profile properly, I'm not sure how relevant that is. In what way is it still not working?
awesome02
awesome02OP•2d ago
It still can't connect to ficsit.app. I've even tried disabling my antivirus and still nothing changes.
McCovican
McCovican•2d ago
Could you screenshot the error you're seeing please?
awesome02
awesome02OP•2d ago
No description
Acxd
Acxd•2d ago
Can you access ficsit.app through any web browser?
awesome02
awesome02OP•2d ago
Yeah, even clicking on the support links in SMM opens those pages properly.
McCovican
McCovican•2d ago
Anything in the SMM proxy settings? (Mod Manager Settings -> Set Proxy) / Do you have any kind of proxying on your local network? Also, could try toggling between offline/online in SMM. [For reference]
awesome02
awesome02OP•2d ago
Nope, I don't use proxy settings, and in truth I couldn't find anything I could use for that setting, so I leave it alone. Toggling it didn't work either.
Acxd
Acxd•2d ago
Check your firewall settings, maybe it's blocking SMM
awesome02
awesome02OP•2d ago
I already tried that as well.
Acxd
Acxd•2d ago
I'm out of ideas :Sadge:
McCovican
McCovican•2d ago
Given that the pre-reinstall log there shows successful connections, like, ~9 hours ago though? Something is getting in the way. I do not know enough about the networking stack that SMM uses to say if there's any possible snags on that side of thigs (though, very doubt it tbh). But there are many things at OS, LAN, and ISP sides which could be impacting this tbh. My money is on some kind of application-level filtering.
awesome02
awesome02OP•2d ago
Hmm... well, that's unfortunate. I can't figure out what could be the issue, especially since I was able to use SMM when the 1.0 update came out at first. I'm still working on figuring out some other things, so I guess this is will have to rest for the time being.

Did you find this page helpful?