I noticed, in TSR Workshop, when you export a file it states that it is compressing the file. If it's using the same method as the other compressions, wouldn't that explain why newer TSR Sim3Packs are dieing out too? I don't recall older Workshop packs giving that prompt on export, just noticed it in RC1.

I don't recall who said it, and the thread was deleted on MTS, but someone there had mentioned that the only sim3pack's they had disappear were the ones that been compressed. If that can be verified, may lead to a faster solution.

Well, getting ready to patch, but want to make sure I did this right:
Added:
PackedFile Mods/dbcss/*.dbcs
PackedFile Mods/dbcss/*/*.dbcs
to my resource config file,
Created Mods/dbcss/
Copied DCCache and DCBackup, Cache into dbcss, backup into a normal mods folder.
Shouldn't that work when patch is done?

I'm glad I ran across this. Haven't had many issues with the sims, but noticed just lately that my PC is running hotter then normal. Hit the fps on after reading a few threads, and saw it topping out at 270. Must give this a try and seeing how it works out.

Ok, it looks like I found my problem, it wasn't Awesome mod really. Something was bad with the d3dx9_31.dll I had in my ...\Electronic Arts\The Sims 3 World Adventures\Game\Bin folder. I changed the bad one out with the one from Awesome's framework again, from a fresh download..
Bam, game loaded.
If all else fails, give it a try.

Same problem here, which is odd.. The beta version worked perfect in 1.7, not even a hic-cup. On installing WA yesterday  and placing the newwest Awesome back in again, I've now got the problem with the loading screen progress bar not moving. Cleared the caches, cleared out any other mods and tested again, and it died out again. Double checked my framework/resource.cfg, and everythings in order.
Odd.