Plugin not working anymore after Automatic1111 latest updates

Interpause / auto-sd-paint-ext

Extension for AUTOMATIC1111 to add custom backend API for Krita Plugin & more

MIT License

477 stars 41 forks source link

Plugin not working anymore after Automatic1111 latest updates #145

Open Shangooriginal opened 1 year ago

Shangooriginal commented 1 year ago

The plugin does not work (all tabs) anymore after updating to the latest updates from Automatic1111.

To Reproduce Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots If applicable, add screenshots to help explain your problem.

Screenshot of backend console output
Status bar message when error occured
All contents of Krita error popup (if any)

Desktop (please complete the following information):

OS: [e.g. Windows, Linux]
WebUI commit revision [looks like this: e68484500f76a33ba477d5a99340ab30451e557b; can be seen when launching webui.bat, or obtained manually by running git rev-parse HEAD]
Extension commit revision (can also be seen when launching webui.bat)

Additional context Add any other context about the problem here.

Interpause commented 1 year ago

Can you attach a screenshot of the A1111 WebUI console?

delolat commented 1 year ago

I'm on Macos and I have the same problem after getting new update.

checked out a1111 cb81b52f, but had other issues with other extensions.

Interpause commented 1 year ago

I'm on Macos and I have the same problem after getting new update.

checked out a1111 cb81b52f, but had other issues with other extensions.

Error seems unrelated to this extension. Can you check if the webUI works normally? I am not familiar with the torch MPS backend.

delolat commented 1 year ago

The webui works normally. However, I did receive this same error recently when using controlnet in the new reference only. This exact error in fact, which they were able to patch. Perhaps there's a clue to the problem in their solution.

https://github.com/Mikubill/sd-webui-controlnet/issues/1267#issuecomment-1547319680

Dartterious commented 1 year ago

I'm getting the following error after the AUTO1111 1.5.1 update.

avinashreddymudireddy commented 11 months ago

MacBook Pro m2

Miraihi commented 11 months ago

Heads up for the alternatives for this plugin: