• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Nuadorion

Recruit
Dec 4, 2022
3
0
Since the 3.6 update I have had several different mods cause crashes on the main loading screen. All of them reach 80% progress, then crash. First I made sure that the game ran without mods, which it does. Next I systematically located the mods that were causing the issue, and tested them individually to see if it was a mod conflict issue. Even when they were the only active mod the issue was the same. Its also worth pointing out that most of my mods work fine. Its only a few that are causing the issue. They don't really seem to have any common features, they are by several different authors, and there are even instances of mods with similar functionality working just fine. I've tried pretty much everything. Deleting and reinstalling individual mods. Verifying the integrity of the game files. Uninstalling the game and reinstalling. Deleting the Paradox Interactive folder in my documents and starting everything over from scratch. I even reached out to the mod creators themselves, and at least one has said that they are not having any issues with the mod running whatsoever. I'm starting the process of making mods myself, so I thought I would try sifting through the game files myself to see if I could spot anything, but I can't find any glaring issues. I'm totally at a loss as to what I should do.
 
Which mods?
In no particular order:
Real Machine Worlds
Machine Shipset
Amazing Space Battles
Sins of the Prophets
Expanded Gestalts: Forgotten Queens
A Deadly Tempest [3.5.☠]
Ad Astra Technology Mod 3.5
The Great Khan Expanded [3.6.☠]
Star Wars Sith Empire Ships 3.6
Halo: The Flood (and a bunch of other mods by force728)
Zenith of Fallen Empires (and several of its sub mods)
Dawn of Ascension
Ancient Cache of Technologies (most of its sub mods)
and ~Acquisition of Technology, though that one is impossible to test individually, because its dependent on ACOT
 
I have the same issue, I find that it only occurs when the game thinks certain files do not exist, even if they do exist in reality.
I got most of my mods working by deleting all of the ugc files, but quite a few are still broken
 
So after Yohello's post I have been experimenting with the ugc_###.mod files. It went something like this. First I picked a mod that wasn't working (Real Machine Worlds) and deleted the ugc_###.mod file, then remade it using the text from the descriptor.mod file to remake it, and then I ran the game with the mod activated. It worked, but just to make sure this wasn't a fluke I tried it again, and this time it crashed. So I remade the ugc_###.mod file again and changed the permissions to read only. I started it again and it seemed to work, so I tried another mod (Sins of the Prophets). That one seemed to work too, but when I checked to see if the mod content was in game I didn't see it. So it seems for some reason that the game is trying to do something to the ugc_###.mod files, which causes the game to crash, and if you make it so that the game can't write on the ugc_###.mod files it treats the mods as if they aren't even there.
 
So I looked into what you were saying and did some digging around. I found that ugc_###.mod files which are marked as executable cannot be loaded/are-not-found while ugc_###.mod files which are not marked as executable do load.
HOWEVER, this worked for most of mods, there were a few exceptions for which after you remove the executable permission, it will be re-added after the launch of the game which then causes the crash.

Basically: Removing the executable permission from the ugc_###.mod files get the mod to load, and for the game to not spit out a file not found error. But for some mods, after removing the permission the executable permission is added on launch which causes crashes
 
 
I would clear the mod cache. If you do a lot of modding and switching mods, the cache corrupts.
This resolves all issues with errors in the logs where an object that is loaded in a mod says it was not found.

(From the Paradox Wiki)

Purging all mods

This will reset your mod settings completely (nuclear option!):
  1. Quit Stellaris and Stellaris (Paradox) Launcher
  2. Unsubscribe from all mods. Stellaris Workshop -> Your files (under your avatar) -> Subscribed items – > Unsubscribe From All .
  3. Quit Steam
  4. Go to SteamLibrary\steamapps\workshop\content\281990 and delete everything.
  5. Go to the Stellaris settings folder (one above the mod folder) and delete the following files (some of these might not be present in the actual version):
    • dlc_load.json
    • launcher-v2.sqlite (since 2.8 beta launcher)
    • in settings.txt everything inside last_mods={ }
  6. Restart Steam.
  7. Open Paradox launcher.
  8. Close Paradox launcher.
  9. Resubscribe to your mods.
  10. WAIT UNTIL ALL DOWNLOADS ARE DONE. DO NOT START PARADOX LAUNCHER UNTIL DOWNLOADS ARE COMPLETE.
  11. Start Paradox Launcher.
  12. Close Paradox launcher.
 
  • 1
Reactions: