Honestly yes I will to help out
>Series X
>acer predator CG
>wired controller
>Ethernet
>port forwarded/QoS enabled
>watermelon g fuel
>adderal XR
>Locked in @ 60FPS in 4K/1440p (🤡)
>YOUR BANDWIDTH/FPS HAS A HUGE IMPACT ON AIM ASSIST. LOWER FRAME(s) BEING DROPPED WILL THROW OFF AIM ASSIST/IE PACKETLOSS/NETCODE (128p on a 45hz server, SEND/RECIVE PACKETS once every 45/frame a second, that’s just not enough for 128p)
>Console Settings
>Stay away from the Overlays, Native 4K/HDR
>DO NOT RUN 12BIT COLOR.
>DO NOT RUN 12BIT COLOR.
>12BIT @4K IS NOT SUPPORTED THROUGH HDMI, it requires more data than your HDMI CABLE can transmit! (80% of the time) it automatically changes your FPS to 30.
To compensate. YCC 2:2:2 can fix that issue but, you’re just canceling it out because of the compression. YCC isn’t considered a overlay but will still negatively impact your performance. YCC should only be used for resolution priority.
>GO TO YOUTUBE and set yalls console up the right way for gaming. Or ask me. Input lag/internet HAS more than you think you know involved with AA. Skip,If you already knew this part.
>HUD (matters)
>Ah, yes…FOV.
>Keep it lower than 90 on console, unfortunately we are limited to some pretty bad rendering in this case. The higher your fov, the worse your aim assist is going to be. Lack of anti-Aliasing at further distances. Would be cool to have a FXAA/TAA (resolution/frame rate) option in game. Consoles simply, can’t handle the stress on the. You’d think a WISH 3070(lol) and 32GB-Ram could lol.
>General Sens/MORE OVERLAYS
>45 (ALL OPTICS 1-8 MATCH THIS SENS)
> ADS Sens
> 100
>ADS FOV
> ON
>NO HDR (stay away from HDR if you want aim assist, this game is POORLY optimized for “X/S Experience”
>motion blur
>Minimal
>Vignette/Chromatic
>Off
>Controller/On Foot
>FOV
>85
>Soldier Aim Assist
>70 (to high of a value results in my cross hair pulling to other enemies when another enemy gets in the way of who I’m shooting at)
>Soldier Aim Assist SnapOn
>100
> Soldier ZOOM aim Sens
>100
>Aiming Left/Right acceleration
>0
>Vertical Aim ratio%
>50
>vertical Zoom ratio
>80
>Uniform aiming
>OFF
>Zoom Transition Smoothing
>ON
>Controller Tuning
>Controller Left stick
>Center Deadzone
>4
>Axial Deadzone
>1
>Max input threshold
>1
>Controller Right Stick
>Center Dead zone
>6
>Axial Deadzone
>1
>Max input threshold
>1
>LT/RT deadzones
>lowest
Now of course these are my settings, user defined of course. Catch me streaming sometime if you wanna see 🫡 TTV/iBUSTJUICE
@iBUSTJUICE wrote:>YOUR BANDWIDTH/FPS HAS A HUGE IMPACT ON AIM ASSIST. LOWER FRAME(s) BEING DROPPED WILL THROW OFF AIM ASSIST/IE PACKETLOSS/NETCODE (128p on a 45hz server, SEND/RECIVE PACKETS once every 45/frame a second, that’s just not enough for 128p)
No it does not. As long as you have 512kbps available you shouldn't be seeing any added benefit of extra bandwidth. Bandwidth, ping, jitter, packet loss are independent. It's the last three that really matter for gaming.
If you are on PC you can monitor bandwidth usage by connection. When I've done this in the past for Battlefield I recall seeing typical usage of around 100-200kbps. EA lists 512kbps as the requirement.
Also 45Hz means 45 cycles per second. Or 22ms. In other words if you are running at 45FPS you are generally getting a fresh packet for each frame. You are not getting 45 packets 'per frame' (assuming you are running 60FPS that be equivalent to a 2700Hz tickrate!)
