>>50129069I misspoke, ~3 weeks.
>Client Windows OSs start having odd behaviours after 3 days of use and it gets real bad after 7 usually.Wait until you find out that this is a copy of Windows 7 -> 8.1 -> 10 that's been through an entire architecture change - from some AMD something or another APU to a spare Ivy Bridge board and using the Intel integrated graphics, and then with an actual Radeon card joining the party. The only thing that ever acts up is OneDrive itself hanging on SOMETHING and causing anything that tries to hook into explorer.exe
like a "Save As" dialog from your browser to stall indefinitely. And that happens on a clean, fresh install of Windows anyways, kek.
>>50129153>and I don't think this pc has integrated graphics or whateverIt's not hard to figure out.
>1. Does your motherboard itself have video out ports on its I/O - away from the GPU itself? HDMI, DisplayPort, DVI if it's ancient, etc? If yes, see 2.>2. What kind of CPU do you have? Some do not have integrated GPUs.>>50129414Yeah, that's what they mean. When you use the NAI leak VAE, you
most of the time have to use --no-half-vae. That also increases memory usage during that final step that can take an image that had a perfectly good preview and make it turn black
when --no-half-vae is off - but only with the NAI VAE.Go to the FAQ in the OP. Ctrl-F VAE. Get the SD or WD VAE, or the "NaNless" or "V2.x" versions of ClearVAE - and then remove --no-half-vae from your launch flags. You'll save some VRAM. Also - certain upscalers use more VRAM than others - the ESRGAN ones will use more than latent.
Tiled VAE was a good option for reducing VRAM usage but IDK if it's been fixed, it broke a few weeks ago.
