Cockpit Cam (There really is a visual lag problem)

  • Thread starter squeakD
  • 5 comments
  • 1,246 views
Folks.., this has been discussed before, and I have to say that after tonight I'm now a firm believer in that this is truly the main problem as it relates to lag in this title. (even after the last patch for the consoles)

I've been away from S2U for some time until recently. I dug back into it over the last few days doing some extensive tuning, and tweaking the controller settings.

I will say that some may not realize this.., but a large part of the poor handling in this title is also a result of very shi**y default controller settings (along with piss poor default vehicles set ups).

After HOURS of digging into this title again.., I have to say that much of what we perceive to be lag in this title isn't really the case at all (or at least the lag in steering that so many have been talking about). The lag is a VISUAL lag that is just down right disgraceful when using the cockpit view. The last patch did however tighten up the true steering lag issue.., but with that now being improved it really makes the VISUAL lag within the cockpit view stand out a lot more IMO.

The viewpoint that I race in 99% of the time with all of my racing titles is the cockpit view (if it's available). I do however consider myself to be proficient in both the typical hood cam and cockpit cam. I don't consider myself to be a pro driver.., but I do set fairly good lap times in my titles.., and in some of them making it within the top 5% on the leader-boards (and others ranging within the top 10-15 percent with my best times).

After doing some heavy tuning along with test drives and running actual races within the career mode.., I now have to agree with others who have reported that the cockpit cam has a Visual Delay.., and not a delay in the steering itself. If you really want to get a good idea of this.., and if you're a decent tuner.., I suggest you run several laps from cockpit cam and then switch to the hood cam.

The hood-cam isn't my favorite as I've been using cockpit cam for years with other titles. However.., I'll use it if I have to. I went back and started redoing races and tests with my tunes switching between the two cams and it was like night and day.

From the hood-cam the so called "Fast As Hell" AI wasn't so fast anymore. I was smoking them from the hood cam. The overall feel of the vehicle just felt better as well. The steering was responsive.., the suspension settings were noticeable.., ect. It was just an overall MUCH better driving experience from this cam.

I really would much rather use the cockpit cam (as this is ALL I used in Shift-1).., but after tonight (if I continue to play this title)..., I'm sticking to the hood cam because of this delay issue.

Some of you may agree with this or not.., but if you're on a console I really suggest you try this. ESPECIALLY if you're a game pad user! The reason I say that is because game pad users are even at a greater disadvantage as well because of the shotty and I mean downright shotty steering aids that have been coded for pad use. There is a HORRIBLE "auto correct" done to the steering when you're corning that at times actually can screw up your cornering. You then add in a Visual Delay in the cockpit cam to this and you're left with a frustrating mess.
 
I've been saying that-lag is only visual, not in input- for months(sorry but it is to late to dig old posts and quote myself).
But I play S2U with cockpit view from the start-I even enforced it in the beginning in some online races, but most people didn't like it- and I got pretty used to it and wouldn't trade the experience for a extra tenth...I think I do pretty well, competitiveness wise with it.;)
 
But lag is only visual isn't it. I mean I've not heard of non visual lag before.
I don't think I quite understand.

The xbox version is fine. So I am wary about future patches.
The latest patch screwed up the Force feedback for xbox users. I'm sure that was in the attempt to fix the PS3 version of lag.

A patch to fix PS3 lag would probably inadvertently add lag to xbox lol.

I could handle non visual lag though, I wouldnt notice it.
 
Folks, of course the lag manifests itself as visual. Whether you call it input lag, controller lag, visual lag, or what have you - it's the same thing. It's the time it takes from you move a controller until the frame that takes that input into consideration is being output. That creates a delay in the feedback loop. It doesn't matter what creates the delay, the effect is the same:

Code:
  +---------------------------------------------+
  |                                             |
  +--> human -> input -> processing -> output --+ 
                [...........delay...........]

The lag can potentially be different for different views, as rendering times may vary, and we know that S2U keeps a (varying?) pipeline of ready rendered frames to soak up peaks in rendering times. But at a guess, such differences due to the chosen view wouldn't be much; maybe one frame at most, if any at all.

DJ
--
 
Last edited:
I notice lag after about 3-6 scotch&waters. Is this normal? I am not sure how to patch it.
 
Back