Welcome to symthic forums! We would love if you'd register!
You don't have to be expert in bit baking, everyone is more than welcome to join our community.

You are not logged in.

Hey! If this is your first visit on symthic.com, also check out our weapon damage charts.
Currently we have charts for Battlefield 3, Call of Duty: Black Ops 2, Medal of Honor: Warfighter and Call of Duty: Modern Warfare 3

Posts: 3,440

Date of registration
: Mar 19th 2014

Platform: Xbox One

Location: Canada

Battlelog:

Reputation modifier: 15

  • Send private message

11

Thursday, January 26th 2017, 1:42am

Visual Recoil is the standard, accepted proper noun for your aim point deviating from the true aim point from any form of animation, be that recoil, soldier movement, or anything else. That's the term.

Just like we use Tank for armoured vehicles instead of the more technically correct Landship, thanks the the Brits' Landship Committee using the codeword "Tank", as in "Water Storage Tank", to keep the program secret, and that term sticking, Visual Recoil is the catch-all term for this. Let's discuss the issue, and how to solve it, without being pedantic about word choice and only further confusing people.


Yes, Visual Recoil is definitely an issue in BF1 again, and Optical lens sights are by far the worst affected. Remember that the higher your zoom, the more severe the deviation will be. The best way to get around it is Iron Sights with flat 1x zoom.
Who has fun, wins.

Posts: 3,257

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

12

Thursday, January 26th 2017, 1:45am

Okay, so the title isn't completely accurate to our known definition of "visual recoil" call it "strafing spriginess." The point bidet made and the point I recognized is that the movement animation of the dot does not represent the true aimpoint. Nevermind, Uranium explained it.

The fact that a new strafing animation has been introduced that essentially mimics visual recoil without firing places it on the same level of misleading nonsense that the unpolished implementation of BF4's visual recoil held. I support these designs but only if they can be properly installed. I would have had no issue with the concept of visual recoil had the aimpoint actually presented where shots would land, similarly if the strafing springiness were to represent the true aimpoint I would have no issue here either.

The conflict resides in that they don't and misleading information can never be beneficial for gameplay.
To Aim Assist or not to Aim Assist, that is the question.

Nope. Aim Assist or bust; here's why:

Default Aim Assist Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.75
    AttractUserInputMultiplier 0.45
    AttractUserInputMultiplier_NoZoom 0.5
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.85
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.1
    AttractMoveInputCap 0.0
    AttractYawStrength 1.0
    AttractPitchStrength 0.34
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.2
    SnapZoomPostTime 0.2
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput 0.2
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 1.2
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0

No Slowdown Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.0
    AttractUserInputMultiplier 1.0
    AttractUserInputMultiplier_NoZoom -1.0
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.0
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.0
    AttractMoveInputCap 0.0
    AttractYawStrength 0.0
    AttractPitchStrength 0.0
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.0
    SnapZoomPostTime 0.0
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput -1.0
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 0.5
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0
    DisableForcedTargetRecalcDistance 7.0


No Auto Rotation Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
 AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.75
    AttractUserInputMultiplier 0.45
    AttractUserInputMultiplier_NoZoom 0.5
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.85
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.1
    AttractMoveInputCap 0.0
    AttractYawStrength 1.0
    AttractPitchStrength 0.34
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.0
    SnapZoomPostTime 0.0
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput -1.0
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 0.5
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0
    DisableForcedTargetRecalcDistance 7.0

Prepare your laughbox

the Sebstalder is quiet good since it can 3hit kill at any distanc ,but In my opinion i actually thikn the sweeper is better, its got a really really fast firerate that can beat alll those Noobmaticos, Helregall adn shitguns in close quarters , and its also really accurate out to like l;ong range,. overall great allround gun, jsut my 2$ tho


NoctyrneSAGA

PvF 2017 Champion

(9,607)

Posts: 6,965

Date of registration
: Apr 3rd 2012

Platform: PC

Battlelog:

Reputation modifier: 19

  • Send private message

13

Thursday, January 26th 2017, 2:14am

Visual Recoil is the standard, accepted proper noun for your aim point deviating from the true aim point from any form of animation, be that recoil, soldier movement, or anything else. That's the term.

Just like we use Tank for armoured vehicles instead of the more technically correct Landship, thanks the the Brits' Landship Committee using the codeword "Tank", as in "Water Storage Tank", to keep the program secret, and that term sticking, Visual Recoil is the catch-all term for this. Let's discuss the issue, and how to solve it, without being pedantic about word choice and only further confusing people.


Yes, Visual Recoil is definitely an issue in BF1 again, and Optical lens sights are by far the worst affected. Remember that the higher your zoom, the more severe the deviation will be. The best way to get around it is Iron Sights with flat 1x zoom.


Visual Recoil is the standard, accepted proper noun for your aim point deviating from the true aim point from the firing animation. That's the term.



Visual Recoil has been defined before as the firing animation and not solely on this website either.

The original definition was posited by the CoD Wiki and it took quite a while before the people here actually accepted it as 100% correct.

Not sure when strafing animation or even "deviating from the true aim point from any form of animation" got added in there.

Nor do I understand how you can insert the word "recoil" in there when it is not even firing.



Furthermore, DICE does not use the term Visual Recoil.

They simply call it the firing animation.

I bet if you brought this up with them, they would probably ask if you were talking about strafing animations.



@JSLICE20

Strafing animations and their behavior are not new at all.
Data Browser

Passive Spotting is the future!

With this, I'll rid MGO3 of infestation. Sans bad gameplay MGO3 will be torn asunder. And then it shall be free. People will suffer, of course - a phantom pain.

Reddit and Konami will rewrite the records... And I will be demonized in human memory. But... The thirst for good gameplay that I have planted will infest MGO3. No one can stop it now. The Rebalance Mod will unleash that thirst unto the future.


Are you a scrub?

If it flies, it dies™.

Posts: 3,257

Date of registration
: Apr 26th 2013

Platform: PS4

Location: Arizona, USA

Reputation modifier: 15

  • Send private message

14

Thursday, January 26th 2017, 2:22am

It is exponentially more exaggerated. That's for certain.
To Aim Assist or not to Aim Assist, that is the question.

Nope. Aim Assist or bust; here's why:

Default Aim Assist Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.75
    AttractUserInputMultiplier 0.45
    AttractUserInputMultiplier_NoZoom 0.5
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.85
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.1
    AttractMoveInputCap 0.0
    AttractYawStrength 1.0
    AttractPitchStrength 0.34
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.2
    SnapZoomPostTime 0.2
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput 0.2
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 1.2
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0

No Slowdown Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.0
    AttractUserInputMultiplier 1.0
    AttractUserInputMultiplier_NoZoom -1.0
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.0
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.0
    AttractMoveInputCap 0.0
    AttractYawStrength 0.0
    AttractPitchStrength 0.0
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.0
    SnapZoomPostTime 0.0
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput -1.0
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 0.5
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0
    DisableForcedTargetRecalcDistance 7.0


No Auto Rotation Data

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
 AccelerationInputThreshold 0.98
    AccelerationMultiplier 5.0
    AccelerationDamping 4.0
    AccelerationTimeThreshold 0.15
    SquaredAcceleration 0.0
    MaxAcceleration::Vec2
        x 2.0
        y 2.0
    YawSpeedStrength 1.0
    PitchSpeedStrength 1.0
    AttractDistanceFallOffs::Vec2
        x 1.0
        y 1.2
    AttractSoftZone 0.75
    AttractUserInputMultiplier 0.45
    AttractUserInputMultiplier_NoZoom 0.5
    AttractOwnSpeedInfluence 0.0
    AttractTargetSpeedInfluence 0.85
    AttractOwnRequiredMovementForMaximumAttract 0.0
    AttractStartInputThreshold 0.1
    AttractMoveInputCap 0.0
    AttractYawStrength 1.0
    AttractPitchStrength 0.34
    MaxToTargetAngle 45.0
    MaxToTargetXZAngle 45.0
    ViewObstructedKeepTime 0.0
    SnapZoomLateralSpeedLimit 1000.0
    SnapZoomTime 0.2
    SnapZoomPostTimeNoInput 0.0
    SnapZoomPostTime 0.0
    SnapZoomReticlePointPriority 999
    SnapZoomAutoEngageTime 0.0
    SnapZoomBreakTimeAtMaxInput -1.0
    SnapZoomBreakMaxInput 0.2
    SnapZoomBreakMinAngle 90.0
    SnapZoomSpamGuardTime 0.5
    SoldierBackupSkeletonCollisionData *nullGuid*
    CheckBoneCenterOnlyDistance 40.0
    DisableForcedTargetRecalcDistance 7.0

Prepare your laughbox

the Sebstalder is quiet good since it can 3hit kill at any distanc ,but In my opinion i actually thikn the sweeper is better, its got a really really fast firerate that can beat alll those Noobmaticos, Helregall adn shitguns in close quarters , and its also really accurate out to like l;ong range,. overall great allround gun, jsut my 2$ tho


Posts: 3,440

Date of registration
: Mar 19th 2014

Platform: Xbox One

Location: Canada

Battlelog:

Reputation modifier: 15

  • Send private message

15

Thursday, January 26th 2017, 2:33am

I've been working on this topic since it first got brought to the community's attention in a big way BF4. I've worked directly with multiple devs on it over the past few years, among a laundry list of other animation bugs, errors, and fixing them. I know what terms mean, and what terms devs or the community or whoever use.

You're not working to fix the issue, and are adding confusion where there previously wasn't and doesn't need to be any. Either contribute, or please stay out if it.
Who has fun, wins.

NoctyrneSAGA

PvF 2017 Champion

(9,607)

Posts: 6,965

Date of registration
: Apr 3rd 2012

Platform: PC

Battlelog:

Reputation modifier: 19

  • Send private message

16

Thursday, January 26th 2017, 2:44am

It seems confusing to me that, for all your professed knowledge of the issue, you are unable to use nomenclature properly (nomenclature used by DICE no less).

Especially since you are not the only one who was familiar with the issue since the beginning.
Data Browser

Passive Spotting is the future!

With this, I'll rid MGO3 of infestation. Sans bad gameplay MGO3 will be torn asunder. And then it shall be free. People will suffer, of course - a phantom pain.

Reddit and Konami will rewrite the records... And I will be demonized in human memory. But... The thirst for good gameplay that I have planted will infest MGO3. No one can stop it now. The Rebalance Mod will unleash that thirst unto the future.


Are you a scrub?

If it flies, it dies™.

elementofprgress

Wizard moderator

(3,544)

Posts: 1,619

Date of registration
: Jun 28th 2012

Platform: PC

Location: RI, USA

Battlelog:

Reputation modifier: 14

  • Send private message

17

Thursday, January 26th 2017, 4:15am

I imagine adjusting visual recoil and tweaking it is a pain in the butt on few levels.

So "fixing"/tweaking might be a pain but its not like fixing and/or removing visual recoil is totally possible. From straight up removing the animation(why would they? it would look so bad, to tweaking things or even things like how BF4 responded and treated visual recoil post-CTE.

So I don't know where the notion that they CANT do anything about visual recoil came from, they have done it in the past.

for reference this is visual recoil isolated in BF4 pre-CTE. Maybe I'll get around to isolating it in BF1 and compare but really its only seems significant on a few weapons.

BF4: Hidden Scope Sway Animation While Shooting - YouTube



edit:
@NoctyrneSAGA
Knock it off. No one here cares about the nomenclature, everyone who as posted in this all knows we are referring to the same thing.

Symthic Forum Rules
Battlefield Data Browser
Come join us on teamspeak!!!
Symthic/Team Symthic Teamspeak: TeamSym.Nitrado.net

This post has been edited 1 times, last edit by "elementofprgress" (Jan 26th 2017, 4:22am)


NoctyrneSAGA

PvF 2017 Champion

(9,607)

Posts: 6,965

Date of registration
: Apr 3rd 2012

Platform: PC

Battlelog:

Reputation modifier: 19

  • Send private message

18

Thursday, January 26th 2017, 4:18am

Remember, isolating is as simple as dying while firing the weapon then getting revived.
Data Browser

Passive Spotting is the future!

With this, I'll rid MGO3 of infestation. Sans bad gameplay MGO3 will be torn asunder. And then it shall be free. People will suffer, of course - a phantom pain.

Reddit and Konami will rewrite the records... And I will be demonized in human memory. But... The thirst for good gameplay that I have planted will infest MGO3. No one can stop it now. The Rebalance Mod will unleash that thirst unto the future.


Are you a scrub?

If it flies, it dies™.

elementofprgress

Wizard moderator

(3,544)

Posts: 1,619

Date of registration
: Jun 28th 2012

Platform: PC

Location: RI, USA

Battlelog:

Reputation modifier: 14

  • Send private message

19

Thursday, January 26th 2017, 4:23am

Remember, isolating is as simple as dying while firing the weapon then getting revived.



I know right. I did it the hard way. -.-

Symthic Forum Rules
Battlefield Data Browser
Come join us on teamspeak!!!
Symthic/Team Symthic Teamspeak: TeamSym.Nitrado.net

Posts: 3,440

Date of registration
: Mar 19th 2014

Platform: Xbox One

Location: Canada

Battlelog:

Reputation modifier: 15

  • Send private message

20

Thursday, January 26th 2017, 4:25am

Mr Weapons Guy and Mr Animator Guy at LA have already been working on a few problem guns. I believe the Luger 1906 and Pieper Carbine got adjusted for the Feb patch (not sure what else), and they also expressed interest in toning down the Auto-5's massively misaligned firing animation.

While the firing animations are important, they can never be perfect (especially with iron sights), but it's the strafing/movement misalignment that should really be focused on, I feel.
Who has fun, wins.