Plugins + Scripts Appearance Loader

[ForumCitizen#253]

I found the cause and took measures. If you would like, please help me confirm that it works. I was unable to attach the var file, so I named it ky1001.AppearanceLoader.26.var.assetbundle. Please change the name to ky1001.AppearanceLoader.26.var.

I had just worked out it was something to do with the added person atom to a existing scene and came here to post my findings and looks like you beat me to it lol. I tried your update and it resolved the issue I was having THANK YOU!

Also I just want to add additional praise for improving the load time on CUA's a couple updates back and the removing of CUA's on a apperance change. Those 2 were such quality of life leaps I simply had to mention it so thank you so much for putting those in!

 

[ky1001]

I had just worked out it was something to do with the added person atom to a existing scene and came here to post my findings and looks like you beat me to it lol. I tried your update and it resolved the issue I was having THANK YOU!

Also I just want to add additional praise for improving the load time on CUA's a couple updates back and the removing of CUA's on a apperance change. Those 2 were such quality of life leaps I simply had to mention it so thank you so much for putting those in!

Thank you for checking that it works. Also, thank you for liking this plugin. I have some ideas for adding new features, so I'm going to release it to the Hub with those features. At that time, the var number will probably be the same, so please delete this file.

 

[ForumCitizen#253]

Thank you for checking that it works. Also, thank you for liking this plugin. I have some ideas for adding new features, so I'm going to release it to the Hub with those features. At that time, the var number will probably be the same, so please delete this file.

File has been deleted . looking forward to the next release as always

 

[ky1001]

File has been deleted . looking forward to the next release as always

Sorry, I think I wrote it poorly. There was no need to delete it now. You should have deleted it when you got the next version I released to the Hub. Until then, please use the version I posted here.
I'm using Google Translate, so my intentions may not be conveyed correctly. Sorry.

 

[ky1001]

ky1001 updated Appearance Loader with a new update entry:

Update (ver.26)

Update (ver.26):
1) You can now individually choose whether to delete or keep Custom Unity Assets (CUAs) linked to Persons in the current scene. To use this function, turn on the "Use Extra Menu" toggle. CUAs that are not checked in the Extra Menu will be deleted. Check the CUAs you want to load or keep.
2) The "Clear Old Custom Unity Asset" function is now enabled not only when loading an appearance from a Scene, but also when loading an appearance from a Preset. Accordingly, the default...

Read the rest of this update entry...

 

[ve1cm]

Hi OP. I think I might have discovered another issue when using appearance loader. When loading a new appearance from existing scenes, its lacrimals and sclera settings are lost. Not a major issue but a fix would be appreciated!

 

[ky1001]

Hi OP. I think I might have discovered another issue when using appearance loader. When loading a new appearance from existing scenes, its lacrimals and sclera settings are lost. Not a major issue but a fix would be appreciated!

I can't reproduce the issue, if you're having trouble loading from an appearance in a specific scene please provide that scene.

 

[ve1cm]

I can't reproduce the issue, if you're having trouble loading from an appearance in a specific scene please provide that scene.

It's a paid scene not found on hub. Maybe I forgot to include a detail which is that it was not loading a texture file. It was a NULL value that was set in lacrimals texture tabs. Let me know if you can reproduce the issue with NULL values.

 

[ky1001]

It's a paid scene not found on hub. Maybe I forgot to include a detail which is that it was not loading a texture file. It was a NULL value that was set in lacrimals texture tabs. Let me know if you can reproduce the issue with NULL values.

I thought NULL was the same as clear. Thank you for letting me know. I have created a test version with the corrective measures. If you don't mind, could you please check that it works?
https://mega.nz/file/mQ9gFRQI#ab3NZxQzELcBKezW2-5k_LnEssTwmQG9GTCDU7Nsl38

 

[ve1cm]

I thought NULL was the same as clear. Thank you for letting me know. I have created a test version with the corrective measures. If you don't mind, could you please check that it works?
https://mega.nz/file/mQ9gFRQI#ab3NZxQzELcBKezW2-5k_LnEssTwmQG9GTCDU7Nsl38

Looks good now. Thank you!

Honestly in my opinion your plugin would be perfection if either or both of the following enhancements are implemented:
1. When attaching custom utility assets to the atom, everything is done in the background so editing windows are not switched (although I'm not sure about its technical difficulty of course)
2. When loading the appearance of an existing atom appearance for the second time. Atom components that remain unchanged are not loaded again (even if they are selected in the setting) to speed up the process. This is especially useful when the loaded appearance is partially messed up for whatever reasons (e.g. due to user mistakes or other plugins). It's easily fixed by reloading the appearance, but a complete reload takes a lot longer.

Just my two cents. Great work as always!

 

[ky1001]

Looks good now. Thank you!

Honestly in my opinion your plugin would be perfection if either or both of the following enhancements are implemented:
1. When attaching custom utility assets to the atom, everything is done in the background so editing windows are not switched (although I'm not sure about its technical difficulty of course)
2. When loading the appearance of an existing atom appearance for the second time. Atom components that remain unchanged are not loaded again (even if they are selected in the setting) to speed up the process. This is especially useful when the loaded appearance is partially messed up for whatever reasons (e.g. due to user mistakes or other plugins). It's easily fixed by reloading the appearance, but a complete reload takes a lot longer.

Just my two cents. Great work as always!

Thank you for checking that it works.
And thank you for your suggestion. However, I can't think of a way to achieve either of them. Sorry.

 

[ky1001]

ky1001 updated Appearance Loader with a new update entry:

Bug fix

Update (ver.27):
The textures for eye-related items such as Sclera and Eyelash were not handled properly, so I fixed them. Thanks to @ve1cm for pointing this out.

Read the rest of this update entry...

 

[ky1001]

Looks good now. Thank you!

Honestly in my opinion your plugin would be perfection if either or both of the following enhancements are implemented:
1. When attaching custom utility assets to the atom, everything is done in the background so editing windows are not switched (although I'm not sure about its technical difficulty of course)
2. When loading the appearance of an existing atom appearance for the second time. Atom components that remain unchanged are not loaded again (even if they are selected in the setting) to speed up the process. This is especially useful when the loaded appearance is partially messed up for whatever reasons (e.g. due to user mistakes or other plugins). It's easily fixed by reloading the appearance, but a complete reload takes a lot longer.

Just my two cents. Great work as always!

I have considered how to prevent the switch from Plugin UI to CUA UI when adding Custom Unity Asetts.
https://mega.nz/file/HNswzBoD#nP60hpRuNmhmY4deK0Vp_tYm_wo9NPBmFaNBKNI505c
In fact, it switches to CUA UI for a moment, but it seems that it is not noticeable to the human eye. However, message windows while CUA is being created are displayed. Please try it. If you use this file, do not load other AppearanceLoaders.
Since the HUB update has already been applied for, this change will be applied at the next opportunity. Thank you for your understanding.

 

[ve1cm]

I have considered how to prevent the switch from Plugin UI to CUA UI when adding Custom Unity Asetts.
https://mega.nz/file/HNswzBoD#nP60hpRuNmhmY4deK0Vp_tYm_wo9NPBmFaNBKNI505c
In fact, it switches to CUA UI for a moment, but it seems that it is not noticeable to the human eye. However, message windows while CUA is being created are displayed. Please try it. If you use this file, do not load other AppearanceLoaders.
Since the HUB update has already been applied for, this change will be applied at the next opportunity. Thank you for your understanding.

I didn't see anything popping up. This new version is exactly what I was talking about, and you nailed it within a day!

You are doing god's work, thanks again! I knew I should leave those suggestions there

 

[ve1cm]

Hi OP. I think this parameter is not updated when changing to an appearance. Not sure if it's an intended behavior.

Steps to reproduce:
1. load the default look
2. change its iris color to "Color X"
3. load an appearance
4. now this appearance's iris will also have "Color X"

Thanks.

 

[ky1001]

View attachment 489798

Hi OP. I think this parameter is not updated when changing to an appearance. Not sure if it's an intended behavior.

Steps to reproduce:
1. load the default look
2. change its iris color to "Color X"
3. load an appearance
4. now this appearance's iris will also have "Color X"

Thanks.

Sorry for the inconvenience.
The iris selection is meant to be applied. I checked and the iris selection was applied normally. Is this issue occurring repeatedly? Also, does the iris remain the same no matter which appearance preset you use? If this issue only occurs with a specific appearance preset, please provide the preset. I think it's possible that the irises data isn't saved in the appearance preset.
I found that the AppearanceLoader doesn't initialize the selection of irises, eyelashes, and sclera. However, if the data for irises, etc. is in the preset, the selection will be overwritten, so I don't think this is related to the current issue.

 

[ky1001]

View attachment 489798

Hi OP. I think this parameter is not updated when changing to an appearance. Not sure if it's an intended behavior.

Steps to reproduce:
1. load the default look
2. change its iris color to "Color X"
3. load an appearance
4. now this appearance's iris will also have "Color X"

Thanks.

I was thinking about the conditions under which there is no irises data in the preset, and I remembered that legacy Looks do not save default value items. Is the preset you used a legacy Look (file extension json)? If so, initializing the irises selection may solve the problem.
Initialization added version: https://mega.nz/file/zA93xCTb#neaRumIhSl8V2DinOAPc7rl8HD3U_IqNNQk7gEVvxuk

 

[ve1cm]

I was thinking about the conditions under which there is no irises data in the preset, and I remembered that legacy Looks do not save default value items. Is the preset you used a legacy Look (file extension json)? If so, initializing the irises selection may solve the problem.
Initialization added version: https://mega.nz/file/zA93xCTb#neaRumIhSl8V2DinOAPc7rl8HD3U_IqNNQk7gEVvxuk

This version did the trick, thank you!

No, all I used this entire time is "load appearance from scene", and that scene was probably from 2 years ago, so there is that.

Great job guessing the root cause. This behavior might also exist in other parts of a look, but all I have observed from my case is the iris of a character

 

[ky1001]

This version did the trick, thank you!

No, all I used this entire time is "load appearance from scene", and that scene was probably from 2 years ago, so there is that.

Great job guessing the root cause. This behavior might also exist in other parts of a look, but all I have observed from my case is the iris of a character

I heard that there was a problem with loading appearances from scenes, and I understand the cause. Scenes have the same structure as legacy looks, and the default value data is not saved. I apologize for the inconvenience. I will upload an updated version to the Hub as soon as possible.

 

[ky1001]

ky1001 updated Appearance Loader with a new update entry:

Update (ver.28)

Update (ver.28):
1) I found that the values of Irises, Eyelashes, and Sclera for Scene Appearance and Legacy Look were not applied correctly when they were set to the default values, so I fixed the issue.
2) I have almost completely eliminated the time when the CUA UI appears when loading a Custom Unity Asset.

Read the rest of this update entry...