search

invoke-ai / InvokeAI

InvokeAI is a leading creative engine for Stable Diffusion models, empowering professionals, artists, and enthusiasts to generate and create visual media using the latest AI-driven technologies. The solution offers an industry leading WebUI, supports terminal use through a CLI, and serves as the foundation for multiple commercial products.
https://invoke-ai.github.io/InvokeAI/
Apache License 2.0
22.83k stars 2.36k forks source link

[bug]: installer bat issue #2253

Closed Mremenar closed 1 year ago

Mremenar commented 1 year ago

Is there an existing issue for this?

OS

Windows

GPU

cuda

VRAM

No response

What happened?

Win10 machine. ERROR: Ignored the following versions that require a different python version: 0.55.2 Requires-Python <3.5; 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11 ERROR: Could not find a version that satisfies the requirement torch==1.12.1 (from versions: none) ERROR: No matching distribution found for torch==1.12.1 Requirements installation failed. See above for errors and check https://invoke-ai.github.io/InvokeAI/installation/INSTALL_AUTOMATED/#troubleshooting for potential solutions. The installer will exit now. Press any key to continue . . .

So I tried reinstalling 3.7.9, and then "repaired" 3.11.1. Re-runnning the install.bat, I get: Checking and Updating Python Your version of Python is too low. You need at least 3.9.0 but you have 3.7.9. We recommend Python 3.10.9 from https://www.python.org/downloads/release/python-3109/ The installer will exit now. Press any key to continue . . .

Screenshots

No response

Additional context

No response

Contact Details

marc.remenar@yahoo.com

gogurtenjoyer commented 1 year ago

InvokeAI isn't currently compatible with python 3.11 because of the pytorch version it's using (maybe other dependencies as well, I'm not sure).

Please try installing 3.10.9 from the link provided in what you've pasted above, making sure to check 'add python.exe to PATH' when doing so.

Mremenar commented 1 year ago

I did as requested, removing the latest Python and installing the 3.10.9. as requested.
After much wrangling with the Huggingface tokens, the install appears to have completed, but the actual use will not. When I run the "Unified Canvas" it will not ever complete the task. The first attempt appeared to be asking too much, as did the second. I scaled back the third attempt with a different picture. I'm attempting to extend the bottom of a picture by a third.

My Virtual Memory is 24.7 GB, My Video Card is a 16GB CUDA card, NVIDIA GeForce GTX 1660 Ti

OS Name Microsoft Windows 10 Home Version 10.0.19045 Build 19045 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name D5000 System Manufacturer Micro-Star International Co., Ltd. System Model MS-7B79 System Type x64-based PC System SKU To be filled by O.E.M. Processor AMD Ryzen 5 2600X Six-Core Processor, 3600 Mhz, 6 Core(s), 12 Logical Processor(s) BIOS Version/Date American Megatrends Inc. A.70, 1/23/2019 SMBIOS Version 2.8 Embedded Controller Version 255.255 BIOS Mode Legacy BaseBoard Manufacturer Micro-Star International Co., Ltd. BaseBoard Product X470 GAMING PLUS (MS-7B79) BaseBoard Version 2.0 Platform Role Desktop Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume9 Locale United States Hardware Abstraction Layer Version = "10.0.19041.2251" User Name DESTROYOBOT5000\Dad Time Zone Pacific Standard Time Installed Physical Memory (RAM) 16.0 GB Total Physical Memory 15.9 GB Available Physical Memory 7.28 GB Total Virtual Memory 24.7 GB Available Virtual Memory 3.93 GB Page File Space 8.73 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware No Hyper-V - Data Execution Protection Yes

Do you want to generate images using the

  1. command-line
  2. browser-based UI
  3. open the developer console Please enter 1, 2 or 3: 2 Starting the InvokeAI browser-based UI..

    Patchmatch initialized

    • Initializing, be patient... Initialization file C:\Users\Dad\InvokeAI\invokeai\invokeai.init found. Loading... InvokeAI runtime directory is "C:\Users\Dad\InvokeAI\invokeai" GFPGAN Initialized CodeFormer Initialized ESRGAN Initialized Using device_type cuda Current VRAM usage: 0.00G Scanning Model: stable-diffusion-1.5 Model Scanned. OK!! Loading stable-diffusion-1.5 from C:\Users\Dad\InvokeAI\invokeai\models\ldm\stable-diffusion-v1\v1-5-pruned-emaonly.ckpt | LatentDiffusion: Running in eps-prediction mode | DiffusionWrapper has 859.52 M params. | Making attention of type 'vanilla' with 512 in_channels | Working with z of shape (1, 4, 32, 32) = 4096 dimensions. | Making attention of type 'vanilla' with 512 in_channels | Using more accurate float32 precision | Loading VAE weights from: C:\Users\Dad\InvokeAI\invokeai\models\ldm\stable-diffusion-v1\vae-ft-mse-840000-ema-pruned.ckpt Model loaded in 26.34s Max VRAM used to load the model: 4.28G Current VRAM usage:4.28G Current embedding manager terms: * Setting Sampler to k_lms

Could not generate image. Usage stats: 0 image(s) generated in 54.96s Max VRAM used for this generation: 5.01G. Current VRAM utilization: 4.28G Max VRAM used since script start: 5.01G

gogurtenjoyer commented 1 year ago

Please check the hardware requirements in the documentation; unfortunately the GTX 1660 isn't recommended for InvokeAI.

Mremenar commented 1 year ago

If I understand what you're saying, it's a requirement to have a CUDA card, but you don't support one of the most popular CUDA cards manufactured? I tried resizing the original image down to 512 x 704. It's now producing results, albeit very weird results, but it is producing results.

gogurtenjoyer commented 1 year ago

There's currently either a hardware or driver bug with those cards; it has nothing to do with InvokeAI - essentially, they don't support FP16 properly, and since they have very low VRAM compared to newer cards, they run out of memory quite easily (as they have to use about twice as much with FP32). There's been talk over in the pytorch repo issues about the fault lying with cudnn, and there were supposedly updates to address it, but the results seem to be mixed. Things might work better with those cards and InvokeAI in the future, but nobody here can say for sure.

Mremenar commented 1 year ago

Is it the bug that makes the AI make the weird choices when extending a picture?
(I'm trying to use InvokeAI to build out a picture of a women generated with a different AI that caused one of her legs to be severely deformed. Clipping the deformation from the picture and running InvokeAI...well let's just say that Invoke doesn't seem to grasp human anatomy very well. I've tried nine attempts so far with all of them creating weird mangrove root distortions where the other leg should be.
If I was going for an acid-trip-hippy-picture-lost-in-Salvador-Dali-land, than all the results would be "groovy, man!" But since I'm trying for photorealism-- not really hitting the mark, if you know what I mean.

gogurtenjoyer commented 1 year ago

Nope, unrelated.

github-actions[bot] commented 1 year ago

There has been no activity in this issue for 14 days. If this issue is still being experienced, please reply with an updated confirmation that the issue is still being experienced with the latest release.