Input lag

Well you maintain that bumper cam doesn't lag.

Thing is i see lag in bumper, and i play on the same screen that i play PC sims on and there is no noticeable lag on PC.

Ok, you should have said that earlier. Fair enough. It's good enough for me in the bumper view. I guess you just have better senses than me ;)


Well no. I use DVI for pc and HDMI for PS3

ah, and there is the cable thing interfering too, I see...
 
Forget the steeringwheel in cockpit, that is just EFFED UP
I'm more bothered about the actual car responding in sync

Real cars have a slight delay in response anyway. The wheels and suspension are relatively "soft" even in a race car, so there'll be a slight delay.

Have you got any proof that the lag in GT5/GT5P is more than the mechanical lag in a real car anyway? ;)

Personally if the virtual wheel had the option to be turned off, I'd turn it off (unless there were gauges on the wheel I wanted to see while racing).
 
And what tells you that the lag is not introduced by using different inputs? Wouldn't be the first time...

I have also used VGA, and it is just as responsive.

Regardless, following this logic we can come to the conclusion that HDMI does not provide quick enough connection for PS3, but that would be crap because i have a £150 Monster cable that has over 14GBP/S speed
 
Ok, i tried it with my PS3 with GT5p and my PC with GTR Evolution and they are both connected to the same Samsung FullHD TV and i dont see any lag between controller(Dualshock3)/wheel(Logitech G25) input and reaction on the wheel. All i can definately see is a lag between wheel input and wheel turning in cockpit view, but the tiremovemend seems to be instant.

I have all the enhencements my TV offers disabled, the PS3 is connected via HDMI and the PC is connected via DVI cable. For the DVI connection my TV offers a special PC mode, but that does not seem to change anything. The Ps3 is connected to HDMI port 2, which is recommended for videogamingdevices, but i dont exactly know why.

For me there is no inputlag, just some latency in the reaction of the hands and the wheel in cockpit view. The faster you move the G25s wheel the more obvious this effect gets.
At GTR Evolution i messed arround with the settings for the wheel but it still feels awkeward. The reaction is definately instant, but the ff and the movement seems awkeward, though there is no lag.
 
Why do all you people fail to see the whole screen is lagging, not just the animations.
Also mechanical lag/inertia would not be as slow as what i am seeing on screen. PC sims from a physics standpoint are ahead of GT5P and guess what, they do not have lag, even with more advanced physics parameters than GT5.
 
This thread is pointless.

Bitch about lag in TVs but....there's nothing we can do about it and I for one, have never noticed it. And I'm a competitive player.

End of.
 
Just comment on people that are saying panel response times (6ms 2ms) and talking about input lag. Panel response time has nothing to with input lag. Panel response time means how much panel takes to draw next picture compared to last one. Input lag means how long it takes from picture signal from cord to display on screen. Input lag is caused by processing image. TV with 200ms input lag can display movies and tv very well but panel with 200ms response time just wont manage to display anything right. 200ms input lag tv does not work for games despite having super fast 2ms panel response.
sub 30ms input lag is good for most games.
 
This thread is pointless.

Bitch about lag in TVs but....there's nothing we can do about it and I for one, have never noticed it. And I'm a competitive player.

End of.

I noticed it, and my Dad noticed it instantly the first time i told him to have a go. I guess some people are just more perceptive than others.
I know if i was on a PC forum, i would get a much better level of respect.
PC gamers view things logically from an unbiassed/ Non fanboy perspective and generally from what it seems have a much higher IQ from what i have experienced.
 
dan, the act of the matter is that ive seen videos where steering wheel to videogame response is perfect, no lag.... and some ive seen where there is, This is not affected by the PS3

Its a HARDWARE problem... TV or wheel your using.
 
dan, the act of the matter is that ive seen videos where steering wheel to videogame response is perfect, no lag.... and some ive seen where there is, This is not affected by the PS3

Its a HARDWARE problem... TV or wheel your using.

Well that already goes against my oppinion and also the oppinion of the others.
I think the lag is the whole display
And the others think it is the animations

but most people admit the wheel in game appears to lag on screen.

Please show me one of these in sync videos.

I bet it is not
 
Why do all you people fail to see the whole screen is lagging, not just the animations.
Also mechanical lag/inertia would not be as slow as what i am seeing on screen. PC sims from a physics standpoint are ahead of GT5P and guess what, they do not have lag, even with more advanced physics parameters than GT5.

I can see the screen is lagging ;) personally I notice the lag in PC sim virtual wheels also. However there is also a delay in tire/suspension response too, how do you know the visual lag you see isn't less than the mechanical lag anyway? I just did a test in LFS and I can whip the wheel back and forth quickly and the car itself will be moving left while my wheel is pointing right because the tires haven't had time to respond to the input and translate it to a chassis movement.

Input lag from the PS3 may add to this, I'm not sure, dont own one to test :P but you eyes will often pick up on a visual delay and ignore the mechanical delay that's present in real cars.
 
I can see the screen is lagging ;) personally I notice the lag in PC sim virtual wheels also. However there is also a delay in tire/suspension response too, how do you know the visual lag you see isn't less than the mechanical lag anyway? I just did a test in LFS and I can whip the wheel back and forth quickly and the car itself will be moving left while my wheel is pointing right because the tires haven't had time to respond to the input and translate it to a chassis movement.

Input lag from the PS3 may add to this, I'm not sure, dont own one to test :P but you eyes will often pick up on a visual delay and ignore the mechanical delay that's present in real cars.

Yes but that is because the car was going one way and you quickly tried to make it go the other, there is much more inertia involved there.
A better way would be to just go straight and wip the wheel.
 
Yes but that is because the car was going one way and you quickly tried to make it go the other, there is much more inertia involved there.
A better way would be to just go straight and wip the wheel.

I'm pretty sure there's a delay there too ;) But I dont have screen capture software to save it nor do I have anywhere to upload it (and dont want to bother setting it up :P).
 
I give up, all i have to say is look at this other thread where the majority disagreed with me and look who turned out to be right:sly:

https://www.gtplanet.net/forum/showthread.php?t=119286

I also seem to remember you going around saying that it was actually GT5P that was playable and not GT5. Who was right there?

And besides, past confirmation of an opinion doesn't mean every single thing you sprout from then on is rock solid truth.
 
I have also used VGA, and it is just as responsive.

Regardless, following this logic we can come to the conclusion that HDMI does not provide quick enough connection for PS3, but that would be crap because i have a £150 Monster cable that has over 14GBP/S speed
No. Cable speed has nothing to do with that, as opposed to this:
Just comment on people that are saying panel response times (6ms 2ms) and talking about input lag. Panel response time has nothing to with input lag. Panel response time means how much panel takes to draw next picture compared to last one. Input lag means how long it takes from picture signal from cord to display on screen. Input lag is caused by processing image. TV with 200ms input lag can display movies and tv very well but panel with 200ms response time just wont manage to display anything right. 200ms input lag tv does not work for games despite having super fast 2ms panel response. Sub 30ms input lag is good for most games.
I have seen many tvs that handle their inputs differently, thus my initial question.

Also, on a personal note, I might add that I feel a lot of the "head wind" you are facing in this thread is generated by your attitude - just a friendly hint...
 
1. The final game hasnt hit the streests yet, so you dont know if theres lag or not.
2. The stuff you seen, is not anything usefull for a comparison, you need see it on your own tv, with own SW etc before you can judge it.
3 - Go play a pc sim if the issue is too big? If pc sims is the best, i dont see the point in making such a big fuss about a console game. Just go for the pc, problem solved :S

I havent ran into any problems in gt5p, and doubt ill run into any major ones when gt5 hit the streets in 2015 or when they release it :P So i cant wait :)
 
I agree with you on the lag part, but I'm saying I notice lag in PC sims also, but the only real effect it has on me is visually, which is one of the reasons why I turn off the virtual wheel in PC sims. As far as "feeling" the car is concerned, I dont notice it.

No of course, you are correct, because FFB DOESN'T REALLY LAG BUT THE IMAGE ON SCREEN DOES,

This is what i havebeen saying all along, why do i have to go round and round in circles.

The point you mention is the point i am getting at.
That FFB AND SCREEN ARE NOT IN SYNC
 
And besides, past confirmation of an opinion doesn't mean every single thing you sprout from then on is rock solid truth.

No, but i view things logically and provide evidence to back myself up, i don't just post because i belive something before i have even experienced it.
No one saw my logic in that thread except me, but i turned out right.
 
No, but i view things logically and provide evidence to back myself up, i don't just post because i belive something before i have even experienced it.
No one saw my logic in that thread except me, but i turned out right.

Part of posting and entering into an argument is to be willing to be proven wrong.

It's called pig-headedness. You might actually learn something.
 
Part of posting and entering into an argument is to be willing to be proven wrong.

It's called pig-headedness. You might actually learn something.

Yes but i wasn't

You go and enter conversations to be proved wrong all you want

I enter conversations to enliten people and also to ask any questions i may not have the answer to
 
Here's a thought that might be interesting. It could be possible that we just don't take the delay into account because it has always been that way. What I'm saying is, if we get a reaction from the wheel at a certain point on the track, we may just perceive it as being from that point on the track, when in reality it is 1000th of a second later. Just an idea, I don't know what to think of it myself.
 
Here's a thought that might be interesting. It could be possible that we just don't take the delay into account because it has always been that way. What I'm saying is, if we get a reaction from the wheel at a certain point on the track, we may just perceive it as being from that point on the track, when in reality it is 1000th of a second later. Just an idea, I don't know what to think of it myself.

You mean we learn to feel the track, and memorise it?
 
3840272644_e79e21edb2.jpg


I visualized it so I can explain what I'm thinking. Lets say the track has a bump. The bump may exists on the track at point 1, but we feel it at point 2. Therefor we perceive that the bump actually exists at point 2.

I don't know if this is right or wrong, I'm just throwing around ideas.
 
Yes i know but through out the whole thread, input lag has being reffering to the input to screen.

Why complicate matters?

I feel that I am simplifying it...

We are trying to find out where the lag occurs...

If we can narrow it down to
a) input (before GT5 knows about it)
b) processing (GT5)
c) output (after GT5 has finished)

Then we can see where the problem is.

C.
 

Latest Posts

Back