Program usage issues

[Vincent_Dolph342758546acv]

Below are PC issues: (reporting on version 5.5.5 (pc))
- Crashes happen frequently around 10-20 mins into the project and progressively gets more frequent

Input errors happens a lot, sometimes it disables everything and the only way to get **some** of the inputs back is to minimize fresco and full screen it again
- During these errors groups/folders can be unopenable in which case you need to exit out of the project entirely and go back in
- The invisible icon for hiding a layer appears very late
- Also using m2 multiple times on a layer to pull up options (cut,copy,etc) could be improved so it closes and opens based on it's current state so it doesn't require extra clicks to tinker around

These PC issues have been present for a while now (years?)
--
Below are Mobile issues: (reporting on version 6.15 (mobile))
Also I can't seem to find the ruler/ruler shapes on a phone (ipads/tablets, & pcs have the ui)
--
Also I believe there is a small freeze preventing workflow when updating the file to the cloud (automatic) can disrupt workflow

[Nick Gioia]

I believe an updated version is coming soon that should fix most of these issues. 

[Anshul_Saini]

Hey @Vincent_Dolph342758546acv,

Really sorry to hear about the issues you’re facing—sounds incredibly frustrating, especially with frequent crashes and input errors interrupting your workflow. We truly appreciate you taking the time to detail these problems, as it helps us understand what’s going wrong.

As Nick mentioned, a new update is being worked on that should address many of these concerns. In the meantime, we’d like to take a closer look at the crashes you’re experiencing. Could you upload the crash dump files from the following location to Google Drive (or a similar file-sharing service) and share the download link here?

Crash Dump Location: C:\Users\<username>\AppData\Local\Packages\Adobe.Fresco<app id>\AC\Dumps

Additionally, please generate Adobe logs, upload them to Google Drive (or a similar file-sharing service), and share the link here. It would also be helpful to note the exact time of the crash so we can correlate it with the logs.

Once we have this data, we’ll pass it on to the team for deeper investigation. We look forward to hearing back from you and appreciate your patience!

Best,

Anshul Saini

[Vincent_Dolph342758546acv]

It seems like the folder is empty and there's no crash dump files

[Anshul_Saini]

Hey @Vincent_Dolph342758546acv,

Thanks for checking! Since the crash folder is currently empty, let’s try capturing the crash data in real-time.

• Keep the crash folder open while working in Fresco.

• When a crash happens, immediately check if a crash dump file appears in the folder.

• Duplicate and move it to your desktop right away to prevent it from getting auto-deleted.

• If possible, record a screen capture of the crash while working—this will help us analyze what’s triggering the issue.

Additionally, does the crash:

• Happen with specific files or randomly across different projects?

• Seem linked to using a particular tool or performing a specific action?

Any extra details will help us investigate this further. Looking forward to your findings!

Best,

Anshul Saini

[dacreativegenius]

thank you for sharing your experience! I was writing down some notes today on my frustrating sessions with Fresco on the Surface Pro 11. 

I hear you Anshul. The last update to PC version of Fresco was last November while iPad had three updates this year already. Can we have an update soon that fixes ONE bug? 

I don't want to rehash the long list of issues I have on Snapdragon and Intel versions of Fresco but how many crash logs do you need to collect. I feel like we are the beta testers on this mature app that works smoothly on iPad. 

Today I uninstalled and reinstalled Fresco to see if maybe it was the Surface. 

I will be back when I have some data. 

[Anshul_Saini]

Hi @dacreativegenius, thank you so much for continuing to share your experience. We truly value your insights and feedback.

You’re absolutely right, the iPad version of Fresco has seen more frequent updates recently, and we completely understand the frustration when the Windows version doesn’t receive fixes as quickly, especially on newer chipsets like Snapdragon.

While it may feel repetitive, it’s important to note that not all crashes are caused by the same underlying issue. Each crash log and scenario you (and others) provide helps the product team identify patterns and prioritize fixes. Our role here is to gather and relay as much detail as possible so that when the next Windows update rolls out, it can include the most meaningful and effective fixes.

We know it’s not ideal, and we really appreciate your patience and your willingness to stick with us. When you’re ready to share your next set of findings, we’ll be here to help escalate them.

Best,

Anshul Saini