Outfit Manager has been out for about a year now, plenty of time to learn about the kinds of problems users can run into. The goal of this article is to explain in more details what can prevent OM from working and how to possibly fix it. English is not my first language, sorry if some sentences are weirdly structured.
Installation
Installing OM consists of simply copying the SwGame folder from OutfitManager into your Jedi Survivor folder.
But I'll go a bit more step by step here:
- Locate your game install folder
Steam : Click the Gear icon > Manage > Browse Local Files
EA : Manage > View Properties > Browse
Epic : Click the ⋯ button > Manage > click the little folder icon next to the Uninstall button
This takes you to your Jedi Survivor folder - Download the mod
Click the big Download: Manual button, or go in the files tab and click Manual Download on the Main file.
You can save the downloaded file anywhere, I suggest putting it directly in your Jedi Survivor folder. - Extract the mod
Every mod you download on Nexus comes as a compressed file like .zip .z7 or .rar. You might have file extensions hidden by default so you won't see the file you downloaded is actually a .zip file.
Mods cannot function when compressed. You have a few options to decompress files; just pick one, they all give the same result.
A - Right click the Outfit Manager zip file > Extract All...
- A window pops up letting you set a path for extraction, input or browse to your Jedi Survivor folder
- Click Extract
OR
B - Double click the Outfit Manager zip file, this lets you go inside the compressed file.
- You see a SwGame folder, right click it and click Copy (or press Ctrl + C)
- Go back into your Jedi Survivor folder
- Right click in an empty space in the folder window and click Paste (or press Ctrl+V)
OR
C - Extract the Outfit Manager zip file somewhere else (like on your desktop or whatever)
- Drag and drop the Outfit Manager SwGame folder in your Jedi Survivor folder. NOT over the existing SwGame folder, next to it.
OR
D - Whatever you do, just put the Outfit Manager's SwGame folder inside your Jedi Survivor folder, we want OM's SwGame folder to merge with the game's SwGame folder. We DON'T want OM's SwGame folder to go inside the game's SwGame folder. We DON'T want to end up with .../Jedi Survivor/SwGame/SwGame/.../
That's it, that's how you install Outfit Manager. Simple enough, but it doesn't mean it will work for everyone.
Always Test Twice
Jedi Survivor very often will crash the first time you try to launch it after adding/moving files in its game directory. Might be something caused by UE4SS, I don't know.
So always retry launching the game after crashing once. But if you crash twice in a row, it's unlikely it will work.
Verify Installation
To verify that you installed Outfit Manager correctly, there are 3 things you need to check.
- Go in Jedi Survivor/SwGame/Binaries/Win64/
This folder should contain your JediSurvivor.exe along with xinput1_3.dll, UE4SS-settings.ini and a Mods folder (other files too, but if you got these you likely have the rest) - Go in Jedi Survivor/SwGame/Content/Paks/
In this folder you have the game's content files starting with "pakchunk".
You should also see: OM_Content_P and OM_SkeletonRelative_P files.
You should also see a LogicMods folder - Go in Jedi Survivor/SwGame/Content/Paks/LogicMods/
This folder should only contain logic mods. This is how we call mods that add custom code/logic to the game and need to be loaded dynamically since they usually don't replace or overwrite game assets to function. You shouldn't put mods in this folder unless the mod description explicitly tells you to do so.
In this folder you should find 3 OutfitManager files
Verify UE4SS is Working
When UE4SS works properly, you will see in Jedi Survivor/SwGame/Binaries/Win64/ that UE4SS.log (or just UE4SS if you don't have extensions visible) gets updated every time you run the game. If UE4SS.log remains at 0kb in size and the Date Modified doesn't change, then UE4SS is failing at writing on it.
Permission Issues
The main cause of UE4SS not working is because it is forbidden access to write to its own log file. Or at least that's how I see it, I am not the creator of UE4SS, I know nothing of how it works.
The main cause of UE4SS not having permission to write in your game folder is because your game is installed in C:\Program Files or C:\Program Files (x86). It's the default install location for many people.
- Run as Administrator
If you're lucky all you need to do is:
- Go to Jedi Survivor/SwGame/Binaries/Win64/
- Right click JediSurvivor.exe > Properties
- Go to Compatibility tab
- Enable "Run this program as an administrator" and click OK - Moving the Game
This is the more sure way of fixing it. Relocate the game to a different folder, a folder you have created yourself and have full control over. You can create a folder like C:/Games/ or move it to another drive entirely that's even better. Ideally, you don't want to just move the game folder manually, it's better to use your launcher to move it if it supports moving games (pretty much only Steam does).
Steam : Steam Support
EA : YouTube
Epic : Epic Games - Give yourself permissions to the Jedi Survivor folder
This doesn't seem to work for everyone, but you can still try if you don't want to move your installation.
Follow the steps in this guide
Compatibility Issues
UE4SS is compatible with Steam and EA versions of Jedi Survivor, I'm 100% sure of that.
- Xbox Game Pass
I've seen a few people have trouble getting UE4SS to work with the Xbox Game Pass version of the game. If you open your UE4SS.log (Jedi Survivor/SwGame/Binaries/Win64/) and scroll to the bottom, you might see a bunch of errors about missing AOB for FName or something like that.
If you're tech savvy enough, you can try following this guide. Otherwise, try the R457 version as explained below. - Steam Deck
I can't test any of it and I barely understand this solution, but FrostyAce13 suggested this in the comments:For anyone struggling with Steam Deck or Linux, I got it to work by installing a Microsoft application of xinput to my wine prefix utilizing proton tricks. This lets you use the manager at the cost of controller input. (At least the Xbox controller I used, but I am unsure about Steam Deck). To fix this issue just edit the wine config and add another copy of xinput into the override with a different load order on top of the one you just installed (The one installed earlier will be denoted with a *). Don't ask me why this works but it does. I will update the post if I encounter any crashes or other issues.
-TOP OF LIST-
*xinput1_3 (native, builtin) -Note: This is needed for the outfit manager to work. Must use native Windows.
-BOTTOM OF LIST-
xinput1_3 (builtin, native) -Note: This seems to enable to wine controller passthrough that is lost with native?
Quirks:
Doesnt immediately work with a new game, but if you save and load it will kick in. - The R457 Alternative
If UE4SS truly is incompatible with your game, I have added an optional file here to load Outfit Manger using R467's Mod Loader.Loading OM with R467's Mod Loader comes with two downsides:
- Outfit mods will not be automatically detected, you will need to run main.exe (Jedi Survivor/SwGame/Binaries/Win64/Mods/OutfitManger/dlls/) manually any time you install a new outfit. (because UE4SS isn't running the exe)
- When you die or reload, your outfit will remain frozen in place and you'll respawn as default Cal and need to re-equip the outfit. (because UE4SS isn't running the lua script)
Loading Outfit Manager with both UE4SS and R457 at the same time does not cause any issues, OM is made to only load one instance of itself. - UE4SS 3.0
I've tried getting any logic mods to work with UE4SS 3.0 but was unsuccessful. I don't know why or what needs to be done for blueprint mods to get properly loaded. Best to use UE4SS 2.5.2 that is included with OM.
Verify Outfit Manager is Working
When the game crashes or the OM menu doesn't open with K, that's more often than not a problem with UE4SS. But if you don't see your installed outfits or if you crash when equipping one, then it has something to do with Outfit Manager itself.
Outfit Manager has two things to do, detecting your installed outfits and letting you equip them.
Detecting Outfits
The way OM detects the outfits you have installed is by relying on UE4SS to run main.exe (Jedi Survivor/SwGame/Binaries/Win64/Mods/OutfitManger/dlls/).
Every time you launch the game, main.exe will scan your Paks folder to find mod files and detect outfit assets. Once the assets are found, a ModManager_ModPaths.sav save file will be created in your Saved Games folder along with your real Jedi Survivor saves (C:\Users\Alex\Saved Games\Respawn\JediSurvivor).
You can always manually run main.exe to see if it updates/creates the file in your Saved Games folder.
If the ModManager_ModPaths.sav file doesn't exist or hasn't been updated recently, it could be caused by:
- Antivirus
It's possible Windows Defender (or others) has decided to automatically quarantine main.exe, preventing it from updating your outfit list.Follow this guide by Microsoft Support to add main.exe to it. - Username Issue
I've seen a few cases of people with special characters in their usernames that prevent Windows from properly giving the Saved Games folder to main.exe.If that's your case, I'm sorry there is no solution yet.
Crash on Equipping Outfit
This is likely caused by outfits not being placed in /Paks/~mods/ folder. Some outfits can work when placed directly in Paks folder, but all outfits should work when in ~mods folder.
If you don't have a ~mods folder in your Paks folder, you can create it yourself. Don't forget the ~, don't capitalize, it's ~mods.
Installing Outfits
As I've stated previously, mods do not work as compressed files (.zip, .7z, .rar). You must extract them to get the actual mod files (.pak, .ucas, .utoc). Once you have extracted those, you place them directly in /Paks/~mods/ folder. Do NOT place them in a subfolder /Paks/~mods/DarthVader/ is not a good idea, which is also why installing with Vortex can lead to some issues.
This concludes the section about getting Outfit Manager working at all.
(Game crashing, K not working, Outfits not appearing, crash on equip)
Other Issues
- Cal invisible in cutscenes.
This is caused by an update to OM that fixed the equipped outfit parts disappearing in some circumstance during gameplay (mostly on mounts). I don't know how to fix this yet. - Lightsaber color gets affect even if no color is selected.
This is a bug with OM, no fix yet. But OM might eventually get an update revamping the lightsaber color selection. - Cal's face is a weird color after removing outfit.
I'm not sure why this happens, but it is easily fixed by opening the pause menu and closing it. - Achievements not working
This is a tough one to test by its nature, but I am confident this cannot be caused by Outfit Manager, but possibly by UE4SS. I do not know of any fix for this, but you can try running OM with R457 Mod Loader instead as described in the Compatibility Issues section above.
I hope this was helpful and clear enough despite the lack of images.
If you've found solutions or encountered problems with OM that I didn't cover, please share them in the comments below.
0 comments