I’m experimenting with using Slint for a game development project. One of Rust’s biggest weaknesses in game dev right now is UI capabilities. Naturally, most games need the present mode to be configurable: some users want VSync for smoother visuals, others want the lowest possible input latency.

Slint is a complex project, so I’m not entirely sure if there would be any issues with letting the user configure the present mode freely.

There are two main cases to consider:

• Letting the user set a preferred present mode at rendering setup. This should be straightforward and shouldn’t cause problems.
• Letting the user change the preferred present mode at any time during runtime. This is less clear, would this introduce any technical issues or limitations?

It’s also worth distinguishing between setting a preferred present mode and forcing a specific one. One possible approach: allow specifying a preferred mode at setup, then provide a way to query the supported present modes later and let the user explicitly choose one at runtime if needed.

I haven't found any issue on this subject, only "V-Sync broken with renderer-femtovg-wgpu #8693" where tronical says

"You may have to tweak this inside the surface config setup inside the femtovg renderer. But if it helps, then perhaps we can make it configurable."