TinyLittleTimmy wrote:
ovenbakedmuffin, after testing myself online using my PC I bridged both my xBox and my PS3 through my PC, used a gaming router, a ddwrt, and regular home, wireless and wired, changed mtus,shrank buffers to stop buffer bloat, open, fowarded, triggered, and dmz'd both consoles, set their ips to high priority, used a full duplex gigabit only settings and changed my nics to preferences of high ping small packets instead of large downloads...
A large collection of tasks. As this is a software problem, none of that is necessary, which you have likely realized. Simplicity is often our greatest asset.
TinyLittleTimmy wrote:
...
ulimately it is easy to manipulate lag compensation with NetBalancer, you can add delay to both incoming and outgoing packets as well as throttle speeds (and change dropped packets percentage for both very easily)...
I'll have to look at that. It would be great for the individuals constantly asking me for a Windows-based utility.
TinyLittleTimmy wrote:
...
Unfortunately no matter how much lag comp I gave myself nothing helped (not even 500ms delay with 20% incoming packet loss) all it did was make my bullets effect be delayed by 500ms.
The best help was lowing my ping ...
That's precisely how it should behave for BO2.
I should clarify; you should have a sight advantage of [500ms] as well as a damage delay of [500ms], negating any advantage at this stage. As Treyarch has 'compensated' for actions, but not reactions, you have the advantage over a player who has not moved from cover - regardless of your ping. However, the lower the other player's ping, the less of a disadvantage they will have. As you are bound to find yourself in that situation regularly, lowering your ping reduces your disadvantage.
TinyLittleTimmy wrote:
...
BUT ONE MAJOR PROBLEM REMAINED: THE POV DELAY AND/OR CAMERA POSITION YOU ILLUSTRATED IN THE VIDEO.
The best example I saw in Black Ops 2 was on Raid domination. ...
I hit dead on but all my bullets missed going above their head despite the fact I aimed lower as I shot. Then poof was dead and never got to see their body much less their gun, the only thing that shows on stairs is the hair on the top of their head, Yet on the replay they could see my entire body and their rifle and upper body were completely exposed, plus all my bullets hit the ground rather that go over their head SO THIS IS DEFINATELY A POV ISSUE. Nothing to do with the lag comp nor host issues we had in MW3.
...
FOV/POV/Camera position has nothing to do with the delays shown in my video, nor the others I have watched. In my testing, I painstakingly lined up my run angle to avoid any interaction with camera issues. If there were any, it was on the order of 1~2 frames. Proof against camera-related delay lies with the equal sight advantage / damage disadvantage. If you run around a corner and fire your weapon at a player, you will see the player early and damage the player late by an equal amount (unless latency has changed in the meantime). If it were a camera issue, you would see and damage the player early, or you would not hit the player at all (host determines if your bullets should hit the player). This would have lead to a very different situation, where players could kill one another without being seen at all. I would have published that in my video if it existed; I wouldn't have had to work so hard to get to the truth.
Killcams will not be what you see in the game unless you are the host, and theater will not even show the same results if you are the host. Neither of them should be used as examples if at all possible.
If referring to theater mode as "the replay", the displayed positions are smoothed and often wrong. It's fine for recording your gameplays for YouTube if you don't have a capturecard, but not for purposes of comparison.
Finally, yes there are issues with the camera which are completely unrelated to the networking issues I have discussed in my video. Headglitching is the most apparent of such. What you likely experienced is, in fact, headglitching. While you could only see the very top of the opponent's head, they could see you unhindered. Lowering the camera position would fix ADS-glitching, and raycasting twice - one to point of impact, another between weapon and point of impact - would arrest hip-glitching. A final adjustment would need to be made to collision detection, as it is currently possible to clip your weapon through a wall and fire out of it.
It is extremely important to separate networking and camera issues. While they each have significant and obvious effects on gameplay, their origins are entirely unique - as well as their implications.
Perhaps most important of all, we cannot allow staff/others to blame our experience of lag on completely unrelated issues. It was done in BO1 where all lag was blamed on theater mode, and the effects of that still follow us to this day.
As a follow-up to my previous post, you can expect a short video within the week. I have the footage necessary, but it may take some time to do the editing as I am working long hours.
