Locked How to fix issues loading in

[Milo 917]

How to fix a corrupt PBO

Method 1:

Utilizing the Olympus Mission Updater the program will automatically replace your corrupt PBO with a new and repaired version of the Olympus mission file. It is worthwhile noting that the Olympus Mission Updater is created by Olympus developers, open source and has actually been publicly signed by Microsoft as a verified application.

If this does not work and you get an error like this it is likely that you need to close your Arma, then re-try.

Method 2:

If the Olympus Mission Updater did not work another alternative can be deleting the corrupt PBO so your game will attempt to download a new non-corrupted mission file next time you join the server. To accomplish this you may follow the following steps:

1. Connect to Olympus and try to load in using a unit slot.
2. Disconnect from Olympus and close Arma 3.
3. In File Explorer in your top bar enter %LocalAppData%\Arma 3\MPMissionsCache
   1. Within that folder sort by "Date Modified".
   2. Verify that the file at the top is the most recent and not the oldest.
   3. Delete the most recent PBO file.

If you are not certain that you actually deleted the problematic mission file or it is still not working, it is safe to delete all PBO files within that folder and that will resolve the issue as well. Deleting PBO files will not delete any saved data on any server like preferences or keybinds. It simply just means any server you previously connected to you will need to redownload it's mission file like it was the first time. Which you will only need to do one time.

How do I know if I have a corrupt PBO?

These symptoms include:

Not being able to load in and receiving errors that have paths with __cur_mp.altis

Loading in and spawning out in the water and/or the map being Stratis with no map markers

Nothing worked

Although we believe certain loading issues could be Olympus specific- this has also been reported as an Arma inherent bug as a result of spotrep-00115. Players suffering from the Arma inherent issue will experience these symptoms across other servers; specifically servers where there have been mission file updates or where players have never downloaded a copy of their mission before. There currently is no known solution to this issue but it is a bug that Bohemia is aware of and is trying to address.