[SOLVED]fps drops on proton games

kashishme · 2022-01-26 11:30:01

Lone_Wolf wrote:

[     3.905] (==) Using config file: "/etc/X11/xorg.conf"
[     3.905] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     3.911] (==) ServerLayout "layout"
[     3.911] (**) |-->Screen "intel" (0)
[     3.911] (**) |   |-->Monitor "<default monitor>"
[     3.911] (**) |   |-->Device "intel"
[     3.911] (==) No monitor specified for screen "intel".
	Using a default monitor configuration.
[     3.911] (**) |-->Screen "nvidia" (1)
[     3.911] (**) |   |-->Monitor "<default monitor>"
[     3.911] (**) |   |-->Device "nvidia"
[     3.911] (==) No monitor specified for screen "nvidia".

You either posted the wrong log or didn't remove xorg.conf .

i think there was an error in deleting the file, i did it but whenever i try to remove "20-intel.conf" it shows no such file or directory i can't even see the file through vim or cat terminal just doesn't seem to find it other than plocate, what's wrong? same goes for xorg.conf when i try to see it, i get 'no such file or directory'

Last edited by kashishme (2022-01-26 11:32:33)

Lone_Wolf · 2022-01-26 11:43:18

Post output of

$ ls -lR /etc/X11 /usr/share/X11/xorg.conf.d/

kashishme · 2022-01-26 12:41:23

Lone_Wolf wrote:

Post output of

$ ls -lR /etc/X11 /usr/share/X11/xorg.conf.d/

here: http://ix.io/3NzD

kashishme · 2022-01-26 12:50:39

Lone_Wolf wrote:

Post output of

$ ls -lR /etc/X11 /usr/share/X11/xorg.conf.d/

i almost forgot mlocate needs reboot to refresh the file list, i rebooted and now i am getting 70fps on mirror's edge catalyst, it worked (removing xorg.conf) also the question here is, will i be needing xorg.conf in future? and also the battery saving option i use (prime-render offload) it will keep working right?

V1del · 2022-01-26 13:04:08

The PRIME render offload (...powersaving) was designed with the method you're currently using in mind, if anything it will work "better" (though logically speaking there's no reason for that to be any different if you use the same or other xorg screens) you do not need a xorg.conf, xorg has auto-configuration that will generally do the correct thing. If it didn't do the correct thing then the better approach is targeted snippets that only change single aspects of the configuration as needed, instead of providing the full definition like you used to be doing.

Please don't forget to mark this as [SOLVED] if it's fixed now.

kashishme · 2022-01-27 03:13:52

V1del wrote:

The PRIME render offload (...powersaving) was designed with the method you're currently using in mind, if anything it will work "better" (though logically speaking there's no reason for that to be any different if you use the same or other xorg screens) you do not need a xorg.conf, xorg has auto-configuration that will generally do the correct thing. If it didn't do the correct thing then the better approach is targeted snippets that only change single aspects of the configuration as needed, instead of providing the full definition like you used to be doing.
Please don't forget to mark this as [SOLVED] if it's fixed now.

i will do it after i check if warframe is working properly too

kashishme · 2022-01-27 04:40:51

Ok, it is not solved yet, whenever i start warframe the fps fluctuates from 150 to 30 wildly and before all this i used to go for 150-200 fps smooth as butter
and the proton log is too big to post here and also since this morning even mirror's edge is running slow i haven't done anything since yesterday when everything was fine other than rebooting my laptop

Last edited by kashishme (2022-01-27 04:48:28)

seth · 2022-01-27 07:32:16

Butter is disgusting, so that's a win, I guess.

Updated xorg log and output of "glxinfo -B" and "prime-run glxinfo -B"?
You can upload the proton log anywhere else, in doubt a google drive.

V1del · 2022-01-27 08:01:48

This just sounds like shader caches getting/being rebuilt to me. You'll generally have these episodes whenever there's a driver/mesa update for a short while and they'll eventually fix themselves with enough playing.

kashishme · 2022-01-27 12:50:03

here is the xorg log: http://ix.io/3NFE

kashishme · 2022-01-27 12:51:33

V1del wrote:

This just sounds like shader caches getting/being rebuilt to me. You'll generally have these episodes whenever there's a driver/mesa update for a short while and they'll eventually fix themselves with enough playing.

let me get back to you on that after i play the games again a couple times but i am not sure it will work

seth · 2022-01-27 13:12:31

You're still running on the intel chip but the nvidia chip is available w/ the proper glx library, so "prime-run some_game" should™ work on the nvidia chip.
Possible interference might be from your compositor (if any) and of course any side-load (ie. the CPU, RAM or IO becomes the bottleneck eg. when a file indexer is doing its thing)

kashishme · 2022-01-27 13:15:37

seth wrote:

You're still running on the intel chip but the nvidia chip is available w/ the proper glx library, so "prime-run some_game" should™ work on the nvidia chip.
Possible interference might be from your compositor (if any) and of course any side-load (ie. the CPU, RAM or IO becomes the bottleneck eg. when a file indexer is doing its thing)

i am using picom as my compositor and i tried the prime-run command but it didn't work, should i download 'nvidia-prime' package before doing that? sounds silly but yeah

seth · 2022-01-27 13:37:10

What do you mean by "didn't work"? Yes, it's provided by nvidia-prime and that's what V1del told you to do ~20 posts ago.

Install the package, try to "prime-run" the game, that will run it on the nvidia chip which is supposed to be faster than the intel chip.
Also in doubt kill picom to not get any interference from there and establish a funcitonal baseline.

kashishme · 2022-01-27 14:19:51

seth wrote:

What do you mean by "didn't work"? Yes, it's provided by nvidia-prime and that's what V1del told you to do ~20 posts ago.
Install the package, try to "prime-run" the game, that will run it on the nvidia chip which is supposed to be faster than the intel chip.
Also in doubt kill picom to not get any interference from there and establish a funcitonal baseline.

it didn't work and i think games randomly works and it doesn't this time it didn't work with the prime-run command

seth · 2022-01-27 14:28:26

"did not work" is not an error description, https://bbs.archlinux.org/viewtopic.php?id=57855

'tis going nowhere.

kashishme · 2022-01-27 14:30:34

seth wrote:

"did not work" is not an error description, https://bbs.archlinux.org/viewtopic.php?id=57855
'tis going nowhere.

i apologize for saying that, the command

prime-run %command%

in the properties of a game makes no difference to the low fps

seth · 2022-01-27 14:34:56

Can you query the renderer in the game?
(I have zero experience w/ steam but could assume that this doesn't work for client-side reasons)

What if you "prime-run" the entire proton thing?

V1del · 2022-01-27 15:09:17

Afaik explicitly enforcing prime-run isn't strictly necessary, as DXVK from within proton will have their own code to prefer the dedicated GPU.

For checking this you could e.g. add

DXVK_HUD=1 %command%

which will show on which renderer DXVK is working on.

Some general other notes based on the xorg log, I still think you should try without xf86-video-intel, but that doesn't really explain how this "suddenly" happened, I still believe based on the description that you are simply running into shader cache rebuilding that you'll have to "get through"

kashishme · 2022-01-28 03:19:47

seth wrote:

Can you query the renderer in the game?
(I have zero experience w/ steam but could assume that this doesn't work for client-side reasons)
What if you "prime-run" the entire proton thing?

how do you query the renderer and prime-run the proton thing?

seth · 2022-01-28 08:19:23

See V1del's post and I guess "prime-run steam", though "prim-run" only sets some environment, so you could just export that to some shell and run steam/proton/game from there (again: no steam/proton experience whatsoever)

kashishme · 2022-01-28 09:30:34

apparently it was the shader cache being built, i reinstalled the games and they started working like before (smooth as butter)

Arch Linux

#26 2022-01-26 11:30:01

Re: [SOLVED]fps drops on proton games

#27 2022-01-26 11:43:18

Re: [SOLVED]fps drops on proton games

#28 2022-01-26 12:41:23

Re: [SOLVED]fps drops on proton games

#29 2022-01-26 12:50:39

Re: [SOLVED]fps drops on proton games

#30 2022-01-26 13:04:08

Re: [SOLVED]fps drops on proton games

#31 2022-01-27 03:13:52

Re: [SOLVED]fps drops on proton games

#32 2022-01-27 04:40:51

Re: [SOLVED]fps drops on proton games

#33 2022-01-27 07:32:16

Re: [SOLVED]fps drops on proton games

#34 2022-01-27 08:01:48

Re: [SOLVED]fps drops on proton games

#35 2022-01-27 12:50:03

Re: [SOLVED]fps drops on proton games

#36 2022-01-27 12:51:33

Re: [SOLVED]fps drops on proton games

#37 2022-01-27 13:12:31

Re: [SOLVED]fps drops on proton games

#38 2022-01-27 13:15:37

Re: [SOLVED]fps drops on proton games

#39 2022-01-27 13:37:10

Re: [SOLVED]fps drops on proton games

#40 2022-01-27 14:19:51

Re: [SOLVED]fps drops on proton games

#41 2022-01-27 14:28:26

Re: [SOLVED]fps drops on proton games

#42 2022-01-27 14:30:34

Re: [SOLVED]fps drops on proton games

#43 2022-01-27 14:34:56

Re: [SOLVED]fps drops on proton games

#44 2022-01-27 15:09:17

Re: [SOLVED]fps drops on proton games

#45 2022-01-28 03:19:47

Re: [SOLVED]fps drops on proton games

#46 2022-01-28 08:19:23

Re: [SOLVED]fps drops on proton games

#47 2022-01-28 09:30:34

Re: [SOLVED]fps drops on proton games

Board footer