Issue still present in V1.54
Is there any way to trace or monitor Arma 3's activity while it deals with savegame files ? I feel lonely…
- Queries
- Arma 3 Activity
- All Stories
- Search
- Advanced Search
Feed Advanced Search
Advanced Search
Advanced Search
May 10 2016
May 10 2016
BogeyJammer added a comment to T84922: Only scenario gamesaves created by the "save and exit" command is readable by a new session of Arma3.
BogeyJammer edited Steps To Reproduce on T84922: Only scenario gamesaves created by the "save and exit" command is readable by a new session of Arma3.
It does thanks.
I thought I've always activated that option…
So it's not resolved.
Thanks for your workaround. I actually used this trick a couple times. Now I just watched the location of my last know issue occurrence:
– autosave.Arma3Save: modified at 00:11, 50MB (this is the last performed autosave)
– continue.Arma3Save: (then a moment later I decided to go to bed and clicked to save and exit) modified at 00:12, but 36MB ??????????
Is this could be a clue ? I'm backing up the files in case of…
Same issue here with 1.40 version. It does not always happen but long missions with multiple auto saves are mostly affected like «Whole Lotta Altis/Stratis» «DUWS» or «Operation Cold Rising».
© Bohemia Interactive a.s. Bohemia Interactive® is a registered trademark of Bohemia Interactive a.s. All rights reserved. · Privacy Policy · Terms and Conditions