- Home /
Mac persistentDataPath differs when running through Steam
We're using Steamworks.NET to integrate with Steam, and while we eventually want to be saving steam games to the cloud, we are not yet - we're saving them to the persistentDataPath.
But what's super weird is that on all other standalone platforms, the persistentDataPath seems to point to a normal place. On Mac, it points to ~/Library/Application Support/MyCompany/MyGame/ as one would expect. Yet when running that build via Steam, it instead points to ~/Library/Application Support/unity.MyCompany.MyGame/
Does anyone know what would be changing this formatting? Is it something in Steamworks.NET that I'm not seeing? Is it something steam itself is doing when we upload the game? Something else entirely? I'm pretty much out of ideas as to where that would be coming from...
Thanks in advance for any thoughts and possibilities!
Did you ever find a reason as to this discrepancy? I noticed the same thing today when implementing S$$anonymous$$m Cloud (Auto-Cloud) via S$$anonymous$$mworks.NET as well. Running Unity 5.4.1 & OSX 10.11.6.
Ended up supplying the "$$anonymous$$yCompany/$$anonymous$$yGame" path in the S$$anonymous$$mworks ad$$anonymous$$ and that worked so far.
$$anonymous$$ade a thread over on S$$anonymous$$mworks here.
Answer by Michael-Thomas · Nov 15, 2016 at 03:00 AM
I never did get any real answer on this. We're working around this by doing a string replace on the path to ensure it's consistent and lose the "unity.MyCompany.MyGame" version. This works fine, but it's annoying to have to maintain that extra check and replace code.
Ah okay, I assume it was most likely a Unity change somewhere between 4.6 and 5.4 but I couldn't find a smoking gun in any patch notes.
Our game is definitely pulling data from the $$anonymous$$yCompany/$$anonymous$$yGame path, so that sounds like the right choice going forward.