Snkfanatic
Banned
Be happy you're not sensitive to it. Some people don't notice or aren't bothered by low fps, tearing, etc. Doesn't mean those things don't exist.
Don't think I said anything about OP's issues not being legitimate but ok.
Be happy you're not sensitive to it. Some people don't notice or aren't bothered by low fps, tearing, etc. Doesn't mean those things don't exist.
Noticed it when I reviewed the game. I pretty much ran through the combat sections just to get through them. The input lag was dreadful, worse than the first game. Rockstar or Epic Games needs to show every developer how to do third person shooting controls ha.
This is what completely ruined the experience for me, and why I stopped playing until I am able to pick it up on PC later this month.
Not trying to start shit or anything, but anyone think it's due to the hardware limitations of the xb1? Curious to see what it's like on the ps4 later this year...
This title is misleading. You're not talking about the combat, you're talking about the input lag that effects the XBO version of the game only.
Doubt it's hardware limitations, since the 360 version controls perfectly with almost no lag.
I don't recall shooting at any waste or dumpsters
The fact that you experience this with Halo is strange. What tv are you using?I picked up RotTR from my library this weekend and I noticed that the camera controls felt a bit off. I said, okay, it shouldn't be a big deal, given that it's a single player game.
But holy shit wtf. The sluggish camera controls are totally garbage for the combat in this game. I can't aim quickly and precisely in this game while I can in basically every other game (in either 30 or 60 FPS). There seems to be some sort of delay or a huge deadzone on the right stick causing input delay or something similar (because of bad Vsync?) How can I aim people in the head when I have to deal with unresponsive camera controls? WTF, the game is pretty awesome with the tombs and the explorations, but when it comes to combat...it's awful because of the camera. This reminds me of playing CSGO with a controller along with really bad VSync.
I had a similar problem in Halo 5 but that was basically alleviated when they added an option to reduce the massive inner dead zones. I have had no problems with any other games I've played recently or in the past. The responsiveness on the last Tomb Raider on PC was incredible.
Has anyone else noticed this? How is this not a bigger issue given the combat is somewhat a large component of the game?
The fact that you experience this with Halo is strange. What tv are you using?
The issue in Halo 5 was nowhere as extreme as it is in RotTR but I felt a very small delay that didn't help my aim at all. Reducing the deadzones helped a bunch. I didn't have a problem with any other Halo game. Idk what model my TV is but I have a Sony TV from 2009.
Dont forget Killzone devs, they seem to like input lag and heavy controls as well.
I just cant enjoy games that do this, even GTA 5 I could not stomach for that long
Was this problem in the first game?
I find it really irritating how some post "Fix your tv" I'd like to think most of us here on GAF are fully aware about modern TV's and how to calibrate. Myself included.
Mine are and it's bad on both of my TV's, sucks to be sensitive to this in games tbh.
hmm, if I reall correctly 2008 sony tvs were exceptionally good for input lag.... but I think they drastically reversed that trend in 2009 which were pretty bad for games. In any case, if you don't have problems in other games perhaps it's something else. Use 'Game' or 'Pc' mode if the tv has it, that may help.
Input lag is a real thing. On 360 its not there though, or extremely reduced. Hopefully the PC an PS4 ports don't suffer from it(which i doubt cause its Nixxes da gawd)
Okay.
vs
so i went ahead and tried the demo....
....and i honestly thought it was fine. Seriously, it was more or less in line with how 2013 XB1 version felt. A little heavy but fine if youre not expecting this to be Uncharted @ 60fps or Titanfall
so yeah, im actually gonna take back what i said and pick this up now
I played the demo and I couldn't believe how poorly the game controlled. There's a delay on everything and Lara feels so unwieldy because of it. I don't understand how people are looking past it.
Your video shows ~200ms input lag. That's a LOT. Most 30FPS games are around 130 at most, and around 100 if developer knows what they're doing. 60FPS games are almost always below 100ms. It's bad enough already on your TV but consider that for some people it will only be worse if they have TV with more lag than you.If I slow down Titanfall it does that, or any game, there is always input lag of some sort, consoles don't poll the controller at 0 ms and TVs and monitors don't operate at 0 MS.
This kind of thing is usually deep rooted in the intertwining of rendering pipeline and game logic. It's unlikely it can just be patched. More than likely they have to rethink / rewrite the way their engine works.The only way to play through this game in harder dificulty levels is with shotguns and explosive/poison arrows. The input lag is real and is a shame that CD does not fix it yet
Input lag is never a design choice. It's always bourne out of bad technical design or limitations.I really have to wonder whether this was done on purpose or not.
Okay.
vs
So they removed it on 360 on purpose too because Lara's body is lighter in this version.I really have to wonder whether this was done on purpose or not. I mean, Lara used to have a heavier, less floaty feel to her back in the day (which is something many people nowadays make fun of but many fans of the series actually appreciate and hugely prefer over the floaty controls of, say, Legend) so if the input lag affects everything, not just the camera controls it could be Crystal's attempt at returning some weight to Lara's controls. However, the 360 version not having the input lag would suggest that it's not intentional.
Hopefully.Huh. Maybe this issue will be fixed on the PS4 version?
Input lag is never a design choice. It's always bourne out of bad technical design or limitations.
This kind of thing is usually deep rooted in the intertwining of rendering pipeline and game logic. It's unlikely it can just be patched. More than likely they have to rethink / rewrite the way their engine works.
Xenoblade X is not a shooter, so, is not a big deal...YOU!
Please do this with Xenoblade Chronicles X (if you have it). Because I KNOW that game has some of the worst input lag I've ever felt and not a single damn reviewer brought it up at all. It can't just be me.
No. Input lag is fucking horrible no matter what game you're playing.Xenoblade X is not a shooter, so, is not a big deal...
No. Input lag is fucking horrible no matter what game you're playing.
Agree with you, but is not the same, you can deal with a input lag on a action rpg like XCX, but no in a shooter like TR or something like COD, or a racing game.No. Input lag is fucking horrible no matter what game you're playing.
True, it's less debilitating, but it still irks the shit out of me. I can't even handle it in classic JRPGs.Agree with you, but is not the same, you can deal with a input lag on a action rpg like XCX, but no in a shooter like TR or something like COD, or a racing game.
It was called out by Digital Foundry. The game has very large input lag. Somewhat humoroursly, the X360 version of the game has much less input lag than XB1 version does.
I had no idea this was a known problem with this game. I recently completed TRE and was excited to buy this very soon for my XB1. I still will and hopefully it won't bother me like it does some others.
YOU!
Please do this with Xenoblade Chronicles X (if you have it). Because I KNOW that game has some of the worst input lag I've ever felt and not a single damn reviewer brought it up at all. It can't just be me.
Just curious (for estimating timings): was the Splatoon footage captured at 30 FPS or 60 FPS?