Yes, we were able to recreate the issue, thank you for the report. The team is working on getting a separate post-jam version out that completely fixes this issue. It should only take a small amount of time. Will definitely be done by tomorrow morning!