Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

"Voices Of The Void" Pre-Alpha

Gather unknown signals from deep, silent space · By mrdrnose

There are plans to launch a Linux version?

A topic by Degirme created 17 days ago Views: 593 Replies: 7
Viewing posts 1 to 5

Does anyone know if there are plans to release a Linux version? I can't play using Wine. Does anyone have a solution? Anyone knows if there are plans to launch a Linux version? I can't play it using wine. Someone

I'm not the best person to type out a guide but there is a way. Do you have steam? If you do then extract the game to your file system. Then go to steam click the "add game" button on the bottom left and select "add non-steam game". Find VotV and add it to your libary. Then right click on the game in your libary and select "Properties" Then in the compatibility tab tick the "Force the use of a specific Steam Play compatibility too" and then choose the proton version you want to use. (I'm currently running experimental. I have had no issues running the game on linux this way.

This trick can get other non-steam games to use the proton emulator if needed.

I run many games using steam proton as well. I tried the method you described but it didn’t work for me. Wine provides a similar approach to emulating Windows programs, allowing windows games to run on Linux systems, I finally managed to get it running using Wine, but the experience wasn’t great. T he game was quite broken and far from playable.

Wine is garbage and sucks in running anything in general.

If your game wont launch at all when trying Proton, try to:

- Different Proton versions (not actual versions, but stuff like latest version, "hotfix", "experimental", and so on)

- Move the game files to your OS partition (yes, that indeed may work, you don't even need to change your Proton version)

(1 edit) (+1)

This broke the seal for me, so I finally decided to figure out why Steam wasn't working for me but worked for some people...

When I first installed Linux, I somehow installed 2 versions of Steam - the deb and the flatpak version.

Apparently flatpaks have less privilege and this is causing issues. So I purged both! I did it in an incredibly awful way as I bounced through tutorials, initially doing
[dpkg --list]   ... Yes I manually purged anything that said Steam, I think this was mayhaps not the best option as when I installed steam with [sudo apt install steam], it didn't even boot anymore. Yikes!

So naturally I searched for my problem and found this steam thread: https://steamcommunity.com/app/221410/discussions/0/3094509155628372846/


I'm sure there was some redundancy, but I followed 1, 3, 5, 6, then input [steam] into the terminal. It worked! I noticed it removed more libs than I had managed with my initial purging, probably related XD
EVEN BETTER, THE GAME BOOTED! I don't know if that's because previously I had run the UE4PrereqSetup_x64.exe and finished the installation, which got rid of my C++ runtime error, but that's what learnin' on the jobs all about.

I noticed exit didn't work, so there will likely be some issues. Someone mentioned on reddit that their TV didn't work?

I hope this helps my Linux homies out there. I'm using Pop OS LTS with some duct-tape to make Nvidia work. Best of luck!

Edit: I forgot to mention, I also run it with Compatibility: Proton Experimental

I only had problems with games on Steam when I tried to install the latest Ubuntu distro, Ubuntu 24.04 LTS (probably due to lack of drivers.). Other than that, I have no problems, almost everything runs very well. I now use Pop OS as well and have no major problems. Regarding Proton, in some games, especially online games, it is necessary to add Proton GE, an alternative and unofficial Proton.

But specifically in this case of Voices of the Void (maybe because is a non-steam game? Idk), the same error persisted as with C++. What I did was install C++ from Wine, but, as I reported above, it did not work.

I'm not sure if this'll help, but here's my limited understanding...

Each game that you run on Steam via each separate version of proton, and I think this includes wine in general, will be running its own windows environment and that includes its own dependencies. So if you added VotV to steam as a non-steam game and try to run it with Proton, it will set up this new environment without any dependencies like C++... DirectX... .Net Framework, etc... Probably something like that.

So it's super important in the case of steam to... Hover over the game title in your library -> RMB -> Properties ->Shortcut -> Target -> Browse -> [/home/freyr05/Games/pa0082_0012/pa0082_0012/WindowsNoEditor/Engine/Extras/Redist/en-us/UE4PrereqSetup_x64.exe] -> Click PLAY

The above is the route to my destination. It ran an installer and I let it do its thing. It looks like I tried running every other .exe available before realizing I needed to reinstall Steam from the terminal rather than the PopShop.

If you get an error message beyond the C++ one, then it'll be related to the Steam installation, but for now try doing the above if things still aren't working.

BONUS - Windows Environment Location: /home/freyr05/.steam/steam/steamapps/compatdata/3915131074/pfx/drive_c/users/steamuser/AppData/Local/VotV... The .steam folder will be hidden by default so make sure you enable display hidden files in your file explorer. You might know this, but I'll add it for incoming users as well. Numerical location might be different; I organized by most recent folder since it was brand new as a cheat.

I also actually wasn't sure if the initial paragraph was true, so as a test I ran VoTV under Proton 8.05 (fresh) and it prompted the installation process of C++. It actually auto-ran the installer this time? Maybe because I'm using the alternative version of Steam now? Hard to say, but I hope some of this helps in any capacity.

Keeping this separate since you mentioned drivers... just in case you're a nvidia user like me, the popshop wouldn't let me install drivers beyond 470.256.02 and it's STILL prompting me to install it despite my manual installation of 565.77

That was the duct-tape I was referring to. I'm not sure what the average user experience is for Nvidia drivers, but might as well get all the eggs in a row, eh?