Launcher using lots of memory

[bowrain]

I've had this problem since a long time ago, but this is really bugging me now. Whenever I run it, Sims3Launcher.exe uses a lot of RAM, sometimes more than 1GB, is that normal? I need to run the launcher to install sims3packs, and while the launcher itself is pretty fast, the other programs will slow down real bad. Any solution?

[Heli]

After loading and installing off downloads I close Launcher. In Task Manager I kill core.exe and EAdownload Manager. I allways start the game with Sims3(EP02).exe.

[bowrain]

I do too, I do bypass launcher when I want to play the game. That's not my question by the way I don't even play the game right away after installing stuff.

[Clifford]

There is a custom launcher  by MTS or TSR, try it. Worked fine at me.

Edith: http://www.thesimsresource.com/programs/details/category/sims3/id/115 Here is it.  Yeah I know TSR is bad blah blah blah...

[ElectricSimmer]

So therefore, there is no way in hell we will ever ever use it.

[Clifford]

So the problem wont be solved, if you dont want to use TSR's shit...

[Mirelly]

The launcher is for nitwits.

[wizard_merlin]

So the problem wont be solved, if you dont want to use TSR's shit...

What problem are you referring too?  There aren't too many people complaining about a problem which requires the use of a third party launcher.

[ElectricSimmer]

So the problem wont be solved, if you dont want to use TSR's shit...

GTFO, try to find ONE intelligent user here who'll use that shit.

[bowrain]

So, anybody else has the same issue? Launcher eating a lot of RAM?

[ElectricSimmer]

It does. Not that much for me, but still excessive (800mb roughly)

[markjs]

It's not a issue.
Well, you can call it bad optimized coding though.

You probably have a big of size of your .dbc's in DCCache;
After update 1.10.6 EA "optimized" the Launcher.

Before it would only read your installed content when you click to browse your content.
Now, it reads everything before the Launcher runs.

I have around 1.5Gb~ in my DCCache folder, so if open the Launcher it will eat my memory up to hell.
To avoid this, I move all my .dbc to another place and use the last .dbc to sum, leaving it at the DCCache folder and renaming it to the first index, meaning: "dcdc0";

[Tingeling]

The launcher reads the sims3pack files you have stored in Downloads. Create a folder under Downloads for already installed crap. Leave the sims3packs you want to install in downloads. Decrapify and open launcher. That way, it reads the sims3packs you want to install instead of every sims3pack you have. Easy peasy.

[bowrain]

I don't have anything in my Downloads folder besides 6 sims3packs of houses, so I don't think that's the problem. My DCCache folder does have about 1Gb of stuff though, so maybe that's it I don't really get what you mean by "use the last .dbc to sum" though.

[Tingeling]

I don't have anything in my Downloads folder besides 6 sims3packs of houses, so I don't think that's the problem. My DCCache folder does have about 1Gb of stuff though, so maybe that's it I don't really get what you mean by "use the last .dbc to sum" though.

I see what you mean. I had to toss my dbc files due to them slowing down my game. Another way of keeping the loading times to a minimum would be to merge package files. Search the forum and you'll find instructions on how to do that. I believe that the newest dbc (the one with the largets number) is what markjs is referring to. I have not tested this method myself, as I have not had the need to using my method. But then again, my game is fully patched and updated so it could be due to game versions.

[markjs]

Yes, that is what I meant.

For example, you can move all your dbc's except the last one to a subfolder over DCCache, then rename it to "dcdb0.dbc".
Load the Launcher, it will now consume much less memory, since you only have that one dbc at DCCache.
Install your stuff. (It will sum (insert/add) over the "dcdb0.dbc" the content, unless the final size is bigger than the default dbc size set at Default.ini [Config].DBCacheMaxSizeMB which, by default is 200Mb, it will create another dbc, "dcdb1.dbc");

Then when you are done installing your stuff, rename "dcdb0.dbc" to it's older name, and "dcdb1.dbc" to the older name and add +1 to it's index number.

For example, if you have 5 dbc's your last index is (5 - 1 = 4), meaning "dcdb4.dbc".

This method will keep the launcher of eating the whole memory trying to load all your dbc's.

[morriganrant]

Or, you could do what I do, and name your .dbc file something like Storeshit1.dbc and drop it in with the rest of the custom content, using a resource.cfg modified for that purpose. The objects still work just fine they just aren't listed in the launcher and aren't bogging it down.