>>43830430I'm fuckin stumped. The old way I had it set up - no patches whatsoever - both RAM checkpoint values set to 0, seems to work the best. There's still a RAM leak. It started around the time it started to print that .yml shit to the console when you start webui up. This stuff:
>Loading weights [500bd69b0e] from /content/stable-diffusion-webui/models/Stable-diffusion/SuperSauceIII_fp16.safetensors>Creating model from config: /content/stable-diffusion-webui/configs/v1-inference.yamlIDK. I looked thru the actual code that does the "load the stable diffusion model up" stuff. Above my paygrade sir. I am retarded.
>>43830430>output, drive, etc.sir, what I mean, is that by default, this thing was already set up so that you do not need to manually remap your output folders. it's transparent. I was handling it at the file system level, outside of webui completely...
>If you uncheck this box, your output will only exist on the Colab unless you save individual images or use one of the "copy/ZIP everything" options below.>Google_Drive_Output = True #@param {type:"boolean"}>blah blah blah like 200 lines of script>if Google_Drive_Output and Allow_Drive:> now=!date +%Y-%m-%d_%H-%M-%S> print(f' Your output images for this session will be in a folder named "outputs-{now}" in your Google Drive.') it's been that way. forever.
>settings, config, etc.It's going to make a folder called "vt_colab_settings" and copy "my" settings. Once it does that the first time, it will never overwrite your settings unless you go and delete them from there. It will also load settings from there by default. And it re-writes them at launch to load whatever checkpoint and VAE you download, and to map your outputs on webui's end into those same "now" folders - which will now be subfolders inside a bigger folder called "outputs" because, uh, the root of my drive is a fucking mess now and it's entirely my fault. kek
