Copy link to clipboard
Copied
I'm suddenly getting a continuous string of 408 errors today.
Also, I've also gotten a ton of violation of TOS everythough it's a blank generation, usually on a background. Very odd.
Hi all, can you all confirm that you have the latest Ps beta: Adobe Photoshop Version: 25.0.0 20230727.m.2257 47ac892 x64
Copy link to clipboard
Copied
Can attest to the string of 408's on nothing but a blank generative fill.
Copy link to clipboard
Copied
Happened to me as well anyone figured out a fix yet?
Copy link to clipboard
Copied
can only guess Adobe are working on it
Copy link to clipboard
Copied
Hi all, can you all confirm that you have the latest Ps beta: Adobe Photoshop Version: 25.0.0 20230727.m.2257 47ac892 x64
Copy link to clipboard
Copied
Tthe first version of PSBeta worked, then updated to the latest version for access to generative expand. When I uploaded the newest version it says 100% uploaded and a popup asks to INSTALL while a working wheel spins saying "uploading erase tools". It just never finishes. So I hit install and PSBeta opens. But when trying to use fill or expand features they do not work and an orange warning box comes up "WARNING 408". Does anyone know what WARNING 408 is? I have uninstalled Ps Beta and reinstalled it to try to fix but no luck. Any ideas? THANKS
Copy link to clipboard
Copied
Same issue. Yesterday generative expand was working fine. Today I get the 408 warning. I'm hoping it's something that will sort itself out soon.
Copy link to clipboard
Copied
Can confirm.
Copy link to clipboard
Copied
Hello there,
I have updated to the latest version of Photoshop Beta (25.0) earlier this week to my MacBook Pro (OS Version 12.3.1). Since then, everytime I attempt to use the generative fill comand, or the new generative expand command, I receive the message "Something went wrong. Please try again [408]". Generative fill worked without issues prior to this latest update. Any assistance would be much appreciated!
Kind regards,
Natacha
Copy link to clipboard
Copied
The same problem.
Copy link to clipboard
Copied
I am experiencing the same error as well... 😞
Copy link to clipboard
Copied
here too...
Copy link to clipboard
Copied
I am having the same issue. I'm on Windows.
Copy link to clipboard
Copied
I was working with generative fill today. I suddenly hit a 408 error, so I restarted and the program did an update. It announced the generative expansion, however, generative fill is now completely offline. Any type of generation is returning with a 408 error (at the very end of the generation time).
Also, I've been getting a lot of TOS warnings on empty generative fill prompts, many of which have just been filling in background imagery. Definitely nothing objectionable being expanded and no prompt is being given.
It's interesting because I've been using a lot of other AI text to image and text to video programs and although yours often does a decent job now on empty prompt generations, it's really having a terrible time following prompts. I've tried a number of formats and it often just ignores the prompt given, especially colors for some reason.
Just a bug FYI. Hopefully this will be fixed soon. Thanks 🙂
Copy link to clipboard
Copied
I'm having the same issue. Frustrating.
Copy link to clipboard
Copied
I'm having the same problem, I started getting this problem today. Version 25
Copy link to clipboard
Copied
Confirmed.
Adobe Photoshop Version: 25.0.0 20230727.m.2257 47ac892 x64
Number of Launches: 44
Operating System: Windows 11 64-bit
Version: 11 or greater 10.0.22621.1992
System architecture: Intel CPU Family:6, Model:14, Stepping:13 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, AVX2, HyperThreading
Physical processor count: 8
Logical processor count: 16
Processor speed: 3600 MHz
Built-in memory: 32712 MB
Free memory: 20969 MB
Memory available to Photoshop: 25146 MB
Memory used by Photoshop: 70 %
Crash Handler: Adobe
DCX Version: 7.1.5
SAM SDK Version: 4.1.4
ACP.local Status:
- SDK Version: 3.2.0.1
- Core Sync Status: Reachable and compatible
- Core Sync Running: 6.5.3.1
- Min Core Sync Required: 4.3.66.28
Live Edit Client SDK Version: 4.0.0
Content Credential Helper Version: Not Available
D3D12Warp renderer: Disabled.
Manta Canvas: Enabled.
Alias Layers: Disabled.
Highbeam: Enabled.
Image tile size: 1024K
Image cache levels: 4
Font Preview: Medium
HarfBuzz Version: 4.3.0
TextEngine: Unified Text Engine
======= GPU
Native API stable: True
OpenGL API stable: True
OpenCL API stable: True
GPUDeny: 0
GPUForce: 0
useGPU: 1
useOpenCL: 1
isGPUCapable: 1
GPUName: NVIDIA GeForce RTX 2080
GPUVendor: NVIDIA
IsNativeGPUCapable: 1
IsOpenGLGPUCapable: 1
IsOpenCLGPUCapable: 1
HasSufficientRAM: 1
GPU accessible RAM: 8,002 MB
Required GPU accessible RAM: 1,500 MB
UseGraphicsProcessorChecked: 1
UseOpenCLChecked: 1
Windows remote desktop: 0
Windows available feature level: 12.2
Windows required feature level: 12.0
Windows has required feature level: 1
Display: 1
Display Bounds: top=0, left=0, bottom=1080, right=1920
Display: 2
Display Bounds: top=0, left=1920, bottom=1080, right=3840
Copy link to clipboard
Copied
Generative fill was working more than awesome for a lot of projects, and then all of a sudden started giving an "something went wrong (408)" message and won't work for anything.
Copy link to clipboard
Copied
here too, something went wrong error 408
Copy link to clipboard
Copied
same here too something went wrong error 408, latest version 25.0.0
Copy link to clipboard
Copied
Continuous 408 errors on the simplest of Generative Fill commands, as well as on empty generative fill command.
Multiple TOS alerts as well when there's any amount of skin near the fill area.
Everything worked fine until update. Now it's completely unusable.
Copy link to clipboard
Copied
Also having this issue. Furthermore, results are no where near as good as what they was previously. Hope this gets fixed soon!
Copy link to clipboard
Copied
Yes Cory, on 25.0 for the past 3 days, no issues until today.
Copy link to clipboard
Copied
Continuous 408 errors on the simplest of Generative Fill commands, as well as on empty generative fill command.
Multiple TOS alerts as well when there's any amount of skin near the fill area.
Everything worked fine until update. Now it's completely unusable.
Copy link to clipboard
Copied
I have been on to Support, the best solution while Adobe engineers work on it is to go through CC to Beta Apps remove 25.0 and install v. 24.7... it's working fine for me as of 5mins ago. Hope this helps