#InvokeAI 2.3.3-rc1 installation

1 messages · Page 1 of 1 (latest)

half trench
#

Hello! I downloaded InvokeAI 2.3.3-rc1, unzipped it into my InvokeAI folder, and installed. It ended up with version 2.3.0. It actually downgraded my 3.0.0-a0 to 2.3.0, the old version. (Trust me I was running 3..0.0-a0).
Option 9 doesn't work with error :"invokeai-update.exe': [Errno 2] No such file or directory"

What should I do to set up the updated InvokeAI? Thank you!

half trench
#

I used the comand line "pip install --use-pep517 --upgrade InvokeAI==2.3.3rc1
still got 2.3.0. ......???

#

Ok. Problem solved. Do the command line in developer console.

tacit lichen
#

This is very very strange. Are you sure you unzipped InvokeAI-installer-v2.3.3-rc1.zip and not an older file?

half trench
#

Sorry. yes I am very sure I did. It wasn't the first time. Since the 2.3.0 beta or post 2 (I forgot the versions), every update downgraded my installation to 2.3.0. (by unzipping and installing the ZIP file). And then one day through the console I "accidentally" updated InvokeAI to 3.0.0-a0. Everything went great. I was able to batch rendered 50 images without CUDA error. Then yesterday my itchy fingers decided to update again. The console update didn't work anymore. So I downloaded the 2.3.3rc1. And it downgraded InvokeAI to 2.3.0 again. Until I tried the command line.

#

I ran the command line initially by opening a console in InvokeAI folder. Everything went well (took a long time). I restarted InokeAI and it was 2.3.0. Batch rendering crashed at 22nd images, as usual. Then I re-ran it within the developer's console. It went well and I ended up with 2.3.3rc1. I didn't test the batch rendering so I can't say if it would crash with CUDA error or not.