One of the developers from Bohemia Interactive who's active in our community is asking to see how much interest there is in the Linux port of Arma 3 [Steam Page]. Currently, the Linux (and Mac) ports of Arma 3 from Virtual Programming are hidden from the Steam store page, because Bohemia Interactive class them as experimental. You can install it from Steam like any other game, it's just not advertised.
The developer, who goes by the nickname Dwarden, has asked me to make it clear that this is not an official poll. They're simple trying to find out just how much community interest there is.
On their Discord, they've pinned a message in the "linux_mac_branch" channel that reads:
How many users @here use Linux / Mac ports or may get interested to use ?
(especially if the delay time of port shortens after the Windows release ? )
{you can use reaction to add to the counter(s)}
{just to be clear this unofficial poll is for insight}
You can join their Discord using this link, to let them know your thoughts and add to the "reaction counter" if it's important to you. Once you're in their discord, if you have trouble finding the message here's a direct link (only works if you've joined).
Naturally, commenting here as well will also help so they can see outside interest and for those of you who don't like Discord you can also make yourselves known.
Personally, I quite enjoyed the last time I jumped in with a bunch of members from the community, it performed reasonably well and we all had a really great time. It's a pretty fascinating game, one I wouldn't experience without a Linux port so I really do hope they keep pushing forwards to eventually have it properly advertised on Steam.
Of course, not having it actually advertised won't really help since people won't know unless they're told about it. There's also nothing else like it on Linux, so I feel it's quite important.
Article taken from GamingOnLinux.com.
Quoting: Guest... Although I dislike the way developers always want to make the Linux community beg for titles. But at least they're showing interest, have to give them that.My best guess is there is one person that is trying to convince the business to upgrade Linux support. The best way to do that is to prove that it's not charity work.
They were down grading at one point but that just becomes a pain for them then. So now I rarely play it do to the above!:(
Quoting: GuestQuoting: sonicYou says that is Mesa bug, but from Mesa devs response I am no so sure. And lets be honest, this is mainly caused by the d3d->ogl translation layer.
It is, and the proof is that it does not happen on the Nvidia driver, nor does it happen under MacOS under OpenGL. D3D->GL has nothing to do with it.
That it works on the nVidia driver is proof of exactly nothing. nVidia is known for adding support for broken behaviour and the problem for Mesa here is if they are to be following the OpenGL specifications or if they are to allow nVidia to dictate the OpenGL specifications.
Unfortunately many game devs use nVidia so they don't know that they are not following the specs since it "just works".
Quoting: F.UltraQuoting: GuestQuoting: sonicYou says that is Mesa bug, but from Mesa devs response I am no so sure. And lets be honest, this is mainly caused by the d3d->ogl translation layer.
It is, and the proof is that it does not happen on the Nvidia driver, nor does it happen under MacOS under OpenGL. D3D->GL has nothing to do with it.
That it works on the nVidia driver is proof of exactly nothing. nVidia is known for adding support for broken behaviour and the problem for Mesa here is if they are to be following the OpenGL specifications or if they are to allow nVidia to dictate the OpenGL specifications.
Unfortunately many game devs use nVidia so they don't know that they are not following the specs since it "just works".
Can we stop this please?
Just because of that nonsense attitude , AMD users are still suffering when try to play Dying Light like games.
Is your goal running all games you have without issues as a gamer or caring about driver hacks etc?
Quoting: GuestQuoting: F.UltraThat it works on the nVidia driver is proof of exactly nothing. nVidia is known for adding support for broken behaviour and the problem for Mesa here is if they are to be following the OpenGL specifications or if they are to allow nVidia to dictate the OpenGL specifications.
Unfortunately many game devs use nVidia so they don't know that they are not following the specs since it "just works".
Yawn. You completely missed the part where I said it works on OS X's GL drivers too then. On ALL GPU's there. Also it worked on Catalyst. Nice one in turning it into an opportunity to bash Nvidia though.
Just so you know.. my main Linux box has an AMD card in it.
The same applies. OSX OGL implementation is done by AMD or Nvidia on their propietary drivers. That it works somewhere else is no proof of nothing. Mesa devs try to follow very tightly the OpenGL specs, so it wouldn't surprise me if there is a misunderstanding of the OGL specs from VP devs side.
https://stackoverflow.com/help/mcve
Quoting: GuestThats not always feasible when youre talking about a complex engine. We gave them copies of the game and info from RenderDoc. We even brought Marek and Nicolai into our company Ryver server to discuss it in depth.
I'm pretty disappointed that it's been left to a workaround option to fix, but there it is.
It sounded to me like "We were generous, we let them debug our program, and they even got it for free. Plus it's only one (of two...) drivers where our game's not working."
But I understand such things can be rather complex (that's why I wrote "strive for" not "provide"...).
Patreon
PayPal
See more from me