Hi @Chiara, thanks for posting in the Lucid Community! Could you try using this feature in a private or incognito window to help me narrow down the potential cause? Could you also try connecting to a different network or disconnecting from your VPN (if applicable)? Sometimes account performance issues can be related to internet security/speed or browser issues. These steps will help me eliminate that possibility. For help with opening an incognito window, please see this community post (in English). If the issue persists, please let me know!

Hi @Amelia W, let me expand this situation a little bit.
I'm starting to use Lucidspark to replace jamboard (actually dismissed) for one-to-one lessons with my students, I'm using it as a collaborative whiteboard where I and a student can write simultaneously.
The problem occurs with frequency while using a pen to the point that my students are losing patience to it: while writing, the stroke of the pen get suddenly stopped, the application start saving the board then the pen get working again only when the saving is ended. This way losing all the strokes that are inputted in between.
I've already tried, incognito mode on Chrome, changed network (from home lan to mobile connection), different browsers (Edge\Firefox), different PCs and tablet, different location (all my students experience the same issue in very different setups). It looks that the "autosave" limit the usage of lucidspark for this kind of users since it's designed for different scenarios than whiteboarding...
Pictures are attached as reference, thanks in advance for your help.

Hi @Chiara, thanks for sharing that additional context! Lucidspark’s autosave feature should not interrupt your Pen Tool usage, rather it should autosave after you release your cursor. One thing to try is toggling off WebGL, which can be done by selecting View > Rendering > Use WebGL and un-selecting this option. For help with disabling WebGL, please see this Community post (in English). Please let me know if you do not see improved performance after turning this off.

Hi @Amelia W , I tried deactivating the suggested option, but unfortunately the problem has increased, the pen freezes even more often.

I did tests with different devices (laptop, desktop PC, tablet) and different connections, but I always encountered the problem.

Hi @Chiara, thank you for following up! I apologize for the continued trouble here. That is interesting, as I do not experience the same behavior with the Pen tool, so I’m not sure what would be causing this issue for you and your students. Would you mind sharing a screen recording of you using the pen tool with your Javascript Console window open? You can open your Javascript Console by pressing Ctrl+Shift+J (if your computer is a Windows/Linux) OR Cmd+Opt+J (if your computer is a Mac).

Sorry for the delay, I recorded the video you asked. 

This video was recorded with the WebGL option enabled, which is slightly worse than the disabled option where the issue still happen but a lower occurrence.

I hope we can find a solution, thank you for your support.

Hi @Chiara, thank you for providing that video! I’m doing some additional investigating with our development team to determine the cause of this issue, so I appreciate your patience! To confirm, are you and your students using a mouse and/or trackpad with your devices? Are you using any other tools or devices to draw using the pen tool?

Hi @Amelia W , I’m actually using a Wacom One interactive display, but the same issue occur when I am using the mouse (and now I can confirm trackpad also). Let me point out that this also happen to my students which make use of tablets or PCs with mouses: it looks to me like it’s an issue platform\configuration indipendent...

Hi @Chiara, thank you for adding that information. Wacom tablets are not specifically optimized/supported in Lucid. While Lucidspark  should work with any touch screen computer or Wacom tablet you might attach to it, there are some limits to functionality on these devices.

However, this behavior is odd, and like you mentioned, is happening with students that use a mouse and/or a trackpad. I will update this thread with new information as I receive it from our development team.