|
|
Post by kamyk2000 on Sept 9, 2016 20:55:08 GMT -5
A radial for standalone or replacement under build mode to force a standalone wall or floor or whatever. Sometimes, for me at least, it makes a default replacement for no reason I can discern. Having an option to force it to be standalone would be nice.
|
|
|
|
Post by kamyk2000 on Oct 11, 2016 2:47:04 GMT -5
A radial for standalone or replacement under build mode to force a standalone wall or floor or whatever. Sometimes, for me at least, it makes a default replacement for no reason I can discern. Having an option to force it to be standalone would be nice. When making a Wall or Floor with The Sims 4 Studio, it's already a standalone item by default. If you meant that it's replacing other walls you made, then you probably used the "save as" function on that same wallpaper or flooring. If you want to make a new wallpaper or floor, you will have to start in the main menu. What it sounds like you are doing is opening your custom wall .package, making changes to it, and then saving it as a different .package name. This will create a default override of the original .package because no new clone was made in that process. The cloning process is where instance numbers are generated. If there is no cloning process Studio cannot make new instance numbers. If you want a new wall.package you have to go to the main page and choose to make a new wall.package. The wall.package that is made will have unique instance numbers and it will not override any other wall in the game, custom or otherwise.  Actually no in both cases, although there was some of that during my learning process. More specifically what seems to be happening is if I clone a wall or floor from the main page (and not all of them mind you for some odd reason) and I don't change the catalog text, and price, etc, and the first swatch texture before saving the file after the initial clone save, it acts as a default replacement for the original cloned wall or floor. Seems doing any of those things but not doing them all causes me the issue. Like I cloned a floor from the main page menu, changed the texture for the swatch (just the one, didn't add any others), didn't change the catalog text, and saved, It replaced the original EA floor I cloned it from. Dunno if this is reproduceable or common, or just my poo luck, and like I said it only seems to happen with some of the EA walls and floors, not all of them. Fantastic to hear about reordering swatches, that will be a godsend. I got carried away and my walls and floors are up to 100 colors now, and that's just the tile ones. I've also now made panel walls and floors, and 12 different rugs ranging from fur to velvet to shag to pile to berber and they are all colored to match too so I'm looking at 1000s of swatches to reorder. And I haven't even started on wallpaper with trim yet, or themed painted walls. (I always get carried away when modding). Next step is a few custom mesh furniture sets also in the 100 matching colors. Reordering swatches will be a lifesaver. Btw, is there an appropriate sub forum on here where I can post pictures of what I'm working on so I can get feedback, suggestions (and show off, lol)? Rather than cluttering up various other posts, or putting my pictures in threads that mostly won't be seen? |
|
|
|
Post by Bakie on Oct 11, 2016 7:31:44 GMT -5
kamyk2000, Could you give an example of a floor or wall where this happened to you? (Share the last 4 digits when you hover your mouse over the thumbnail) For feedback on your creations, you can make a thread in the Creator Discussion Feedback section of this forum.
|
|
|
|
Post by kamyk2000 on Oct 11, 2016 15:10:21 GMT -5
Since they weren't what I wanted I deleted the package files that did it, but yeah I'll try and reproduce it for you. Just have to try and remember which walls and floors gave me issues, since I went through dozens looking for ones that had speculars but didn't do that. I did sort of keep a list, but it was only the name of whatever floor or wall I was trying to clone at the time so I could see if my packages ended up default replacing EAs. Once I found ones that didn't, I didn't bother keeping the list either since it only ever had one package name in it at a time. I'll try though.
|
|
|
|
Post by orangemittens on Oct 11, 2016 16:05:55 GMT -5
Hi kamyk2000, I believe you are confused about how Studio makes a build item (wall, floor, terrain paint, or roof recolor). When you select the item you wish to clone and click the Next button, Studio clones the item and, in that process, internally renumbers it. The numbers it changes are the numbers that determine whether something will overwrite an EA item or be a standalone item. Studio changes the numbers so that the item is a standalone item. When you click the save button after naming the .package you have created a standalone recolor. At no point in this process is the item a default replacement. The minute you click the Next button, Studio is generating a standalone wall. After you name it and click Save, Studio saves the standalone wall that was generated.
Nothing you do on the Studio tab after that cloning/saving process will change the internal numbering, and nothing you do on the Studio tab can change the internal numbering. Whether you change the price, the description, the catalog name, or the swatch image, the internal numbers stay the same. If you don't change any of them and you pop that .package into the game, you will end up with a new catalog entry that is exactly like the EA item you cloned except that it isn't in the same catalog entry.
Because it is the internal numbering that determines whether something is a default replacement or not, anything you do on the Studio tab is irrelevant to whether the item you make is a default replacement. The only thing that determines that is how the item is cloned and what editing goes on in the Warehouse after the item is cloned. As Studio is not yet enabled to make default replacements for Build mode recolors the situation you're describing is not possible. Either Studio is somehow, due to a bug that has never been reported before, making a default replacement during the cloning process, or you are somehow making a wall .package that is based on your own, previously cloned wall without any renumbering taking place. As I said before, while I'm perfectly willing to entertain the idea that Studio has a bug and is cloning certain walls as default replacements (or that the game handles certain walls differently than others), I find it difficult to think that this is only now coming to attention. Studio has been successfully making walls for over a year, and no one else has ever reported a problem like this. If you know of a wall like this, please indicate the name of that item so the issue can be investigated.
At the very least, I can assure you that the issue has absolutely nothing whatsoever to do with your activities on the Studio tab. All work on the Studio tab is, by default and design, incapable of changing the numbers that make something a default replacement or not.
|
|
