@Biochemikas I don't think it's working, since you received a higher fps than the max you set. Think they did remove the function of this command w/ the new patch.. my issue is that I have a 240hz monitor and 144hz~ processor, so I set it to 144hz. So right now since this command isn't working (for me) and my cpu is on autopilot, when I land it's basically overclocking itself trying to hit 240 and crashes.
It definitely is working. As I said, my fps goes all the way up to 300+ if I remove it (I did have it set to 0 before this patch and changed it to 237 just recently). Well I didn't try any other value, maybe it is 240 or 0, dunno. But since 240 is what I need anyway (and I don't need to be strictly lower than 240 since I have Gsync off), I won't be testing it further. Try setting it to something much lower and see if it has an effect. E.g., try something like 60 or 100.
P.S. If you're seeing fps all the way up to 300, then your command text must be wrong.
Mine is "+fps_max 237 -novid" (I think, I can't remember now and can't check atm). The -novid command does nothing anymore (used to remove the ultra loud splash screen), but mine is still there, maybe try leaving a space after number if nothing works ("+fps_max 100 ").
Community Manager
