>Read the sticky: >>105076684>GNU/Linux questions >>>/g/fglt>Windows questions >>>/g/fwt>PC building? In this market?! >>>/g/pcbg>Programming questions >>>/g/dpt>Cheap electronics >>>/g/csg>Server questions >>>/g/hsg>Buying headphones >>>/g/hpg>Useful programs and live Windows environment:https://hirensbootcd.org/download/Previous: >>108387207
Do I need to close Chrome, Firefox, Spotify and other few programs before I start a game?
Which FOSS project is this Popsicle eating? https://www.youtube.com/watch?v=Z7bvYsBudr0&t=35>>108413309Depends entirely on the game and the resources available on your machine. In theory, all of that should be swapped out of memory and have low background priority when your game is running, but in reality most modern software has bad manners and will do inane shit in the background if your OS lets it.
>>108413309If you have some video open in a browser then it can mess with your monitor(s) in various ways, such as HDR and refresh rate.
>>108413309if you are trying to extract every single possible frame out, yes, but this is usually pointless. typically you have a target framerate that looks good to you (i have very low standards and for me it's 45fps) and you balance that with convenience. as long as your framerate stays at or above your target during heavy scenes you probably don't need to close things unless they're causing issues (and the only thing i've found to cause issues is trying to screenshare in discord while i'm in a game while gsync is on). if it dips below that and you aren't willing to reduce the game's settings in some way, check which hardware is bottlenecking and then close whatever might be contributing (if it's ram, close tabs, if it's gpu, close videos, etc).also if you aren't using vsync (i.e. if you're using gsync/equivalent or if you're just not using a sync solution) make sure to set a global fps cap so your computer isn't trying to crank out every single possible frame it can and using unnecessary resources and generating unnecessary heat.
>>108413712oh, note that gsync won't have this issue but you still want a framerate cap a little ways below your refresh rate, forgot to mention