|
|
Post by orangemittens on Jan 1, 2015 12:38:57 GMT -5
Introduction
This tutorial will show you how to merge multiple .packages into a single .package using Sims 4 Studio.
Note that this will not cause the swatches to all show up in a single catalog entry.
What you will need:
Sims 4 Studio .packages you want merged
Directions:
1. Open Sims 4 Studio and select Content Management from the upper menu bar. When the drop down appears select Merge Packages.
2. When the Merge Packages box pops up drag and drop the .packages you want to merge into it. Alternatively, you can click the Add button and navigate to the .packages you want to include. Both methods allow you to add multiple .packages from a single folder at once and both work just as well.
3. Once you've added all the .packages that you want to include click the Merge button. If you accidentally added one you don't want in there click on it and then click the Remove button. After you click the Merge button a box will pop up allowing you to select where you want the new .package saved. Once the .package is merged this folder will open allowing you to see the new .package in its location.
|
|
|
|
Post by win7yes on Jan 1, 2015 19:14:55 GMT -5
If I recolor 2 different objects, save the packages individually and then merge both packages, it will make both objects show up separately on Build Buy but the data itself will be on only one package right?
|
|
|
|
Post by andrew on Jan 1, 2015 19:45:33 GMT -5
win7yes, all it does is put them in the same package. They will still be separate in the catalog in game.
|
|
|
|
Post by martine on Jan 5, 2015 8:04:10 GMT -5
Thanks so much for adding a merge feature to S4Studio! I do have a question about adding packages to a merged file (as I used to do with S4PE). I merged all my 'buy mode' items into one package, and was able to open that file with S4Studio but when I tried to add additional package files, it only merged those files, not everything together. I merged all my 'build mode' items into another package, and opening that file gave me an error message (click to open spoiler): {Error message}
System.NullReferenceException: Object reference not set to an instance of an object.
at S4Studio.Data.IO.Package.DBPFPackage.<>c__DisplayClasse`1.<fetchresource>b__d(PackedResource x) in c:\workspace\thes4studio\TheS4Studio\S4Studio.Data\IO\Package\DBPFPackage.cs:line 235
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
at S4Studio.Data.IO.Package.DBPFPackage.FetchResource[T](DBPFResourcePointer index) in c:\workspace\thes4studio\TheS4Studio\S4Studio.Data\IO\Package\DBPFPackage.cs:line 235
at S4Studio.ViewModels.ObjectSwatchItem..ctor(IResourceHandle objd, ObjectCustomContentViewModel parent) in c:\workspace\thes4studio\TheS4Studio\S4Studio\ViewModels\Objects\ObjectSwatchItem.cs:line 40
at S4Studio.ViewModels.ObjectCustomContentViewModel.<.ctor>b__1(IResourceHandle x) in c:\workspace\thes4studio\TheS4Studio\S4Studio\ViewModels\Objects\ObjectCustomContentViewModel.cs:line 37
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.ObjectModel.ObservableCollection`1.CopyFrom(IEnumerable`1 collection)
at System.Collections.ObjectModel.ObservableCollection`1..ctor(IEnumerable`1 collection)
at S4Studio.ViewModels.ObjectCustomContentViewModel..ctor(IResourceProvider remoteSource, IResourceProvider localSource, DBPFPackage localPackage) in c:\workspace\thes4studio\TheS4Studio\S4Studio\ViewModels\Objects\ObjectCustomContentViewModel.cs:line 37
at S4Studio.MainWindow.<editobjitempage_onloaded>b__11a() in c:\workspace\thes4studio\TheS4Studio\S4Studio\MainWindow.xaml.cs:line 2675
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)</editobjitempage_onloaded></fetchresource>'System.NullReferenceException: Object reference not set to an instance of an object.
at S4Studio.Data.IO.Package.DBPFPackage.<>c__DisplayClasse`1.<FetchResource>b__d(PackedResource x) in c:\workspace\thes4studio\TheS4Studio\S4Studio.Data\IO\Package\DBPFPackage.cs:line 235
at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
at S4Studio.Data.IO.Package.DBPFPackage.FetchResource[T](DBPFResourcePointer index) in c:\workspace\thes4studio\TheS4Studio\S4Studio.Data\IO\Package\DBPFPackage.cs:line 235
at S4Studio.ViewModels.ObjectSwatchItem..ctor(IResourceHandle objd, ObjectCustomContentViewModel parent) in c:\workspace\thes4studio\TheS4Studio\S4Studio\ViewModels\Objects\ObjectSwatchItem.cs:line 40
at S4Studio.ViewModels.ObjectCustomContentViewModel.<.ctor>b__1(IResourceHandle x) in c:\workspace\thes4studio\TheS4Studio\S4Studio\ViewModels\Objects\ObjectCustomContentViewModel.cs:line 37
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.ObjectModel.ObservableCollection`1.CopyFrom(IEnumerable`1 collection)
at System.Collections.ObjectModel.ObservableCollection`1..ctor(IEnumerable`1 collection)
at S4Studio.ViewModels.ObjectCustomContentViewModel..ctor(IResourceProvider remoteSource, IResourceProvider localSource, DBPFPackage localPackage) in c:\workspace\thes4studio\TheS4Studio\S4Studio\ViewModels\Objects\ObjectCustomContentViewModel.cs:line 37
at S4Studio.MainWindow.<EditOBJItemPage_OnLoaded>b__11a() in c:\workspace\thes4studio\TheS4Studio\S4Studio\MainWindow.xaml.cs:line 2675
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)' Is it possible to merge in additional packages or does everything need to be re-merged? |
|
|
|
Post by orangemittens on Jan 5, 2015 9:19:18 GMT -5
Hi Martine, if you want to merge additional .packages you can open the Merge box as before and drag the merged .package into it. Then drag in the additional .packages you want to merge. Studio will ignore any duplicates you may accidentally put there and create a new merged .package. Then you can just delete the old merged .package and use the new one.
The error is resulting from the check Studio runs to see if something is a complete .package before opening it in the Studio view. It is seeing things in the merged .package that make it think there's a full .package there but when it looks for the other resources it cannot find them...probably because there is some item or other that doesn't need all the resources a standard .package has. The way around this will require a new function to be added to Studio that will allow the .package to just be opened in the Warehouse view without this preliminary check...similar to how it is able to open the Fullbuild files currently. This will be added in an upcoming version.
|
|
|
|
Post by martine on Jan 5, 2015 11:09:22 GMT -5
Ah I see, I hadn't thought of that! Does it make any difference for the end result, whether a merged package and new packages are merged, or a re-merge of all the packages? Thanks!
|
|
|
|
Post by orangemittens on Jan 5, 2015 12:58:39 GMT -5
No, that won't make a difference.
|
|
|
|
Post by lientebollemeis2i on Jan 14, 2015 11:14:02 GMT -5
I created 4 different recolors of The Intrepid with each 3 different swatches (so 12 different recolors in total). I merged the 4 packages into one package. I then opened the new merged package. So that's a recolor of The Intrepid with 12 swatches.
Now the problem is that there are no 12 different swatches but only 3 in the new merged package.
It's like 1-2-3 1-2-3 1-2-3 1-2-3 but it should be 1-2-3-4-5-6-7-8-9-10-11-12
I already tried to recolor swatch 4, but then swatch 1 and 7 and 10 are recolored again two so in the end it's 4-2-3 4-2-3 4-2-3 4-2-3
What can I do so I can have 12 different swatches in one package?
|
|
|
|
Post by orangemittens on Jan 14, 2015 13:00:41 GMT -5
If you want all the swatches to show up on a single catalog entry you need to follow this tutorial: The merge .package feature keeps each .package the same as it was before you merged it and places them all into a single .package. The other tutorial shows how to make the swatches of different .packages show up in a single catalog entry in the game. If you use both the tutorials together you will end up with a single .package and all the swatches of each present with just one catalog entry. |
|
|
|
Post by lientebollemeis2i on Jan 15, 2015 4:56:56 GMT -5
The 12 swatches are now in one package in one single catalog entry and they show up in 12 different swatches in game. Exactly as I wanted.
But when I open that file in S4S it's still like 1-2-3 1-2-3 1-2-3 1-2-3 but it should be 1-2-3-4-5-6-7-8-9-10-11-12
While in the game it works correctly :s
|
|
|
|
Post by orangemittens on Jan 15, 2015 9:16:35 GMT -5
Studio is currently written to work on a single .package at a time and once it finds the resources it needs to open a .package it will open it. Changing the prototype ID doesn't make the .packages the same .package...it just tells the game they should all be entered into the same catalog entry. Merging them won't make them a single .package from a code perspective so that's no help either. Studio's code can be changed to allow people to open .packages that represent consolidation of multiple .packages in a future version but for now it is best to finish working on your .packages prior to merging them.
|
|
|
|
Post by lientebollemeis2i on Jan 15, 2015 15:38:54 GMT -5
So if I want to change something on a recolor I better keep the 4 parts I merged and change it in the unmerged package and then merge them again.
I'll keep that in mind and make sure that I don't edit the merged package.
Thank you!
|
|
|
|
Post by orangemittens on Jan 15, 2015 19:08:16 GMT -5
For now you are probably best off discarding the merged .package that contains a .package with material you don't want. Depending on how the items in a .package are numbered your new material may or may not overwrite the old material in the merged .package. So yes...you would want to save each .package you want to merge, make the changes to them, and then make a brand new merged .package.
It's inconvenient but we didn't predict that people would have such an interest in merging .packages like this so Studio will have to be updated before it will work more efficiently.
|
|
|
|
Post by verdigris on Apr 4, 2015 4:21:06 GMT -5
Is it possible to split previously merged packages into parts or edit the content of such packages, i.e. remove some objects from the package?
|
|
|
|
Post by orangemittens on Apr 4, 2015 17:48:55 GMT -5
At the moment the only way is to keep a backup and use that to make a new merged .package without the unwanted items in it.
|
|
