*solved* Game is limited to 60fps MAX now. What gives?

[Wow!]

---> Crinkly solved it - changing the .ini fixed it. No idea why it was set to 60.000. Changed it to 120 and my fps is back to normal now.

I've got a Gsync 120hz display. I've tried Gsync off, Vsync off, no change. In Nvidia Control Panel & in Hell Let Loose itself. This started this morning.

[TWB*Clell_Miller]

Let me check.... (checking...) Server list coming up at 110 FPS. I hear that's a typically a stress point.

[Wow!]

Originally posted by TWB*Clell_Miller:

Let me check.... (checking...) Server list coming up at 110 FPS. I hear that's a typically a stress point.

What do you mean? My fps in other games is still normal.

[Dont be Silly Wrap your Willy]

Either your pc cant punch above 60 or you have a lock somewhere because game is most def not locked to 60 by it self.

[Wow!]

Originally posted by Dont be silly Wrap your willy:

Either your pc cant punch above 60 or you have a lock somewhere because game is most def not locked to 60 by it self.

It used to do 90ish avg

[SVEN-148]

I am having same issue capped at a constant 60fps used to get any where between 98fps to 140 fps depending on map and server. Started when i last played on the PTE server last friday running on a i7 cpu 10th gen, RTX 2080 Super GPU and either a MSI 165HZ 1440p monitor or my Omen 240hz 1080p monitor, tried changing gpu settings and monitor settings as well as fresh install all no good capped at a constant 60fps only for HLL

[Wow!]

Originally posted by SVEN-148:

I am having same issue capped at a constant 60fps used to get any where between 98fps to 140 fps depending on map and server. Started when i last played on the PTE server last friday running on a i7 cpu 10th gen, RTX 2080 Super GPU and either a MSI 165HZ 1440p monitor or my Omen 240hz 1080p monitor, tried changing gpu settings and monitor settings as well as fresh install all no good capped at a constant 60fps only for HLL

I've had a couple other people in-game say they are having this issue as well. Idk if some secret update borked something or what~ It's so weird.

[Crinkly]

Go to:
C:\Users\USERNAME\AppData\Local\HLL\Saved\Config\WindowsNoEditor
Then open the file called : GameUserSettings (.ini )
Once the file is open you will have a window popping up there you need to find the line with :
Frameratelimit : 60.0000
And change 60 to 0 for unlimited cap or use your screen Hz ( 60-120-144-240 etc ) for it to match your screen frame.

This is from HLL discord tech support, not my work.

This should resolve your problem. It happened to me after a graphics card driver update.

for info: I run a i9-9900 @ 3.10GHz, RTX 2060 Super and 32 Gig ram. FPS between 100 - 145 depending on map, trees etc.

[Wow!]

Originally posted by OC Crinkly:

Go to:
C:\Users\USERNAME\AppData\Local\HLL\Saved\Config\WindowsNoEditor
Then open the file called : GameUserSettings (.ini )
Once the file is open you will have a window popping up there you need to find the line with :
Frameratelimit : 60.0000
And change 60 to 0 for unlimited cap or use your screen Hz ( 60-120-144-240 etc ) for it to match your screen frame.

This is from HLL discord tech support, not my work.

This should resolve your problem. It happened to me after a graphics card driver update.

for info: I run a i9-9900 @ 3.10GHz, RTX 2060 Super and 32 Gig ram. FPS between 100 - 145 depending on map, trees etc.

I thought the .ini was changed to be read-only a few updates ago(?). Trying now.

[Crinkly]

Originally posted by Q:

Originally posted by OC Crinkly:

Go to:
C:\Users\USERNAME\AppData\Local\HLL\Saved\Config\WindowsNoEditor
Then open the file called : GameUserSettings (.ini )
Once the file is open you will have a window popping up there you need to find the line with :
Frameratelimit : 60.0000
And change 60 to 0 for unlimited cap or use your screen Hz ( 60-120-144-240 etc ) for it to match your screen frame.

This is from HLL discord tech support, not my work.

This should resolve your problem. It happened to me after a graphics card driver update.

for info: I run a i9-9900 @ 3.10GHz, RTX 2060 Super and 32 Gig ram. FPS between 100 - 145 depending on map, trees etc.

I thought the .ini was changed to be read-only a few updates ago(?). Trying now.

I believe changes were made to some sections. eg: the ability to prevent wheat fields from rendering.

[TWB*Clell_Miller]

Originally posted by Q:

Originally posted by TWB*Clell_Miller:

Let me check.... (checking...) Server list coming up at 110 FPS. I hear that's a typically a stress point.

What do you mean? My fps in other games is still normal.

I believe you. So what does this reported outcome suggest to you on the surface? I can't tell you how many times I've heard "But I can run other games just fine." If you want to identify the source of a problem, you follow it home. I can run HLL rather well. So can many other folks. Many cannot. Let's list some accepted facts;
1. Many assert HLL is poorly optimised. It certainly is --for some.
2. Many have hardware that can run HLL very well.
3. Many have hardware that can't run it worth squat. And they don't hesitate to admit it.
The prevailing howl is this: "HLL developers have the responsibility to make the game run on most computers at THEIR expense." Do they? Can they? Do they even have the time or money to do so before this product is eclipsed by another product? Perhaps a later version even more demanding. As Noah said to God: "Do I really have to do this?" And God asked: "How long do you want to tread water?"
Now... if this is a situation that anyone is in earnest to correct, what is likely to resolve the problem at the earliest possible moment? I'm not going to coax anyone. Answer it to yourself quietly.

[Wow!]

Originally posted by TWB*Clell_Miller:

Originally posted by Q:

What do you mean? My fps in other games is still normal.

I believe you. So what does this reported outcome suggest to you on the surface? I can't tell you how many times I've heard "But I can run other games just fine." If you want to identify the source of a problem, you follow it home. I can run HLL rather well. So can many other folks. Many cannot. Let's list some accepted facts;
1. Many assert HLL is poorly optimised. It certainly is --for some.
2. Many have hardware that can run HLL very well.
3. Many have hardware that can't run it worth squat. And they don't hesitate to admit it.
The prevailing howl is this: "HLL developers have the responsibility to make the game run on most computers at THEIR expense." Do they? Can they? Do they even have the time or money to do so before this product is eclipsed by another product? Perhaps a later version even more demanding. As Noah said to God: "Do I really have to do this?" And God asked: "How long do you want to tread water?"
Now... if this is a situation that anyone is in earnest to correct, what is likely to resolve the problem at the earliest possible moment? I'm not going to coax anyone. Answer it to yourself quietly.

Solved - I edited the .ini - it was set to "60.000" in the fps field. Changed it to 120 and now my performance is back to normal. So weird. I was under the impression they had locked .ini edits in a previous patch. Something reset mine to a locked 60.

[Wow!]

Originally posted by OC Crinkly:

Originally posted by Q:

I thought the .ini was changed to be read-only a few updates ago(?). Trying now.

I believe changes were made to some sections. eg: the ability to prevent wheat fields from rendering.

I edited the .ini and it fixed it! Thanks man. :D

[Pork Loin]

This seems to be linked to how you exit the PTE as a lot of similar issues mentioned on Discord around this.

Message from Jambax confirmed as below.

Alright, figured it out. We lock the framerate to 60 in the menu in PTE - then unlock again once you join a game. If you played the PTE and don't separate the config files, the unlock would never take place in the base game, so the original game would be left locked to 60. Essentially, if you leave the PTE via the main menu it'll leave the lock active in the base game.

[TWB*Clell_Miller]

I didn't realize the .ini was accessible. Good research. I looked at mine. it is set to 0.0, so I assume no attempt is being made at any limiting. Good to know.