|
|
Post by Merry927 on May 24, 2016 16:36:56 GMT -5
I created a new override package and some of the swatches have random thumbnails in them (e.g. a sink or knife block when the package is for a door). The clear button is not removing them. This is not happening for the regular recolor package of the same doors that I made. package |
|
|
|
Post by inabadromance on May 24, 2016 19:30:52 GMT -5
Wow that's super odd. Have to tried re doing the package?
|
|
|
|
Post by Merry927 on May 24, 2016 19:48:05 GMT -5
No, I didn't, but I did close the package and reopen it.
|
|
|
|
Post by MisterS on May 24, 2016 20:02:20 GMT -5
Have you cleared the cache and put in the game, clicked on all the swatches and re opened it in s4s ?
|
|
|
|
Post by Merry927 on May 24, 2016 20:48:58 GMT -5
Redoing the package gets the same result. Unfortunately, so does clearing the cache and putting in game.
|
|
|
|
Post by MisterS on May 24, 2016 21:17:26 GMT -5
Its odd to say the least.
Ive passed it on, seems some type of bug
|
|
|
|
Post by Feyona on May 24, 2016 21:22:23 GMT -5
Offtop MisterS Orangemittens can be tagged when you write @ admin |
|
|
|
Post by MisterS on May 24, 2016 21:23:13 GMT -5
Oh that's why it didnt work, I pm'ed her instead
|
|
|
|
Post by BrazenLotus on May 25, 2016 20:05:00 GMT -5
I've had the same issue with some plant overrides. It's been like this for a while.
|
|
|
|
Post by Bakie on May 26, 2016 2:16:24 GMT -5
The only thing I know is that this happens if the override has more thumbnails then it originally had. I had this too and could solve it by deleting the thumbnailhash line in the Object Catalog line, but looking at your package file, those lines are already all zero's..
In fact, I do have the same problem now with an overwrite I'm making myself right now..
Opening them in game did result in new thumbnails for the emty ones, but the other objects thumbs are still there just as the first 4 original ones.
|
|
|
|
Post by Merry927 on May 26, 2016 16:41:01 GMT -5
So it doesn't sound like there's a solution yet. Hopefully, this can be addressed in S4S at some point, but i think I'll just settle on releasing the recolors for now. Luckily for me, having overrides for this package is not super important. Thanks for your input everyone. I will leave the thread open since the issue still isn't solved at this point.
|
|
|
|
Post by orangemittens on May 28, 2016 10:19:45 GMT -5
Hi all, this is occurring because of how Studio renumbers when you add a swatch. In order for object swatches to show up in-game in the same order you have added them in Studio, Studio sequentially renumbers each swatch you add. If you have cloned something as an override adding swatches in sequential order will, inevitably, add a swatch that is numbered with the same number EA is using for something else. The fact that you end up with an odd looking thumbnail is just the tip of the iceburg. Because you are overwriting a swatch from another item, this other item no longer has that swatch in the game. For example, in this case, your door override swatch has replaced the knife block (or sink) swatch that is showing as a thumbnail in your .package. If someone puts this door in their game, they will no longer find that knife block swatch as an option for the knife block.
This issue highlights the care you need to take when making an override.package. We'll take a look at changing how Studio deals with the addition of swatches using the 32-bit instance numbers EA uses so that this won't be an issue when adding swatches to an override .package. In the meantime, you can fix it by manually renumbering the swatch (object definition and object catalog resources).
|
|
|
|
Post by Merry927 on May 29, 2016 14:52:00 GMT -5
This issue highlights the care you need to take when making an override.package. We'll take a look at changing how Studio deals with the addition of swatches using the 32-bit instance numbers EA uses so that this won't be an issue when adding swatches to an override .package. In the meantime, you can fix it by manually renumbering the swatch (object definition and object catalog resources). Thank you for the explanation. |
|
|
|
Post by BrazenLotus on Aug 27, 2016 19:54:00 GMT -5
This issue highlights the care you need to take when making an override.package. We'll take a look at changing how Studio deals with the addition of swatches using the 32-bit instance numbers EA uses so that this won't be an issue when adding swatches to an override .package. In the meantime, you can fix it by manually renumbering the swatch (object definition and object catalog resources). Has S4S been updated to correct this? If not, how exactly do we renumber these? Is it the key portion of the definition and catalog and do I use the hash generator? Sorry if this is a noob question  |
|
|
|
Post by Merry927 on Aug 28, 2016 11:20:05 GMT -5
|
|
