Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
About Ashes II, is good to read your words. I would like to thank all your efforts
I agree. I think if performance tuning is needed and there is no budget, there are several ways to tackle the problem.
Be very clear and open in your communication and everyone would appreciate it. Even if the performance is less than stellar, i'd still buy it.
I agree, as a Linux user I care about my computer a lot and that's why I stuff it with premium parts. Vega 64, $900 CPU with 16 cores, $400 B-Die 32GB Ram, $400 Motherboard, 3x 50" 4k Displays etc...
I think there is a general unspoken rule that Linux Gamers and users on average try to buy hardware with at least 150% the performance of windows to offset these potential performance dips in various titles when the software just hasn't/can't be optimized as much as the dev would like it to be.
Additionally as stated above, the open source graphics drivers now support game-profiling where the community and driver can identify and apply a optimization profile per game which is helpful too.
The only thing that doesn't work is selecting Vulkan, and I haven't touched Debian's default Vulkan libraries so not too surprising. DX11 mode is good enough to play.
Nice, why don't you send your report to protondb? It would help people know what to do to run with an AMD. :-)
Really? Man, you are missing SO MUCH due to lack of vulkan. Since dxvk/proton I have bought almost a hundred games that I wouldn't be able to play otherwise.
This is what we have going in our new titles we're working on. We have a Cmake option for DX11, DX12, and Vulkan.
Vulkan support in Ashes 1 was pretty...iffy. And that, in turn, make things on Linux a lot iffier when combined with how hard we push the drivers.
For instance, the #1 crash problem in Ashes is in the drivers for NVIDIA cards because we have so many light sources.
These days, making a modern games that isn't using Unity or Unreal means you need to work with the video card leaders can it's a lot easier to get support if it's before the game ships.
Luckily, this effort did lead to good things for the future. It was, as you can imagine, a fairly expensive endeavor for us to port to Linux in the first place, especially since we won't end up being able to recoup that investment with an actual shippable product.
But on the other hand, it allowed us to eliminate the varoius Windows dependencies that were in the code and get our Vulkan support up to snuff.
This in turn made it possible for us to begin supporting Stadia because porting to Linux was the first step on that path.
Good Job thanks for your support!
I really appreciate your honest feedback. I'll proceed to buy your game now, I believe that you deserve my money based on your hard work (not to mention that your game works with proton after using some tweaks... or at least that's what protondb says :P).
I do have Vulkan (vulkaninfo output looks correct AFAICT) but it's just that Ashes wasn't working for me when I tried to relaunch using that setting. Since it doesn't impact my ability to play, I'm not that worried about it.