pewe

with the 1.70 update i can finally really play the arma linux port... was stuck with lowest resolution textures before which made the game look really old... but now it's mainly working fine... thanks a lot! @fraczek: for me 4K now works, but I'm on linux not Mac, so seems like some Mac-OS specific thing... the only poblem i now have is: i played through the campaign to finally finish it and every now and then after an hour of playing or so the game just froze... not in a specific situation, but more like randomly.. cpu/gpu usage just went to zero and the application just didn't respond anymore... short look with gdb at the situation showed all threads being in nanosleep, so seems like a deadlock with some mutex/waitcondition... only happens after some while playing it... was playing solo-missions only... system is: linux-64bit, core-i7 5820K, 16GB RAM, GeForce GTX 980Ti(384.69)@3840x2160 a thing that for me is still missing is proper joystick support... i don't see any joystick appearing at all in the config... I'd love to fly helicopters (have the DLC for additional fun!)... but that requires full support for some reasonable setup (for me it's thrustmaster hotas warthog joystick + throtte and saitek pro flight rudder pedals).. warthunder and x-plane can do that perfectly for some years now, so it's definitly possible with reasonable effort... and for a simulation, especially when including flying, it is essential! another thing with input is: i tried to assign my gamepad for driving (logitech f310, works absolutely fine in other games), it shows up in the configuration, but when trying to configure anything for it, it is not possible... i'd like to use it for driving with the analog sticks it has, but they are not recognized... also the buttons seemed to be nowhere recognized or selectable (some menu items get a default assignment when a gamepad is detected, but pressing the shown buttons doesn't show any reaction from the game at all)... theoretically would like to use my logitech g25 for driving, but then again having all that stuff messing up your desk makes playing uncomfortable or you'd need like 5 minutes for changing between control-setups... that's the most pressing issues for me at the moment to have the full experience... for me that things are more important than being at the same version as windows... I'd prefer if the basics (like the mentioned input) would get more attention so the playing possibilities become the same for a specific version and not some stuff that works since version 1.0 on windows still isn't available in the ports in 1.70 or later.... just my point of view....

nope, unfortunately no difference... seems like those parameters are for the windows version only... had this issue on two linux boxes: - openSuSE tumbleweed with i7, 8GB RAM, GTX970 - mageia5 with i7, 16 GB RAM, GTX980Ti funny thing: bioshock inifinite also uses eon and there it has no problem using the full vram on the linux box when looking at the logs in eon.txt

got curious, so I started looking around and generated the following output: strings "/games/SteamLibrary/steamapps/common/Arma 3/arma3.i386" | grep -i nvidia NVIDIA Detected NVidia card Available texture memory (from NVidia extension): %u kB NVidia card: restricting reporting of available memory to 768 MB NVidia card: detected 358.00 NVidia driver, kernel version >=3.11 and glibc >=2.19, NOT RESTRICTING memory NVIDIA_PhysX_Help.mht NVIDIA Corporation so it seems like they have VERY specific requirements for the environment they expect.... feeling a bit silly keeping my drivers up to date (currently 361.28)... but I don't think it's me who should reconsider strategies...

Hi. Yep. Had this since the first beta. Was posted by many people in some other thread already (look here: https://forums.bistudio.com/topic/184459-public-beta/), but nothing has changed so far. Can run with ultra-textures on windows7 with same hardware, but only gives me low on linux.. looks very ugly... and sadly no-one up til now came with a working solution / workaround.. small addition: most likely it's an nvidia only issue, especially when running high resolution (4K in my case)... as someone already found out: in the logs of the graphics-wrapper (see: ~/.local/share/bohemiainteractive/arma3/eon.txt) you might find something like this: [thread 00000001][34]: Available texture memory (from NVidia extension): 6291456 kB [thread 00000001][34]: NVidia card: restricting reporting of available memory to 768 MB so, when only that much memory is made available, it's no wonder there's no possibility to get higher res textures... they must have negotiated a good deal with amd/ati to do stuff like that....

tried, but unfortunately it didn't.. auto-setting was low for textures.... only way i could make a high setting available was when reducing the resolution to half size (1920x1080) and setting the sampling to 50%... going back to full res (3840x2160) and 100% sampling the configuration displayed high textures setting but when playing low res textures were used and when i returned to the config menu it showed low or standard (but the displayed quality here is the same)... could run max. texture quality with 4k-res on windows, so doesn't seem to be a general arma3 problem...

have the same problem here, but playing around with settings let's me choose nothing higher than standard... and for me the sample rate can't be set higher than 100% as long as I want to stay at the physical resolution of my display... and no matter what I choose (low or standard), the textures look all the same, as if only the minimum size would be available, which isn't really nice to look at... also tried to modify the config-files directly, using the settings of my old windows installation, but didn't change anything.. visual appearance stays the same.. any additional ideas what to do about it? or simply file a bug-report? otherwise the games runs fine so far.. (besides not supporting rotor-lib, which I really can't understand as physics normally is the easiest things to port / write multi-platform)