VaM 1.x The VAM on Linux thread

[atani]

Has anyone had any success getting DLSS 5 to work on Linux?

I'm not a pics guy, but I was curious to try that soon. I did see a comment from a linux user in the DLSS5 thread in the place that cannot be named, so maybe it might?
Did you try with the UncleBurrito resource or another way?

Update:
Can't even get BepinEx working on Arch
Anyone have any tips?

 

[MalMorality]

I'm not a pics guy, but I was curious to try that soon. I did see a comment from a linux user in the DLSS5 thread in the place that cannot be named, so maybe it might?
Did you try with the UncleBurrito resource or another way?

Update:
Can't even get BepinEx working on Arch
Anyone have any tips?

I got it working after all yesterday. I'm not very tech savvy at all, but found out that I of course needed the last version of reshade 6.8.0 with addon support, so I got that installed, along with all the necessary files. Lo and behold it worked after some trial and error. I had no luck with bepinex though. Got tons of help from @Juno to get the right files, and folders set up. Bless the guy!

Edit: Bazzite (Fedora) btw

 

[atani]

I got it working after all yesterday. I'm not very tech savvy at all, but found out that I of course needed the last version of reshade 6.8.0 with addon support, so I got that installed, along with all the necessary files. Lo and behold it worked after some trial and error. I had no luck with bepinex though. Got tons of help from @Juno to get the right files, and folders set up. Bless the guy!

I tried only the UncleBurrito plugin that requires BepinEx but didn't manage bepinex working at that time. Can you share what method you used that wasn't the UncleBurrito plugin to do DLSS 5?

Update:
Finally got it working with BepinEx and UncleBurrito's plugin works too, will update soon instructions.

 

[atani]

VAM on linux with BepinEx:

1. Download the Windows release of BepinEx;
2. Extract the files/folders to the VAM root folder;
3. Configure winecfg in your VAM prefix to use the winhttp proxy as shown on this page;
4. You're done.

Loading the UncleBurrito DLSS5 plugin on VAM:

1. The plugins needs BepinEx, so follow the above instructions;
2. Extract the plugin's files and place them in the appropriate places as shown in the provided readme file;
   • With my packages manager, the plugin's zip had files where the file names included paths instead of being in real folders. If you also see that, rename the files as shown in the readme file and place them in their expected folders.
3. In VAM, toggle the plugin with F10 and see the plugin page for instructions on how to use it.

 

[Sally Whitemane]

Trying to find out which PNG formats are not loading / show messed up of me. (Proton Hotfix atm)
I could really use a IT expert on Window to re-test this on Windows.
I'm completly puzzled where that damn loading bug really is, because I'm very confident that I myself did use 1bit alpha textures on Windows and they worked perfectly fine - which would point to a Proton bug.
But on the other hand I can find multiple links with evidence for the 16bit blueish PNG image bug being an old Unity bug.
Not sure what to believe anymore ... multiple things broken? I don't know ... now I've vibe coded myself a CLI tool in GO, (compiles for Linux and Windows), to scan and convert problematic PNG files and automatically invalidate the matching cache files -> so VaM gegenerates the DXT texture cache.

This is my checklist. Filled out manually by test loading and looking at 72 PNG test images. Maybe other Linux user can re-create and confirm my findings. AI can easily generate a similar PNG test suite.

## 01_colortype_bitdepth_interlace — Color type x bit depth x interlace (core matrix) (30 files)

| Loads | Shows correct | File | Notes |
|:---:|:---:|---|---|
| [❌] | [❌] | `gray_1bit_noninterlace.png` |convert to 2bit|
| [❌] | [❌] | `gray_1bit_adam7.png` |convert to 2bit|
| [✅] | [✅] | `gray_2bit_noninterlace.png` | |
| [✅] | [✅] | `gray_2bit_adam7.png` | |
| [✅] | [✅] | `gray_4bit_noninterlace.png` | |
| [✅] | [✅] | `gray_4bit_adam7.png` | |
| [✅] | [✅] | `gray_8bit_noninterlace.png` | |
| [✅] | [✅] | `gray_8bit_adam7.png` | |
| [✅] | [✅] | `gray_16bit_noninterlace.png` | |
| [✅] | [✅] | `gray_16bit_adam7.png` | |
| [❌] | [❌] | `palette_1bit_noninterlace.png` |convert to 2bit|
| [❌] | [❌] | `palette_1bit_adam7.png` |convert to 2bit|
| [✅] | [✅] | `palette_2bit_noninterlace.png` | |
| [✅] | [✅] | `palette_2bit_adam7.png` | |
| [❌] | [❌] | `palette_4bit_noninterlace.png` |convert to 8bit|
| [❌] | [❌] | `palette_4bit_adam7.png` |convert to 8bit|
| [✅] | [✅] | `palette_8bit_noninterlace.png` | |
| [✅] | [✅] | `palette_8bit_adam7.png` | |
| [✅] | [✅] | `rgb_8bit_noninterlace.png` | |
| [✅] | [✅] | `rgb_8bit_adam7.png` | |
| [✅] | [❌] | `rgb_16bit_noninterlace.png` |convert to 8bit|
| [✅] | [❌] | `rgb_16bit_adam7.png` |convert to 8bit|
| [✅] | [✅] | `grayalpha_8bit_noninterlace.png` | |
| [✅] | [✅] | `grayalpha_8bit_adam7.png` | |
| [✅] | [✅] | `grayalpha_16bit_noninterlace.png` | |
| [✅] | [✅] | `grayalpha_16bit_adam7.png` | |
| [✅] | [✅] | `rgba_8bit_noninterlace.png` | |
| [✅] | [✅] | `rgba_8bit_adam7.png` | |
| [✅] | [✅] | `rgba_16bit_noninterlace.png` | |
| [✅] | [✅] | `rgba_16bit_adam7.png` | |

## 02_transparency_trns — Transparency via tRNS (5 files)
transparency works different anyway, ignore test!

| Loads | Shows correct | File | Notes |
|:---:|:---:|---|---|
| [✅] | [ ] | `gray_8bit_trns_colorkey_black.png` | |
| [✅] | [ ] | `gray_16bit_trns_colorkey_black.png` | |
| [✅] | [ ] | `rgb_8bit_trns_colorkey_black.png` | |
| [✅] | [ ] | `rgb_16bit_trns_colorkey_black.png` | |
| [✅] | [ ] | `palette_4colors_trns_partial_alpha.png` | |

## 03_ancillary_chunks — Ancillary chunks (12 files)

| Loads | Shows correct | File | Notes |
|:---:|:---:|---|---|
| [✅] | [✅] | `baseline_no_ancillary.png` | |
| [✅] | [✅] | `with_gAMA.png` | |
| [✅] | [✅] | `with_sRGB.png` | |
| [✅] | [✅] | `with_cHRM.png` | |
| [✅] | [✅] | `with_iCCP.png` | |
| [✅] | [✅] | `with_pHYs_72dpi.png` | |
| [✅] | [✅] | `with_pHYs_300dpi.png` | |
| [✅] | [✅] | `with_bKGD.png` | |
| [✅] | [✅] | `with_tEXt.png` | |
| [✅] | [✅] | `with_iTXt_utf8.png` | |
| [✅] | [✅] | `with_tIME.png` | |
| [✅] | [✅] | `with_all_chunks_combined.png` | |

## 04_filter_methods — Forced scanline filter methods (6 files)

| Loads | Shows correct | File | Notes |
|:---:|:---:|---|---|
| [✅] | [✅] | `filter_0_none.png` | |
| [✅] | [✅] | `filter_1_sub.png` | |
| [✅] | [✅] | `filter_2_up.png` | |
| [✅] | [✅] | `filter_3_average.png` | |
| [✅] | [✅] | `filter_4_paeth.png` | |
| [✅] | [✅] | `filter_adaptive_baseline.png` | |

## 05_idat_chunking — IDAT chunk splitting (4 files)

| Loads | Shows correct | File | Notes |
|:---:|:---:|---|---|
| [✅] | [✅] | `idat_single_large_chunk.png` | |
| [✅] | [✅] | `idat_64k_chunks.png` | |
| [✅] | [✅] | `idat_1k_chunks.png` | |
| [✅] | [✅] | `idat_100b_chunks.png` | |

## 06_dimensions — Dimension edge cases (11 files)
It seems a minimum of 4 is a must?

| Loads | Shows correct | File | Notes |
|:---:|:---:|---|---|
| [✅] | [✅] | `dim_1x1.png` | |
| [✅] | [✅] | `dim_2x2.png` | |
| [✅] | [❌] | `dim_3x5.png` | |
| [✅] | [✅] | `dim_7x13.png` | |
| [✅] | [✅] | `dim_17x257.png` | |
| [✅] | [✅] | `dim_255x255.png` | |
| [✅] | [✅] | `dim_513x513.png` | |
| [✅] | [✅] | `dim_1024x1024.png` | |
| [✅] | [✅] | `dim_4096x4096.png` | |
| [✅] | [❌] | `dim_4096x1.png` | |
| [✅] | [❌] | `dim_1x4096.png` | |

## 07_apng_bonus — APNG (bonus, outside core PNG) (1 file)
* Shows correct non animated.

| Loads | Shows correct | File | Notes |
|:---:|:---:|---|---|
| [✅] | [✅*] | `apng_4frame_colorcycle.png` | |

## 08_reference — Reference (3 files)

| Loads | Shows correct | File | Notes |
|:---:|:---:|---|---|
| [✅] | [✅] | `smoke_test_solid_red_64x64.png` | |
| [✅] | [✅] | `lenna_original_untouched.png` | |
| [✅] | [✅] | `lenna_recompressed_rgba8_256.png` | |

 

[atani]

Hi, @Sally Whitemane

When I switched to Proton-EM I never again encountered any dreaded blue skin, if you want to use that one.

 

[Rezz]

Hey all I just moved to Linux completely. I'm still figuring things out. So I have a valve index I'd like to use with vam. I have vam on it's own ssd, which is still using NTFS but I can mount it in Bazzite just fine. I have tried running vam with Lutris, and the vam_updater.exe just crashes. When I set it to use vam.exe it looks like it's running in VR mode but nothing shows in my index headset and it causes steamVR to crash shortly after.
I have tried adding VaM.exe as a non-steam game and running it from steam, but the same thing happens. I have GE-proton 11-7 installed and that's what I tried to use.
Any suggestions?

i'm jealous of you wireless headset ppl. maybe someday I can get the frame
Also, steamVR shows that it's running "wine64-preloader" when I try to run vam through Lutris, and before it crashes. idk if that's useful info

 

[atani]

I don't have an Index or that OS, so I cannot attest to things working as well. And saying "as well", I had to go back to Windows for VR use for a while as my linux VR experience was having major issues with artifacts and other things. "Horny time" and the time needed to fix everything were not compatible enough, so I escape to Windows for those moments while work continues on VR linux.

That said, you should read this page that I linked to from the first page: https://vronlinux.org/
Index may need Monado + Envision to get things working well, so do read that section well. I also suggest you create bat files, or use the existing ones in the VAM root folder, instead of using vam_launcher.exe, as you can edit those to your needs more easily.

My setup is listed below, which is not suitable to your headset but I list it anyway for others:

• OS: archlinux
• Wine manage: Faugus Launcher
• VR and other tools: wivrn (Pico 4), wayvr, xryzer, yakuda connect, proton plus

 

[NewQuestUser2]

Hey everyone. Just wanted to see if anyone else is running into this but I've tried Fedora, Mint, and Zorin. I keep running into the issue that at the setup menu launching VaM for the first time I cannot click any of the buttons. I can see my cursor, but nothing registers. I added VaM.exe as a non-steam game and tried using proton experimental and proton-ge, but nothing works. I'd appreciate any help.

 

[atani]

Hey everyone. Just wanted to see if anyone else is running into this but I've tried Fedora, Mint, and Zorin. I keep running into the issue that at the setup menu launching VaM for the first time I cannot click any of the buttons. I can see my cursor, but nothing registers. I added VaM.exe as a non-steam game and tried using proton experimental and proton-ge, but nothing works. I'd appreciate any help.

Did you try Faugus Launcher? It's what I use for running windows stuff.

 

[bzq]

hey, very psyched to say I got Vam running in cachyOS with VR! I did it the simplest way I could and may need to try some things to improve performance such as wiVRn, but all I did was:
installed steam and steamVR with pacman -S steam
got steamVR working with my prismxr wifi (doesnt connect to internet just bridge pc and headset). this included opening ports for steam since udw was blocking it. after I had the prismxr working as a bridge I added this command to steamvr launch options to turn on and off the connection:
nmcli dev connect <wifi device id like enp...>; %command%; nmcli dev disconnect <wifi device id like enp...>
then added vam as a non steam game in steam twice - once with launch options -vrmode OpenVR and once without for desktop

and it worked! I couldn't believe it

 

[atani]

Some weeks ago I had the heartbreaking decision to once again install Windows to do VR VAM, as I was having several issues with VR on archlinux. I couldn't find a way to resolve those, and so needed to check with Virtual Desktop if the problem was on software, the router-VR location, etc.
VAM on VD worked okish, but SteamVR for using Heresphere was just horrendous. So the fallback was shit, and so the new plan was to try a clean linux and hope that since then a fix for my problems in VR had appeared.

This time insteal of a plain arch install where I could easily miss something that could make a difference with VR performance, nvidia tweaks, and other things, I went for CachyOS and place my hopes on that being handled by the build for a solid VR ground. I went back to my prefered tools for VR: yakuda-connect to handle all VR stuff, and faugus launcher for the proton stuff.
Suffice to say, it was the best VR experience with VAM on passthrough. WayVR handles passthrough so much better than VD in the latest version, and all the weirdness and issues I had several weeks ago seem to be gone. Hurrah.

Now, I don't know if the OS change - arch to cachy - made a difference, but for a mainly gaming machine it helps a lot to not spend much time looking up and configuring things. The other tools also had updates so more likely it was there that problems were resolved, and VR on linux never looked better.

My updated setup for running VAM desktop and VR:

• OS: CachyOS
• Wine manage: Faugus Launcher
• VR tools: yakuda-connect (wivrn handler), wayvr, xryzer

For those using SteamVR. consider using the above and compare as SteamVR can be quite buggy.

P.S. I think I finally have an assurance that I won't ever need to install Windows again, all special usecases are now handled on linux. Hurrah hurrah hurrah.