Try reducing your graphics settings. Almost any large mod will crash if you are on the highest graphics settings due to the game hitting its RAM limit.

Jason wanted to separate the large game assets that don't change much, like the models, music, textures etc., from the game files, which tend to be changed a lot. That way people can download the much smaller game files when they need to update the mod.

If it's set to Highest it can be the issue, your experience be damned.

LoL its not set to the highest, anyone who plays with mods knows better then that.

whats with the snippy attitude? that's completely uncalled for.

right now the mod simply crashes, as it does for others.

I once had to do tech support for somebody who kept on saying our mod wouldn't run. Turns out he'd deleted his exe for the game and nothing worked... So yeah, it's always good to start with the basic.

My mod is set to highest settings and has over 360 textures and 800mb+ of meshes. No memory crashes currently. If you know what you're doing, I'd recommend cloning your sins directory and go about gutting things the mod isn't using. Not being a developer of the mod, it might take you some time to figure that out, though. A good place to start is the textures for default ships, planets, and any skyboxes that might not be used. I've personally removed half the UI, the player portraits, most of the icons, and all research-related stuff. Meshes are more troublesome because unlike textures the game will crash if it can't find them. A way to bypass this would be to replace either the game or mod entity files for defaults to point to placeholder meshes and gut the ones you removed references to.

Since the game force loads everything in its directories, the problem with the ram limit for a TC is usually the TC + the default game, which the patches will make progressively worse.

I'd be interested to see how replacing default assets with 0kb placeholders in a mod works out in RAM usage, but only for the benefit of others, as I have no reason to hold onto the default assets myself.

I'm about to post a v1.82 hotfix (Ironclad add new stuff for Neutron Star and Spaceship Graveyard amongst other things)... and right now I've done a full Alliance playthrough (including all research and ship abilities) and no crashes.

About to start a playthrough on Empire.. hopefully(!) I will find a bug there.

Otherwise, the issue is probably graphics related. Although my system is pretty decked out (16Gb DRAM, 2 x GTX780 SLI'ed) memory wise I occasionally get instability at maxed settings. I'm positive there is an internal memory leak in the game code relating not to system memory but memory management and allocation in the game. For example, sometimes starting a new game (without restarting the .exe) I will get unable to load textures/sound errors.

The latest patch to Requiem (4.7.1) imposes the limit of 1 super weapon per 20 gravity wells (the default is 1 per 4 wells)

You'll find the value in gameplay.constants file which I've changed to:

cannonGravityWellRatioDenominator 20

Early game you will see nothing (until the enemy gets 20 wells).
Late game you can expect probably 2, maybe 3 super weapons at most firing every 5 minutes at you.

How about give that a try and see how it goes? Post on the sins.imperial.cc forums if you will as I don't get to these forums that much.

Of course the game strategy for super weapons is offworld/auxillary governments in the starbase of your frontier worlds (the ones that get scouted by AI) and boost them later with shield gens.

If the Requiem nerf isn't enough.. the next step would to reduce the firing rate from 5 minutes to something like 10 or 15 minutes. But in Star Wars lore there is the precedent of the Galaxy Gun... so it does have a place but admittedly not a game changing place.

Grave digging this post lol... but thought I'd mention that I'd patched this (v4.8) which works with current version and all DLCs.

Busy modding Rome Total War 2, Space Engineers and 7 Days to Die these days... but still love my Sins!