Riccardo Giovanetti

I did another round of tests to check if the issue might be caused by an anti malware, antivirus or the firewall, disconnecting first from the Internet, then deactivating one...

In case it helps, I first started the v2.3.0 backend (default option 2), then I executed the developmental version of InvokeAI from the C:\InvokeAI_test\InvokeAI\invokeai\frontend folder with the command `yarn dev`...

Apparently, yes.

Unfortunately, this error is still happening in the latest v2.3.1 even before running any generation process:  It doesn't happen with the latest developmental version (SHA-1: e700da23d82d822cc3d39fa09cf246387f3d9d7f)

OK, here is my fist test on your "Idea 1". Since I was pointing the output directory somewhere else, I simply restored the usage of the standard output directory (C:\invokeai_23\outputs)...

Don't worry, Nikos, I hope the fix still works with the current 2.93 LTS version of Blender. Haven't checked it yet. Kind regards.

Testing the Model Manager in the Development Branch I noticed a couple of things that I don't know if they are by design or bugs. 1) Click on the Model...

@blessedcoolant Thank you for your reply. I was using your development branch to start the backend, as we've done yesterday, not this PR which I don't know how to implement,...

Yes, I always pressed the Update Model button, and apparently nothing happens and there are no messages in the backend or webserver consoles. Here is a screenshot after trying to...

Hello. I wish to let you know that I downloaded the [Update-2.2.5.zip](https://github.com/invoke-ai/InvokeAI/files/10300797/Update-2.2.5.zip) file from the Pre-release page of the 2.2.5-rc1 and ran it apparently without getting any error message, really...