Satisfactory Modding•4d ago

SMM can't detect game

the smm can't detect my install anymore, don't know what changed. i reinstall the game, and the directroy it is looking to exists, and the exe file is in that directory.

SMMDebug-2025-11-15-...

Solution:

i am running nobara linux 42, and extra drives don't auto mount by default, even using the system settings UI (there is a section about auto mounting media), the system mounts media to the "/rum/media/%User%/[media to be mounted]"...

Jump to solution

13 Replies

FICSIT-Fred•4d ago

SMM Version: 3.0.3

SMM Version: 3.0.3

-# Responding to Key Details for SMMDebug-2025-11-15-03-29-11.zip triggered by @shinoshi

Robb•4d ago

The mod manager works on steam/epic manifests, can you launch the game successfully through steam? I know there also used to be a bug where the mod manager didn't work if you run it from within the game install folder.

shinoshiOP•4d ago

it runs fine through steam though it dosen't give me a load session option, have to use the load save option

Robb•4d ago

Sounds like it's not persisting user settings properly. But that's probably not related to this issue I guess try with the mod manager in a different folder

shinoshiOP•4d ago

it won't start in the game directory, says it dosent exist, rund fine from my download, desktop, and root folders

Robb•4d ago

@Mircea (Area Actions) any ideas? In the mean time you could try this: >cli

FICSIT-Fred•4d ago

https://github.com/satisfactorymodding/ficsit-cli/

GitHub

GitHub - satisfactorymodding/ficsit-cli: A CLI tool for managing mo...

A CLI tool for managing mods for the game Satisfactory - satisfactorymodding/ficsit-cli

shinoshiOP•4d ago

all permissions on my steam drive are 777 +E

shinoshiOP•4d ago

running the cli tool with sudo allows it to work, so it a permissions issue of some kind i started to auto mount the drive in fstab it may have stopped working after that

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=403C-13BB                              /boot/efi                       vfat    umask=0077          0 2 
UUID=22274dfc-6016-416f-a636-e7d172bc6d94   /boot                           ext4    defaults            0 2 
UUID=a896b3c9-e6ab-4273-a6d2-d074aedd75dc   /                               ext4    defaults            0 1 
UUID=fe72b4f9-4846-43e0-82f8-6fb26ae60454   swap                            swap    defaults            0 0 
tmpfs                                       /tmp                            tmpfs   noatime,mode=1777   0 0 
UUID=10b8e2ab-ccbd-48f0-87a1-8b12e7ed4357   /run/media/shinoshi/steam       ext4    nofail,users        0 0 
UUID=115a6c91-72f1-4dac-8bc6-caa458fb9bf2   /run/media/shinoshi/4tb         ext4    nofail,users        0 0 
UUID=fb3e24e1-37aa-4b84-8ec0-5fe14f7ae3f6   /run/media/shinoshi/Incomming   ext4    nofail,users        0 0 
UUID=6c353f45-b89b-400a-b464-2302cae7dce9   /run/media/shinoshi/VideoWork   ext4    nofail,users        0 0 
//192.168.1.11/winshare /run/media/shinoshi/NAS cifs credentials=/.smbcredentials,uid=shinoshi,vers=3.0,auto 0 0
//192.168.1.119/Ripper-tmp /run/media/shinoshi/Ripper cifs credentials=/.smbcredentials,uid=shinoshi,vers=3.0,auto 0 0

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=403C-13BB                              /boot/efi                       vfat    umask=0077          0 2 
UUID=22274dfc-6016-416f-a636-e7d172bc6d94   /boot                           ext4    defaults            0 2 
UUID=a896b3c9-e6ab-4273-a6d2-d074aedd75dc   /                               ext4    defaults            0 1 
UUID=fe72b4f9-4846-43e0-82f8-6fb26ae60454   swap                            swap    defaults            0 0 
tmpfs                                       /tmp                            tmpfs   noatime,mode=1777   0 0 
UUID=10b8e2ab-ccbd-48f0-87a1-8b12e7ed4357   /run/media/shinoshi/steam       ext4    nofail,users        0 0 
UUID=115a6c91-72f1-4dac-8bc6-caa458fb9bf2   /run/media/shinoshi/4tb         ext4    nofail,users        0 0 
UUID=fb3e24e1-37aa-4b84-8ec0-5fe14f7ae3f6   /run/media/shinoshi/Incomming   ext4    nofail,users        0 0 
UUID=6c353f45-b89b-400a-b464-2302cae7dce9   /run/media/shinoshi/VideoWork   ext4    nofail,users        0 0 
//192.168.1.11/winshare /run/media/shinoshi/NAS cifs credentials=/.smbcredentials,uid=shinoshi,vers=3.0,auto 0 0
//192.168.1.119/Ripper-tmp /run/media/shinoshi/Ripper cifs credentials=/.smbcredentials,uid=shinoshi,vers=3.0,auto 0 0

i have commented out my entries on fstab, and has set my GUI automount setting back to what they were, and am gonna restart my computer now i don't have permissions to mount the drive, something i could do last week... i think thats why i added the drives to fstab ok, so i can manually mount stuff again, anf SMM will now run from the game directory

Solution

shinoshi•4d ago

shinoshiOP•4d ago

and i misread that as run, with an N where it should be rum with an M, mistake #1 second in the fstab file the options should be 'defaults' and only that these are the conditions i changed to get this working again is that the right mark to close this? @Robb (Busy) thanks for the kickstart ^^

Robb•4d ago

Close: https://discord.com/channels/555424930502541343/1439098883811836015/1439098889155121152

Gaming

Programming

SMM can't detect game

Did you find this page helpful?