Thankfully, the way CC Magic works now is that it doesn't collect anything to merge from the mods/packages folder. It leaves those alone and just lists them in the legacy folder, which it doesn't touch. So, as long as someone keeps their hacks in the packages/mods folder, awesomemod will be untouched.

Anyway, decided to try it again, since it worked for you, and for some reason, it works fine now. Maybe the first awesomemod update had something it didn't like, or most likely, it was something on my end that I somehow resolved without realizing it.

Thanks for that bit of advice, Crash. 3Booter currently is allergic to CC Magic, and the Awesomemod updater, which allowed me to use it, isn't updated to the new patch (quite understandably, due to holidays and sudden patch release).

I'll update in this thread if I notice anything on my end for those of us using this method.

Hopefully this won't count as necromancy.

Since updating Awesomemod to the 1.29 patch via the updater (and then patching my game in turn), the Awesomemod Updater's been acting up. Whenever I click on the .bat file or somehow use it in another program (like CC Magic), it's given me a message I've never seen before, asking that I change my TS3 shortcut so that it points to the updater.bat file. It says I'll never see the message again, yet it comes up each time I try to boot Sims 3 using the updater.

Also, it thinks that the latest version of Awesomemod does not match the game's patch, thus refuses to start.

Aaah. Damn. Thanks for saving me a lot of confusion there!

I'll see how much I can get working on the pre-patch items and granthes's rigfix tool (since I read it will fix dbc files), and install the rest, like beds, as packages.

Man, this problem has dogged me for a while to no avail, but I figured I'd ask. I thought I had solved it but turns out I was just fooling myself.

Anyone else having problems getting store items to not appear as custom CC? If it was just that, I'd deal, but it also seems to mean any houses I download that use things from store packs won't recognize the packages as actual store items, and just pull out default base game objects in their place. Is there a string that the recompressing and/or decraping on my end gets rid of that makes this happen?

Yeah, I finally braved EA's Launcher and installed that way. Everything seems to be working fine- thanks for separating out the counters!

Yeah. I'm trying to see if I can figure it out myself and if anyone's tried anything I didn't think of, or if I missed some step. Everything else installed just fine, and I'm incredibly grateful for the work put into the files, as well as the bittorrent itself- empty thank you posts are frowned upon here for good reasons, however. It's not your guys' fault that the counters are fubar'ed.

Really, if worse comes to worse, I'll just install those via package. I'm used to counters being borked. A few people on the Custom Launcher 2 forum are looking into what the issue is with counters (since this effects any counter that's cloned from EA's), and how to install any counter without it automatically glitching when you attempt to do a corner. This'll make the fact that the store counters are separate from Moryrie's files very useful, in case you need to install them separately.

Anyone having trouble installing the counter sims3packs from the bittorrent via Custom Launcher 2?

I've tried various versions of the counter Sims3Packs (decrapified and recompressed as the instructions in the bittorrent file say, recompressed but not decrappified, the files in the mac file, etc), but when it gets to the part where it imports them in, it crashes. The log files point to whatever sims3pack it loads first (since I took some out) being the culprit. It handles other sims3packs just fine.

I'm still looking and will try some different things as I have time, but I wanted to see if anyone else had the same problem, since, from reading, it seems Sims 3's own launcher is not going to be a help either. Also I want to make sure there's nothing I've missed.

No problem. As for the Sims 3 taking out files, now I understand what you mean. If it's all store content, maybe try Moryrie's compiled package sets in the store downloads thread and compare how the game works with them versus what files you have now? I use those, myself, and they show up in game, even if they don't show up in newer lots. This is a problem that has nothing to do with Moryrie's files, however- I'm still testing out different versions when I have time. I can definitely understand the whole 'god, I don't have time for this shit' thing.

Bigpooh-

I wasn't aware the Sims 3 program *could* remove packages from the mod folder, but maybe I haven't encountered this due to using a combo of Custom Launcher (which places packages in a different spot) and the Awesomemod Updater. Was this in-game?

Edit: I was assuming you already saw this, but just in case: http://www.moreawesomethanyou.com/smf/index.php/topic,17454.0.html. If this solves your problems, chalk it up to a case of not enough searchmoar and testing things out. It happens. If I had a penny for every time I troubleshooted just by using the search button here, I guess I'd have enough for Taco Bell. I don't even like Taco Bell.

Ahh. Yeah, I found that thread earlier, but wasn't sure if it applied since nothing I have is decrapified, and I avoid the launcher like the plague. I wonder what EA did in the last update or so that changed this up; everything used to work just fine. I'll have to experiment some more to see how I can get things working again- maybe some way to have both sims3packs and packages versions installed.

Okay, adding onto this post. I'm having no luck on the package side of things. Tried a number of things, but it looks like store items just don't link up anymore.

It was referenced earlier in the thread that the game doesn't recognize Moryrie's store pack packages.

I'm running into a second problem because of this ever since I've updated- despite the store items being in my game, everything that uses store content in lots I've downloaded refuses to recognize them as those exact items. For example, the game no longer recognizes something like the Vorn sink *as* the Vorn sink from the store, so if a lot uses it, it'll just default to the base EA sink. However, the Vorn sink still shows up when I look for it- it's just shown as another custom package.

Content installed via expansion packs, as well as plain ol' custom content, works just fine.

Going to do more troubleshooting later, but is anyone else running into this problem? Even running a game with only a few hacks (like nointro and awesomemod) produces the same problem. Should I try decrapifying (which I want to avoid), or should I combine them into a dbc file? If I'm the only one with the problem, that'll narrow things down to a setup specifically on my computer.

I've reposted them with the artist's permission at SimsCave here: http://www.simscave.com/index.php?topic=21602.0

If you'd rather not look through all the files, someone else also uploaded just the medieval dresses here: http://www.simscave.com/index.php?topic=21530.0

Before. Granted, with the amount of packages I have, it takes Sims 3 a while to load up. I'll try booting it up without any packages, save hacks, and wait to see if I need to press any buttons before Sims 3 will boot up.

Edit: Yeah, it automatically boots Sims 3 up. I didn't have to press any keys to get Sims 3 to start booting- it's just my horrid bloated packages folder. I'm actually in the process of cleaning up and I'm picky on quality (no transparency issues, textures have to fit well, no shoddy modeling) on top of it, but still, I have a large folder.

Also, a belated thanks for including me in the credits. I can't believe I missed it the first time; I didn't even think to look since I figured I was the one who should thank you instead!

Yeah. What I should have done before I updated was to check to see if the problem worked just fine when using it outside of Custom Launcher, and whether or not it's just that coupled with the 64x system. I'm kicking myself for not thinking of that. If you want me to test that for you for future reference, I'd be more than willing to.

Anyway, program was updated. The code that came up went by too fast to read until it started checking to see if there were any updates on any of the programs. The only time I had to press any keys was the credits screen, where you listed people you wanted to thank. It loaded up Sims 3 without a hitch, and worked perfectly with Custom Launcher.

 

I tried the newest version, if just to see if it no longer gives me an Error 1, but, unfortunately, it still does. The new file is in the windows directory and everything.

I'm... not even sure why I'm still getting this error, but eh, 64x systems just always seem to have weird stuff happening all around.

Yeah, I'm not sure what happened there either. It works now, however!

The updater works just fine now, though a new problem has risen that's never come up before. Usually, I use program in conjunction with Granthes's Custom Launcher (which now has included a way to use a custom startup file if needed).

Now, when I use the updater with the Custom Launcher, I get an error code 1. When I use the updater or the custom launcher by itself, however, they both work just fine. This has never come up before, so I figured I'd report it in case other people have the same problem, or if it was a symptom of a larger problem.

If you were already aware of this, my apologies. I haven't had any problem using both until v.2.2.1.

I updated to v2.2, and while it worked perfectly before, now I keep getting Error code 4. I made sure that the wget and unzip programs were in my windows directory, but it still keeps giving me Error Code 4 no matter what I do. I use  Windows Vista 64, and I've had no problems until now.

Already done. I was just seeing if I could work it out myself until granthes had a chance to implement it. I was doing it the other way around, but I couldn't figure out what file the Custom Launcher used to open Sims 3.

Right now, I use your program for when I'm peering through new packages that I want to delete, and granthe's for when I want to load the massive loads of packages in my downloads file, so it's all good.

This program is awesome, though I'm currently trying to find a way to use this program in conjunction with granthes's Custom Launcher on MTS, either by somehow forcing the Custom Launcher to open the Updater or by rerouting it. That would be *perfect*.

Aaaah. I didn't realize that. Now I'm glad I checked here before pointing this out to those creators- they'd have no real way of fixing it unless they just started from scratch.

I've noticed this lately with people who are making patterns for the game, and this may produce trouble with people (like me), who use packages instead of throwing Sims3packs into the launcher. I haven't tested it with combined packages yet, so YMMV.

It seems that, when patterns are made with only one layer (ie, if you look at the file in Portal, you'll see the image on one image while the other layers are blank), Sims 3 can't read them as package files. It'll just hang as soon as you go into CAP. It can, however, read them if it's installed as a sims3pack via the launcher. Why? Beats me. I'm not at the level of awesome needed to figure it out. I've tested it on a new neighborhood with no hacks installed aside from awesomemod, and I still had the same problem.

I'm not sure why it does this, but I've recently run into this problem, and it's vexing me because more and more pattern makers are using this route to create patterns. I'm simply not installing packages from creators that do this, so my game's fine, but I want to know if it's just something that's only happened to me and not anyone else before I start letting the creators know.

Hm. I tried using it, but it simply says 's3ce has stopped working'. Unfortunately, I think this is due to me having the 64-bit version of Vista.

Probably! Goodness knows where the hell I got that idea into my head. Everything else works smoothly, and I like the 'sort CC' button. I've been pretty lucky- so far, everything, including mods, is working perfectly.