Unable to start game since Apex

30 posts in this topic

I have not been able to get the game to run since the release of Apex. Quite some time back I pre-purchased Apex back when I was still running Windows on a second partition. Since then I have gone 100% Linux and I would like to play ArmA3.

Share this post

Link to post

Share on other sites

Seems like ArmA runs with expansion addon enabled. Try forcing no-mod run with -mod="" launch option. Apex is not available for Linux/Mac ports yet.

UPD.

OR, alternatively, use -world="Altis" instead of -mod="". Most likely you will have first error, but not the second; also you will probbaly get to main menu, then go to Configure -> Expansions menu end try to disable "expansion" there.

Share this post

Link to post

Share on other sites

Receive the same error as pedeathtrian here (Bad version 72 in p3d file 'a3\vegetation_f_exp\clutter\grass\c_grassbunch_hi.p3d'). Tried verifying the cache and also a total reinstall.

Edit:

Forcing no-mod run with -mod="" did nothing, but using -world="Altis" (as pedeathtrian suggested) let me open the game. Unfortunately nothing is playable and I cannot disable "Arma 3 Apex", the disable button is greyed out. Selecting "Arma 3 Apex" and hitting enter gives me the option to restart the game to apparently apply changes, but it does not disable Apex.

Share this post

Link to post

Share on other sites

In Steam I opted Arma 3 to legacyports branch (using Arma3LegacyPorts as password) -- something I never did since first installed legacy port client (though I did it for dedicated server) in September of 2015 -- had to redownload some 4.7 gigs, then everything worked like a charm.

Share on other sites

Limited User-Generated Content compatibility - custom scenarios and mods technically can work in the ports, but it is likely their authors will pursue compatibility with the primary Windows version instead.

It's not that mods authors pursue compatibility with Windows only, but more like BIS pursue compatibility of their tools with Windows version of Arma only, so that not only modders' content is incompatible with legacy ports, but even their (BIS) own content is incompatible too! Modders have little to no control of compatibility there.

Share this post

Link to post

Share on other sites

In Steam I opted Arma 3 to legacyports branch (using Arma3LegacyPorts as password) -- something I never did since first installed legacy port client (though I did it for dedicated server) in September of 2015 -- had to redownload some 4.7 gigs, then everything worked like a charm.

This worked for me too and seems to be the best workaround while we wait for a solution. Thank you pedeathrian, you're lifesaver!

Share this post

Link to post

Share on other sites

The last lines of the crash report which have some kind of google suggestions are the following:

[thread 00000004][W][53911]: eON_GetProcAddress() for module 0x400000, in PE file 'Arma3Retail_DX11.exe' FAILED. Proc not found at name '_OPENSSL_isservice'.
[thread 00000012][E][54632]: Program from shader GL_FRAGMENT_SHADER with length 43353 and CRC 0x1aa62d1e has not been successfully linked. Program info log:error: Too many fragment shader texture samplers

Edit:

Disabling the shadows makes me play the game but is not good in a military simulation.

Share this post

Link to post

Share on other sites

By the way, how do you start the Apex DLC under Linux? I bought it but Steam does not download additional files and in the games library there is no DLC section where I could check or uncheck a DLC (and no DLC tab under Properties). Do I have to select a specific Branch in order to use the Apex DLC?