apex greyed out reflex options... werid bug

[kunihir0]

The titled is true but towards the end of this post it won't be lol because I encounter a weird bug I think its specific to having the installed game on a different drive. for example on my setup before I fixed the problem by redoing the steps but having apex on the same drive.

here is how it was structured

drive: a) has apex on my mainos drive: b) accessing apex in drive a where originally I was using drive:a as my gaming but decided later to use a new os for my gaming. After finishing the new install and downloading the required packages to get steam to run apex. A biit later, I got everything all setup an running, now I just imported my steam library where in this case would be in drive:a so I choose drive:A/home/kunihiro/.local/share/Steam... and it found my apex install thats good.

Drive:A ) Main OS/
├─ Apex - installed with MainOs steam install 
Drive:B ) Gaming OS/
├─ Steam accessing Apex in Drive:A

at this point I grabbed lutris fixed up everything there along with the env vars for apex to get latencyflex running. I installed everything to the right place but a weird things I had to do was directly set the DXVK_CONFIG_FILE=/fullpathto/dxvk.conf in lutris as directly place the dxvkl.conf in the apex folder will result in a error outputted in the logs using the env var in launch options for apex PROTON_LOG=1 DXVK_NVAPI_LOG_LEVEL=info

so to solve this I had to redo every step slowly and moving my Apex to my GamingOs and setting the dxvk conf env var.

additional information:

My main os has the folder with the appid on the main os so when I start apex it starts the wine prefix in the main os where I had originally installed apex and not the second os.

so my gaming os does not create the folder steamapps/compatdata/**appid** as it is already using the one created on the main os drive:a/home/..../steamapps/compatdata/**appid**

my logs got overwritten as I keep starting Apex... sorry about that

[ishitatsuyuki]

Please find ways to grab a log. Without that there's no practical way to troubleshoot nor provide help.

[kunihir0]

I have to do that next weekend to reproduce the bug with logging.

[kunihir0]

got the logs https://www.klgrth.io/paste/ar2en/raw

my launch options PROTON_LOG=1 DXVK_NVAPI_LOG_LEVEL=info PROTON_ENABLE_NVAPI=1 DXVK_NVAPI_DRIVER_VERSION=49729 DXVK_NVAPI_ALLOW_OTHER_DRIVERS=1 LFX=1 %command%

[ishitatsuyuki]

I think it probably has something to do with the Steam container runtime not handling cross drive symlinks correctly. Try replacing the symlinks from the installation instructions with a copy.

[miyagui]

fixed by 0.1.1