• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Input Lag Simulation

Joined
Jun 8, 2008
Messages
26
Input Lag is a greatly discussed thing on these forums, and no doubt on many others like it.

Some people seem to be totally insensitive to it, unable to detect even the slightest latency when using for example, the Dell 2408WFP, one of the highest lagging monitors in existence.

On the other end of the scale, there are people like me, who are extremely sensitive to it. Even when navigating an interface with a mouse pointer, I can detect the input latency.

Unfortunately, I had to discover my inability to cope with lag the hard way. I purchased a 2408 without comprehending how bad the lag could be. I had to return the monitor to the website I had purchased it from, causing a large amount of stress, not to mention shipping costs.

I tell you all of this because I had an idea which could help pretty much every prospective display purchaser gauge their sensitivity to input lag.

Essentially, if somebody were to develop a simple tool which simulated the effects of input lag on various actions, such as pointer movement, clicking, etc.

This tool would obviously need the ability for lag adjustments, so users could accurately simulate the latency on a monitor they are interested in purchasing.

Unfortunately, I have little to no programming knowledge. But I am convinced that with the right people, the development of such a tool is by no means an impossible task.

If anybody has any ideas on how this could be executed, I'm sure it could be extremely helpful to many purchasers.

All the best,

Joe
 
Congratulations on totally missing the entire point of the post. My idea would allow people to see how much input lag they can cope with...
 
That's very useful Silverglider, certainly a basis for something more advanced. Firstly, standard flash lag may be adding a small amount of the lag to the mouse movement. Secondly, it assumes you are working on a zero lagging display for it to work.

I was thinking something that perhaps detected what display you are currently using, and adjusted the figures accordingly. But that flash app is certainly very useful, thanks.
 
I can't handle input lag. So far I've returned two 2408WFP's, and a Sammy 275T. Then I got a BenQ FP241, which had great input lag. But it was too small for me, and I returned it. I am in the process of getting a 3007WFP or W3000H, which both have very low input lag.
 
Congratulations on totally missing the entire point of the post. My idea would allow people to see how much input lag they can cope with...

Well, my point is that you came with the idea becuase of your very bad experience with a very bad monitor. That's like creating a "frustration simulator" for people used to shop in a grocery with very rude and slow shop assistants :)
What about backlight bleeding simulator? Or colour shift simulator? ;)
 
@OP

I've been thinking exactly the same thing since my recent experience with a 2408 a00. It should be possible to write a keyboard and / or mouse driver that delay input for a short period of time and hence simulate lag for the whole system. Unfortunately I don't have the documentation, tools or time to investigate this. I do however have a Logitech G15, new revision, and put together the following script to simulate input lag on the WSAD keys for use in games.

Code:
function OnEvent(event, arg)
	OutputLogMessage("event = %s, arg = %s\n", event, arg)

    if (event == "G_PRESSED") then
        Sleep(60)
        if( arg == 1 ) then -- G1 key
            PressKey("w")
        end

        if( arg == 2 ) then -- G2 key
            PressKey("a")
        end

        if( arg == 3 ) then -- G3 key
            PressKey("d")
        end

        if( arg == 4 ) then -- G4 key
            PressKey("s")
        end
    end

    if (event == "G_RELEASED") then
        Sleep(60)
        if( arg == 1 ) then -- G1 key
            ReleaseKey("w")
        end

        if( arg == 2 ) then -- G2 key
            ReleaseKey("a")
        end

        if( arg == 3 ) then -- G3 key
            ReleaseKey("d")
        end

        if( arg == 4 ) then -- G4 key
            ReleaseKey("s")
        end
    end

end

The two Sleep(60) lines add a 2408ish 60ms delay to key press and key release, I'm on a CRT btw. Change the 60 in both places to the required lag value.

The key mappings are quite obvious:
G1 = W, G2 =A, G3=D, G4=S
One for PressKey and one for ReleaseKey, should anyone wish to change them.

In use it does indeed give the floaty feeling I remember from the 2408, if anything the 2408 felt even more sluggish.

Of course you're out of luck if you don't have a Gxx, but it may be of use to some.
 
Back
Top