The situation could be better, but I believe it's the best I can do with the time I have to work on this project.

This type of software is very difficult to test because it gives people infinite possibilities to break it. There's always some edge case I didn't think about outside of what I perceive to be common use cases. The hardest problem with PAC is to balance new features, performance improvements and code maintainability improvements without breaking someone's outfit. One strategy that's working alright has to been to introduce new parts instead of breaking existing ones. For example the new bone part has fixed a lot of issues that the old one had, but I cannot make it backward compatible because of how it works. So when you load an old outfit it would choose the old parts which ideally should work they way they've been working, but new outfits would use the new parts.

I have the unstable versions on github which I believe many people are using according to the discord server and other sources. This latest update has been tested for almost a year, but there's always going to be new bugs when you release it to a wider audience. I could let the workshop version stay as is for a few more years but I don't think that's going to change anything unless I actively encourage people to test the unstable version. It just postpones the eventual bugs until I push it to the widest audience.

Some people are highly emotional, and I have to do my best to see what the actual problem is behind a wall of emotional text. Usually we tend to think everything is broken when more than 2-3 things are broken. The only thing I can and should do is to remain calm and try to figure out what exactly is broken.

I'm actively adding people who I think might be onto something and trying to ask for reproducible results if it's difficult to reach them (like here on this comment section). Some people also contact me on discord or steam about issues too which is fine.

I've set aside a lot of time for this update because I knew things would most likely be broken. I will not revert the update, because as I said I'll just be postponing the problem until I push it out again.

I'm glad you talked to us about it, to be honest I don't know why pac is still getting updates because I thought that it was perfect the way it was before but at the same time this also put some things about the addon into perspective. I've been using pac for at least 3-4 years now and I can start to see where you are coming from now. From what I've experienced with the recent bugs, pac is creating script error when loading some or all textures. I hope that at least helps to narrow things down. I might also check out the unstable version if it helps things progress forward.

Originally posted by Aidan Barrett:

pac is creating script error when loading some or all textures.

Which parts are you using and which textures?

They're using the legacy materials. Okay so I took a look and I figured out what was wrong. The way pac worked before, you were able to overlap textures but if you assigned certain textures to certain parts of the model again then it would work but now it doesn't do that. I have had models with some or a lot of overlapping textures that did work at the time but don't anymore. That's a good thing though because now it means that pac works better than it did before. I know that was a weird way of explaining it. But it should be fixed now.

The march 3rd update broke all of my outfits. every attached model no longer has edits such as bone adjustments, sub materials or clips. Can you please fix or reverse this update?

Update: I also cant edit bones or materials on new models I add to outfits. Ive spent a lot of time making outfits in this game and I hope you can fix this. I dont want all of the things I made to be gone

or is there at least an option to convert new parts into legacy parts. the legacy parts still seem to work and I notice a feature that converts legacy parts into new ones. If I could just get a way to do the opposite I could make temporary fixes

lastly the face poser is now all ♥♥♥♥♥♥ up

I fixed bones now, I messed something up while fixing something else.

What is it about the faceposer that doesn't work for you?

Thanks. For some reason certain things on faceposer will be stretched a lot further than they were before but seem to go back to normal when you hover the cursor over the tab on the left. for example jaws will be opened further but tbh I could just re adjust the face poses I already have. Seriously though thanks so much for fixing the bone thing. Sorry if I sounded demanding

I made a mistake when doing something with how flexes are reset. It could cause an error, but it's fixed now.

I'm having issues with models with jiggle bones, loading them up, they are going to the orgin of my player instead of the bone i set them to, and models that are children of bones of the jiggle are not being put in the right spot if you have edited the bones.

all my models turned into bases for no reason

I've noticed where I've previously used two separate events for a sort of "AND" operation, they are no longer working properly. Is this intentional and if so, is there a better way of reading true/false from two different commands for an AND operator?

Originally posted by blazer:

I've noticed where I've previously used two separate events for a sort of "AND" operation, they are no longer working properly. Is this intentional and if so, is there a better way of reading true/false from two different commands for an AND operator?

please send an example and I will fix it. It's not intentional.