F.E.A.R. - FPS / Logitech fix

05-22-2010, 02:39 PM

Since I have seen so many posts about it and people still asking, this is for the answer.

This is a known compatibility issue with the original F.E.A.R. engine and Logitech G series keyboards and mice, with an emphasis on the former.

This is caused by the engine incorrectly overpolling the USB I/O in Windows. This is mainly apparent in all versions of Windows 7.
Logitech is not at fault - there are some apparent flamers here - which is why Logitech products work with a literal 99% of games.

TO FIX

Simply go into the Start menu and right-click "Computer", choose "Manage".

From there, go to "Device Manager" and choose "Human Interface Devices".

To get the best performance, you are going to want to disable all "HID-Compliant Device", you should not need to disable ANYTHING else.

Note: for the most part, these are used for the interfaces on the keyboards, which is why there is anywhere from 3-7, any applets will be disabled until these HID devices are re-enabled.

Interestingly enough, this issue is also persistent in Condemned: Criminal Origins, since it uses the same engine - Lithtech Jupiter EX - this "fix" also works.

The_Thing · 05-22-2010, 03:03 PM

Someone should sticky this thread. Great job!

zemzamzeman · 05-22-2010, 03:21 PM

This fix works just fine for me. I had the same issue.

I am on Windows 7 Enterprise. Logitech G19 MB + G500 Mouse. I had horrible lagtastic framerate. After using the fix listed above, everything was smooth.

Thanks again.

JK_DC · 05-22-2010, 03:28 PM

/rant

I have 13 entries to disable because someone is too lazy to spend 1 hour editing the polling rate to a lower value. So the whole world gets to waste 1000's of hours, even though they patched it 8 times and never bothered to fix this little issue.

/rant

MenaceInc · 05-22-2010, 08:41 PM

Thankfully (in respect to this issue) I've only a G500 mouse but I found that it was the devices listed that controlled my left scroll, right scroll and middle thumb button.

Just a note as well, it has to be a HID-compliant device with 046D in their hardware ID. You can find this by right-clicking --> properties --> details --> Hardware IDs.

I tried everything in the SetPoint software (which isn't run normally) to set these buttons to unassigned or disabled but after testing various combinations, none of them worked. Only disabling them in device manager had any effect.

zemzamzeman · 05-22-2010, 11:26 PM

I understand everyone's frustration.

I would love to say that they should just patch this, but the developer for this game went out of business years ago. The current publisher owns the rights to the game, but does not have the ability or the desire to try and patch it. What we have is what we get. At least, that is what I have been told.

I guess the good news is that it is such an amazing game, these little oddites can be overlooked now that there is a fix (of sorts) for the problem.

Mr_Fayce · 05-22-2010, 11:49 PM

Thanks for the fix.

Should be sticked.

playerboy8 · 05-23-2010, 01:52 AM

Mah boi, you just got rep!(i mean OP, not guy above)

MenaceInc · 05-23-2010, 07:10 AM

Quote:

Originally Posted by zemzamzeman

I understand everyone's frustration.

I would love to say that they should just patch this, but the developer for this game went out of business years ago. The current publisher owns the rights to the game, but does not have the ability or the desire to try and patch it. What we have is what we get. At least, that is what I have been told.

I guess the good news is that it is such an amazing game, these little oddites can be overlooked now that there is a fix (of sorts) for the problem.

I'm sure the 100+ employees who work for Monolith ( http://www.lith.com/ ) would hate to hear that they've been working at an out-of-business studio for years. o.0

Fact is though that there was a mess between Logitech and Monolith between the way the Jupiter EX engine polls the USB bus so much and Logitech having weird drivers which resulted in bruised egos and still years later, no one wants to own up to the issue.

WB could tell Monolith to fix it but it's doubtful they will.

05-23-2010, 07:18 AM

I don't suppose anyone knows if the problem applies to logitech keyboards that are PS/2, from what I read on wikipedia the PS/2 keyboards and mice don't support HID and so shouldn't even be using it...

Does this problem, and the fix, apply to PS/2 devices?

MenaceInc · 05-23-2010, 07:20 AM

Quote:

Originally Posted by xylent

I don't suppose anyone knows if the problem applies to logitech keyboards that are PS/2, from what I read on wikipedia the PS/2 keyboards and mice don't support HID and so shouldn't even be using it...

Does this problem, and the fix, apply to PS/2 devices?

You shouldn't have any issues with any PS/2 equipment, it's limited to how the game uses the USB ports.

mesaone · 05-23-2010, 09:16 AM

so, considering the g9 and g9x mice (i have the g9) have an adjustable polling rate, would it work if the polling rate was set to a low value?

Circlestrafe · 05-23-2010, 09:41 AM

I have the G500 with Setpoint v5.20.40 @ report rate of 500, Windows 7 x64 Professional and no framerate issues whatsoever. I do not have a Logitech keyboard, but the Saitek Eclipse. Perhaps the issue is related only to the Logitech Gxx keyboards, or those with polling rates of 1000 on their mouse?

Painseeker · 05-23-2010, 09:56 AM

G9 and G19, used this fix yesterday and went from 12fps on lowest to 100+fps on max

FulValBot (ITA) · 05-23-2010, 10:30 AM

we need a real fix for this bug... if you disable these components you disable also some features on setpoint... check it...

05-22-2010, 02:39 PM	#1
Fatt-Slice Guest Posts: n/a	F.E.A.R. - FPS / Logitech fix Since I have seen so many posts about it and people still asking, this is for the answer. This is a known compatibility issue with the original F.E.A.R. engine and Logitech G series keyboards and mice, with an emphasis on the former. This is caused by the engine incorrectly overpolling the USB I/O in Windows. This is mainly apparent in all versions of Windows 7. Logitech is not at fault - there are some apparent flamers here - which is why Logitech products work with a literal 99% of games. TO FIX Simply go into the Start menu and right-click "Computer", choose "Manage". From there, go to "Device Manager" and choose "Human Interface Devices". To get the best performance, you are going to want to disable all "HID-Compliant Device", you should not need to disable ANYTHING else. Note: for the most part, these are used for the interfaces on the keyboards, which is why there is anywhere from 3-7, any applets will be disabled until these HID devices are re-enabled. Interestingly enough, this issue is also persistent in Condemned: Criminal Origins, since it uses the same engine - Lithtech Jupiter EX - this "fix" also works. Last edited by Fatt-Slice: 12-20-2010 at 03:45 PM.

05-22-2010, 03:28 PM	#4
JK_DC Join Date: Jan 2009 Reputation: 193 Posts: 2,209	/rant I have 13 entries to disable because someone is too lazy to spend 1 hour editing the polling rate to a lower value. So the whole world gets to waste 1000's of hours, even though they patched it 8 times and never bothered to fix this little issue. /rant Last edited by JK_DC: 05-22-2010 at 03:31 PM.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

05-22-2010, 03:03 PM	#2
The_Thing Join Date: Nov 2008 Reputation: 325 Posts: 2,539	Someone should sticky this thread. Great job!

05-22-2010, 03:21 PM	#3
zemzamzeman Join Date: Oct 2009 Reputation: 9 Posts: 70	This fix works just fine for me. I had the same issue. I am on Windows 7 Enterprise. Logitech G19 MB + G500 Mouse. I had horrible lagtastic framerate. After using the fix listed above, everything was smooth. Thanks again.

05-22-2010, 08:41 PM	#5
MenaceInc Join Date: Sep 2009 Reputation: 1461 Posts: 851	Thankfully (in respect to this issue) I've only a G500 mouse but I found that it was the devices listed that controlled my left scroll, right scroll and middle thumb button. Just a note as well, it has to be a HID-compliant device with 046D in their hardware ID. You can find this by right-clicking --> properties --> details --> Hardware IDs. I tried everything in the SetPoint software (which isn't run normally) to set these buttons to unassigned or disabled but after testing various combinations, none of them worked. Only disabling them in device manager had any effect.

05-22-2010, 11:26 PM	#6
zemzamzeman Join Date: Oct 2009 Reputation: 9 Posts: 70	I understand everyone's frustration. I would love to say that they should just patch this, but the developer for this game went out of business years ago. The current publisher owns the rights to the game, but does not have the ability or the desire to try and patch it. What we have is what we get. At least, that is what I have been told. I guess the good news is that it is such an amazing game, these little oddites can be overlooked now that there is a fix (of sorts) for the problem.

05-22-2010, 11:49 PM	#7
Mr_Fayce Join Date: Sep 2009 Reputation: 97 Posts: 1,293	Thanks for the fix. Should be sticked.

05-23-2010, 01:52 AM	#8
playerboy8 Banned Join Date: Jan 2010 Reputation: 6 Posts: 50	Mah boi, you just got rep!(i mean OP, not guy above)

05-23-2010, 07:18 AM	#10
xylent Guest Posts: n/a	I don't suppose anyone knows if the problem applies to logitech keyboards that are PS/2, from what I read on wikipedia the PS/2 keyboards and mice don't support HID and so shouldn't even be using it... Does this problem, and the fix, apply to PS/2 devices?

05-23-2010, 09:16 AM	#12
mesaone Join Date: Mar 2009 Reputation: 120 Posts: 1,010	so, considering the g9 and g9x mice (i have the g9) have an adjustable polling rate, would it work if the polling rate was set to a low value?

05-23-2010, 09:41 AM	#13
Circlestrafe Join Date: Sep 2006 Reputation: 87 Posts: 852	I have the G500 with Setpoint v5.20.40 @ report rate of 500, Windows 7 x64 Professional and no framerate issues whatsoever. I do not have a Logitech keyboard, but the Saitek Eclipse. Perhaps the issue is related only to the Logitech Gxx keyboards, or those with polling rates of 1000 on their mouse?

05-23-2010, 09:56 AM	#14
Painseeker Join Date: Feb 2010 Reputation: 0 Posts: 53	G9 and G19, used this fix yesterday and went from 12fps on lowest to 100+fps on max

05-23-2010, 10:30 AM	#15
FulValBot (ITA) Join Date: Oct 2007 Reputation: 98 Posts: 2,528	we need a real fix for this bug... if you disable these components you disable also some features on setpoint... check it...