lilxyzw / lilToon

Feature-rich shaders for avatars
MIT License
916 stars 93 forks source link

lilToon Overflows System RAM on startup #95

Open Slushe opened 1 year ago

Slushe commented 1 year ago

Importing lilToon OR having lilToon in project causes Unity to use 100% of my systems RAM until project finishes loading. Loading takes 40 to 50 minutes on average to open WITH lilToon. WITHOUT lilToon it takes 3 to 4 minutes. This causes my PC to lock up or run really slow. This happens every time I start Unity.

Project Size: 55GB System RAM: 16GB

tschaerni commented 1 year ago

Got the same Problem while importing the 1.4.0 version. 2023-05-27 06_45_26-Window Something seems to be royally fucked, if it tries to allocate 18.446 Petabytes

Slushe commented 12 months ago

Still a problem in 1.4.1

tschaerni commented 12 months ago

Still a problem in 1.4.1

I just recently installed 1.4.1 in the same project, and it works. I don't know what the cause was. But I suppose something random like that is quite hard to debug.

Slushe commented 12 months ago

The only way I been able to reproduce it is by having a large project. 5-10 Booth Avatars + 10 or so outfits for each in a single project makes lilToon load every file into ram on startup or import of lilToon. I remove lilToon and it loads up just fine. I have had to resort to just forcing my projects to be small by deleting the outfit files after I finish uploading to VRChat servers which gets pretty exhausting.

tschaerni commented 12 months ago

Weird, the project were I had issues is about 18GB big, with several Avatars in it, all of them having a lot of outfits.

Slushe commented 11 months ago

steamwebhelper_2023-10-21_11-32-42

Slushe commented 9 months ago

Unity 2022.3.6f1 LilToon 1.5.0

Still puts my 120gb Unity project into ram on startup. Happens every time I start Unity even if I let it finish the first time.

Unity_2023-12-10_09-07-25

MozillaFoxy commented 9 months ago

Unity 2019.4.31f1 Liltoon 1.5.0 Project Size: 78 GB Same happens to me image3 image (2)

DarkZeyan commented 8 months ago

Same here, since 1.4.0 I've been trying to opening my project but it crashes everytime lilToon starts to run the migrateMaterials process

DarkZeyan commented 8 months ago

image Well, by modifying this boolean to false it should fix for now the memory overflow

lilxyzw commented 8 months ago

My 21.3GB project doesn't have this problem, does this problem still exist?

DarkZeyan commented 8 months ago

My 21.3GB project doesn't have this problem, does this problem still exist?

Yes, this problem still exists but apparently it is not directly related to the size of the project itself, I could say it is more related to the number of materials the project has and the size of the texture of those materials.

I have this problem in my 64.5 GB project and disabling Migrate on Startup has been a temporal solution for me since I modified the bool