Product Name/Version: AMP ADS v2.4.5.4, built 14/07/2023 19:36
Problem Description: When using automatic datastore selection, it will always use the “Default Datastore” instead of others.
Steps to reproduce:
Add second datastore, active, priority 0
Deactivate “Default Datastore”, priority 1000
Create game instance
Actions taken to resolve so far:
Have tried permutations of priorities (secondary higher and lower priority than default) and default datastore active/deactivated.
Game instances remain created on “Default Datastore” instead of secondary.
Additional notes: usage on both datastores reads as “unknown”. Datastores are located on local EXT4 partitions.
I was able to reproduce this and have addressed the issue. It was a side-effect of the way that template instances are handled. This has been rectified for the next update.
Ah, noted. I didn’t know that existed, but it certainly did the trick! I’m wondering if there’s a way to schedule that, but otherwise I’m good to go. Looking forward to the update!