Hi, I’m interested to know if anyone has ever had a similar problem and how were you able to solve it?
The bottom line: When prototyping through a component (for example, navigation between pages), wild lags occur during the viewing mode. If you don’t connect frames to each other, then everything works fine.
P.S. The computer is good, there is almost no load on the processor / RAM, the Internet (wired/ wi-fi). It’s definitely not into this
Hi @Pavel_V, Thanks for reaching out about this.
While we wait for input from our community, I wanted to share that our engineers are currently aware of two known issues that might be causing slowness in presentation view. I’m not sure if this directly relates to your situation, but it would be great if you could check these in your file:
Sections If your prototype file is using Sections and these sections contain a large amount of content, it could contribute to the slowdown. A workaround could be to either remove sections or isolate your prototype flows to separate pages that don’t contain any sections.
Deeply Nested Instances If your prototype frames include deeply nested instances, this could be another contributing factor. To enhance performance, we recommend flattening your hierarchies as much as possible.
Additionally, large or complex component sets, especially those containing images, nested instances, or other complex elements, can also impact performance. Reducing the size of these component sets where possible might help.
I hope these suggestions help! The team is continuing to work on performance improvements and we appreciate your understanding.
If anyone in our community has additional tips or workarounds, please feel free to share here.
Thanks again for reaching out!