Update: I managed to get it working, head to your prefences file located here:
Set the fullscreen mode to zero and set some height and width and it seemed to reset it. Now it works normally on the first load, but it will break again. You need to set the windowed mode to zero each time you want to load it, for now. Vulkan seems to require the exact height and width too.
Update 2: A better option, is to force all this as a Steam launch option for the game like one of these:
Or
Some quick thoughts on the new version:
The new AA modes are nice to have and the higher modes certainly look good on OpenGL, but with Vulkan if you select 2xMSAA or higher the performance falls off a cliff. If you find Vulkan performing poorly, check your AA level as it seems to badly affect the Vulkan version.
This update has also introduced other issues. You can often see enemy outlines through walls, which obviously breaks the game quite a bit.
The new auto join queue feature for full-servers sometimes seems to completely break not letting you actually join a game. Claiming you're next in the queue, even with space available. If there isn't space available, clicking auto join will end up sitting on the player list, claiming you will be a spectator until space is available, but never actually progress into putting you into spectator mode. Sometimes it does work, it just seems to be a mess now.
The new "friends playing" feature also doesn't seem to work, with it showing zero for me. Even though checking my Steam list, with people clearly playing it.
Servers now sometimes outright refuse to let you join them, with a simplistic error message about failing.
The Vulkan version gives higher FPS in certain areas, but it's no way near as smooth as the OpenGL version.
Yeah...they're going to need to polish this up quite a lot.
Original article:
Confirmed by others as well, the latest Ballistic Overkill that adds in Vulkan and many other things, has completely broken the Linux version.
Yesterday, I broke the news that Ballistic Overkill would be updated today with Vulkan, new friends features, new AA options and loads more.
The OpenGL version gives a black screen and the Vulkan version just instantly crashes, as of today. The developers are already aware of it, as I've already been in touch with them about the issues.
Shame, was pretty hyped to try it with Vulkan and it is a very fun game. I'm willing to give the developer a little leeway here since I enjoy it so much, but considering all the people that have confirmed the Linux version is broken to me, including testing it myself, I am a little annoyed personally. It seems not enough testing was done their end on the Linux version.
Investigating it a bit further, it seems it may be a similar problem to the issues facing White Noise 2 at the moment. The game seems to set zero for the resolution width and height. I tried setting them manually, but the game overwrites the preferences file on loading.
.config/unity3d/Aquiris Game Studio/Ballistic Overkill/prefs
Set the fullscreen mode to zero and set some height and width and it seemed to reset it. Now it works normally on the first load, but it will break again. You need to set the windowed mode to zero each time you want to load it, for now. Vulkan seems to require the exact height and width too.
Update 2: A better option, is to force all this as a Steam launch option for the game like one of these:
-screen-fullscreen 0 -screen-width 1920 -screen-height 1080 -force-vulkan
Or
-screen-fullscreen 0 -screen-width 1920 -screen-height 1080 -force-glcore
Some quick thoughts on the new version:
The new AA modes are nice to have and the higher modes certainly look good on OpenGL, but with Vulkan if you select 2xMSAA or higher the performance falls off a cliff. If you find Vulkan performing poorly, check your AA level as it seems to badly affect the Vulkan version.
This update has also introduced other issues. You can often see enemy outlines through walls, which obviously breaks the game quite a bit.
The new auto join queue feature for full-servers sometimes seems to completely break not letting you actually join a game. Claiming you're next in the queue, even with space available. If there isn't space available, clicking auto join will end up sitting on the player list, claiming you will be a spectator until space is available, but never actually progress into putting you into spectator mode. Sometimes it does work, it just seems to be a mess now.
The new "friends playing" feature also doesn't seem to work, with it showing zero for me. Even though checking my Steam list, with people clearly playing it.
Servers now sometimes outright refuse to let you join them, with a simplistic error message about failing.
The Vulkan version gives higher FPS in certain areas, but it's no way near as smooth as the OpenGL version.
Yeah...they're going to need to polish this up quite a lot.
Original article:
Confirmed by others as well, the latest Ballistic Overkill that adds in Vulkan and many other things, has completely broken the Linux version.
Yesterday, I broke the news that Ballistic Overkill would be updated today with Vulkan, new friends features, new AA options and loads more.
The OpenGL version gives a black screen and the Vulkan version just instantly crashes, as of today. The developers are already aware of it, as I've already been in touch with them about the issues.
Shame, was pretty hyped to try it with Vulkan and it is a very fun game. I'm willing to give the developer a little leeway here since I enjoy it so much, but considering all the people that have confirmed the Linux version is broken to me, including testing it myself, I am a little annoyed personally. It seems not enough testing was done their end on the Linux version.
Investigating it a bit further, it seems it may be a similar problem to the issues facing White Noise 2 at the moment. The game seems to set zero for the resolution width and height. I tried setting them manually, but the game overwrites the preferences file on loading.
Some you may have missed, popular articles from the last month:
Quoting: pete910Not just me then.
Edit:
This shows in console when run
Player data archive not found at `/mnt/games/steamapps/common/Ballistic/BallisticOverkill_Data/data.unity3d`, using local filesystem[pete@com1 Ballistic]
I noticed this with the recent Zombie Night Terror update too. So I don't think it's an isolated thing at this point, but more likely a Unity issue.
Same issue, same solution, different game.
Last edited by Luke_Nukem on 16 May 2017 at 9:26 pm UTC
0 Likes
Quoting: XicronicThere also seems to be an in-game bug now where people can see others through walls. It's become a sniperfest =/
You're not wrong. I experienced that this evening, however I do need all the help I can get :-)
0 Likes
Here's how it runs on i7-4790k and GTX1070 using Vulkan. Both 8xMSAA and like pre-Vulkan FXAA:
View video on youtube.com
There's still a lot of room for improvement.
View video on youtube.com
There's still a lot of room for improvement.
0 Likes
Quoting: pete910This shows in console when runThis is just a diagnostic message about an optional feature, not an error.
Player data archive not found at `/mnt/games/steamapps/common/Ballistic/BallisticOverkill_Data/data.unity3d`, using local filesystem[pete@com1 Ballistic]
The resolution issue is being researched.
0 Likes
Seems a lot of people can, and a lot can't run it at the moment.
Darrn, I have time this evening and wanted to give it a try on my RX460 and GTX1050 graphics cards to see...
Fingers crossed I'm among the lucky ones. For the sniper bug - I usually play sniper, and since I'm bad at FPS games, it's a good thing they decided to help me :D.
Last edited by STiAT on 17 May 2017 at 10:44 am UTC
Darrn, I have time this evening and wanted to give it a try on my RX460 and GTX1050 graphics cards to see...
Fingers crossed I'm among the lucky ones. For the sniper bug - I usually play sniper, and since I'm bad at FPS games, it's a good thing they decided to help me :D.
Last edited by STiAT on 17 May 2017 at 10:44 am UTC
0 Likes
Well, there's an update for it but still broke on my end :(
0 Likes
It does work for me with the workarounds from the top of the page. As most other people, I couldn't start the game after the latest update and so I went straight to GOL, hoping to find more info here. Sure as hell I did find it! :) Hopefully, they're gonna fix this soon, the scale of the issue suggests very poor testing routine (for Linux at least).
0 Likes
Quoting: drvictor666It does work for me with the workarounds from the top of the page. As most other people, I couldn't start the game after the latest update and so I went straight to GOL, hoping to find more info here. Sure as hell I did find it! :) Hopefully, they're gonna fix this soon, the scale of the issue suggests very poor testing routine (for Linux at least).It's highly possible it's a Unity bug, as Unity Engine dev Tak commented above.
0 Likes
Quoting: NaibQuoting: PieGamer314Strange, it never broke for me. I opened it up as soon as it finished updating and it worked just fine.
what GPU? what drivers?
I have nvidia-381.22 and vulkan crashes for me. I am just finishing recompiling libreoffice and ill try with the launch string from above
I'm running it on a laptop with an AMD apu and whatever the default graphics driver is in ubuntu.
0 Likes
Actually, for me is setting:
-screen-fullscreen 0
enough to get it running properly. Don't need to set a resolution. Interestingly: I only have one screen XD.
Last edited by STiAT on 17 May 2017 at 5:51 pm UTC
-screen-fullscreen 0
enough to get it running properly. Don't need to set a resolution. Interestingly: I only have one screen XD.
Last edited by STiAT on 17 May 2017 at 5:51 pm UTC
0 Likes
See more from me