macOS: Game data corrupt immediately if moved to an exFAT partition

[i0ntempest]

Type

Crash to desktop

Bug description

If I move the game folder to a exFAT partition within the game and quit it, the game will crash and no longer open (crash on startup).

Screenshots or videos

No response

Version

2022.821.0

Logs

database.log
network.log
performance.log
runtime.log
macOS crash log
crash.log

[peppy]

This is a limitation of realm. Please avoid doing this.

We’ll need to add better messaging to avoid this happening in the first place.

[i0ntempest]

Well the size of my beatmap library doesn't allow me to put it on the system partition. It worked for a period of time before, so this limitation must be new?

[peppy]

Unless you mean a year or more ago, nothing should have changed.

Out of curiosity, is there a reason you use an ExFAT partition as opposed to APFS or HFS+?

[i0ntempest]

Can't remember the exact time but it definately worked in late 2021/early 2022.
I have a dual boot setup and afaik only exFAT allows r/w access for both macOS and Windows (officially anyways). I have thought about making lazer on both OSes use the same directory, not sure if that's a good idea so haven't tried yet.

[peppy]

Hmm... so realm has this fallback logic which should handle these cases (as discussed at realm/realm-dotnet#2751). Could something have regressed with that? Or maybe it never worked? We'll need to test this against an ExFAT drive and report back to realm.

[i0ntempest]

Just found the screenshot I took in lazer on macOS, it was taken on April 24. So the newest version at that time definately worked.

[peppy]

I can reproduce the issue, so I will report it upstream.

[peppy]

Tracking at realm/realm-core#5789.

[peppy]

This has been fixed upstream. We should be able to close out this issue after the next realm release.