After replacing the smart layer, various problems may occur. Without replacement, exporting PNG directly is not a problem
Main issues after replacement:
abnormal.docx (2.2 MB)
abnormal.pdf (413.4 KB)
python code.docx (10.8 KB)
python code.png (54.1 KB)
Could you please provide more details about the specific issues you are facing after replacing the smart layer? Additionally, what steps have you taken to resolve these problems?
@hellokimi56 could you please provide the input file. Unfortunately, Aspose.PSD doesn’t support 3D Effects, also, Aspose.PSD can not provide pixel-perfect rendering in comparison with Photoshop.
Replacing the intelligent layer called ‘replace’ can reproduce it
Replace_example_image.png (12.2 KB)
PSD files abnormal.zip
@Dmitriy.Sorokin We originally planned to use a deep subscription, but it seems that there are still many problems. There is a 30-40% chance that there will be problems. Can you help us solve it? Thanks!!!
@hellokimi56
The team will work on task that will not to rerender unsopported effects like 3D. Hope it will help in some cases.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): PSDNET-2382
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
Is there an estimated repair time? 1 month, 3 months, or 6 months
@hellokimi56 feature “not to rerender unsupported layers” will be released before June. Improvement of Smart Objects and its’ Effects is released every month. Support of 3D effects is not in the Roadmap for 2025.
The issues you have found earlier (filed as PSDNET-2382) have been fixed in this update. This message was posted using Bugs notification tool by yaroslav.lisovskyi
Various issues may arise after replacing the smart layer. After replacement, the image becomes blurry with jagged edges. If not replaced, exporting PNG directly will not have any problems.
@Luo.Lingfeng We’ve reviewed your new report and included it in our current improvement cycle. We’re working on gradually improving this functionality to ensure a stable and consistent result.
In a large upcoming fix is planned for version 25.11, which includes several important improvements.
We will keep you updated once it’s addressed in a public build.
What date is your update scheduled to be released in November? I would like to know the specific date as I need to update as soon as possible
@Luo.Lingfeng We don’t have an exact date yet. The release will be published when it’s ready. Please wait for the release updates.