@barnacledemon, try verifying the integrity of the game cache.

Upload a troubleshooting report for the developers to review.

For issues regarding Arma 3 you can file a troubleshooting report, also via an action available in the option menu in the upper right corner (gear icon)

Be sure to upload the whole report file. You can use a free file sharing service such as Dropbox if it will not upload to the feedback tracker.

@Jawsh , I did verify the cache with no success. I will upload the report, but for posterity it is also now on my dropbox

Ah, I now see what you mean by troubleshooting report. As stated, I am on Linux. Unless I missed the rollout, the launcher is not available for Linux still. Thanks.

In T122378#1552734, @barnacledemon wrote:

Ah, I now see what you mean by troubleshooting report. As stated, I am on Linux. Unless I missed the rollout, the launcher is not available for Linux still. Thanks.

Are there any crash dumps (arma3.rpt, arma3.bidmp, and arma3.mdmp files) output by the game? For Windows they would be in %userprofile%\AppData\Local\Arma 3. I am unsure of the directory on Linux and Mac.

Workaround: go to Steam and opt Arma 3 into legacyports branch using Arma3LegacyPorts as password. This will redownload Apex expansion in suitable format.

Hi,

try to update your Arma 3 from 1.64 to actual 1.66. It might be useful.
In any case I´ve reported your issue to programmers.
You can sent us game report .rpt If you could. We have just your dumps.

Thank you

1.66 isn't available for Linux. This bug is in the Linux/Mac port.

@Alwin, sorry for the delay with the reports. I had no idea where they were saved (as they cannot be generated from the launcher, as it is not available on Linux), until I saw @Jawsh's comment. FYI, @Jawsh, there were no mdmap files, not sure if that's a Windows only file...

@pedeathtrian, I will do that, thank you.

Note: If BI's fix for this will be to simply use the legacy Tanoa map files, please be aware most mods are now also binarized as version 72 and will also not be able to be opened by the Linux binary...as well as presumably the Jets DLC.

Here's my crash report, hope that helps.
Initial state: Arma 3 is opted into legacyports branch.
Actions taken:

1. Shut down Steam
2. Clear Steam's depotcache directory. (I was suggested to do so for more purity of experiment, shouldn't hurt anyway)
3. Start Steam
4. Opt out from legacyports branch back to main branch.
5. Download required files by Steam.
6. Run Arma 3 => CTD with same error "Bad version 72 ..."

The last file seems to be .mdmp file (at least it has MDMP magic signature). In my case it was located in temp directory /tmp/arma3ADZBVa (name suffix is randomly generated each run, look for directory timestamps if you need the correct dump, or search for GUID-like dump filename from Crash Report).

Thnak you,

I will check it.

This issue appears to be resolved - on my end, I can now load version 72 .p3ds, fixing not only Tanoa but a host of mod content as well. Thank you!

Opted out of 'legacyports' branch to main.
Nothing changed on my side. Not a single file in Arma 3 directory was updated since January, 2nd.
Naturally error 'Bad version 72 in p3d file ...' still persists.

This is still happening, and is 2019.