Hi @Mr.Flibble,
Thanks for the follow-up.
This behavior is already a known issue and is being tracked internally. Creating a new thread won’t change the timeline or priority here — once the fix is ready, it will be included in an update and explicitly called out in the release notes (Early Access first, then Stable).
At the moment:
- The fix has not yet shipped to Early Access
- There’s no additional information or diagnostics needed from users
- The only place to watch for updates on this is the release notes, not separate threads
As soon as the fix becomes available, it will be clearly introduced in the release notes.
Thanks for your patience.