40 replies to this topic

[Mouthcrunch]

Has it always been like this!?

[VonMiller58]

    O          O

 

           <

 

?????????????

[lostchance]

I knew that the gld only worked when the tank was stationary. And since I'm usually in motion. I habitually would choose the rammer over the gld.

After seeing this. I think I'll actively avoid the gld.

[reluctanttheist]

WG states that the bug will be fixed in 3.3.1.  I'm guessing something like this can be fixed server-side since aiming is done at the server, not at the client.

[hson_hson]

reluctanttheist, on 03 November 2016 - 05:25 PM, said:

WG states that the bug will be fixed in 3.3.1.  I'm guessing something like this can be fixed server-side since aiming is done at the server, not at the client.

 

I'm not so sure.

Yes the final calculations are made server-side in order to calculate the shell trajectory but I wouldn't bet on the bloom being sent from server to client constantly.

I would guess that the client calculate the bloom based on the data stored in the client (base dispersion, dispersion on the move and so on) and use that when drawing the bloom.

But I could be wrong...

[reluctanttheist]

hson_hson, on 03 November 2016 - 08:32 AM, said:

I'm not so sure.

Yes the final calculations are made server-side in order to calculate the shell trajectory but I wouldn't bet on the bloom being sent from server to client constantly.

I would guess that the client calculate the bloom based on the data stored in the client (base dispersion, dispersion on the move and so on) and use that when drawing the bloom.

But I could be wrong...

 

Perhaps the server can send corrected values to the client for bloom reduction?  The whole server-client interaction in this game is a huge component of its design - and its success.

​

[hson_hson]

reluctanttheist, on 03 November 2016 - 07:31 PM, said:

 

Perhaps the server can send corrected values to the client for bloom reduction?  The whole server-client interaction in this game is a huge component of its design - and its success.

​

 

It could be done that way, but I can't see any real reason to do it, it would just cause some overhead. 

The bloom indicator is just a visual aid for the player...

[Player_5773117413]

Mouthcrunch, on 02 November 2016 - 11:56 PM, said:

Has it always been like this!?

 

I feel like it's been an unspoken issue, or at least it simply wasn't realized, since before this update

[_Diesel_41_]

Thanks RA. Proof is in the video.

The bloom jndicator is also directly tied to the aim time. 

When you add V-Stab, it makes the bloom smaller initialy from the get go, hence the aim time is shorter regardless if in motion or not.

when you add GLD, it makes the bloom time (from largest size to smallest size), shorter. ONLY if tank is completely motionless

Edited by _Diesel_41_, 04 November 2016 - 02:23 AM.

[SigDocBon]

I dumped all my GLDs and camo last night. Over a million credits in refunds, lol

[SchnauzerKampfwagenIV]

This maybe off topic but the shell reload on my M2 autogun has gotten way longer since yesterday. I mounted the derp and will check egld now bc that bloom is crazy. There are some bugs in this ud.

[Zip_Zip]

Just ran some tests. Its very difficult to tell and time. Does GLD kick in when the tank stops accelerating or turret stops actually moving or when the control input stops. Many tanks have momentum and don't stop imidiately including turret. Remember the camera is instant but the turret takes time to move and line up with the camera and the camera can also move with tank movement.

 

GLD kicks in when tank and turret stop moving. A turretless TD should be the best means of gauging the aim time decrease by parking the tank and just traversingthe gun. Even then its the gun dispersion value and not the fully bloomed aim from hull movement. 

 

May try again after super with a TD to see if I come up with a different conclusion.

 

My current conclusion is nil. Needs more testing and more reliable means of timing. I'll check the reload time with and without on my is2 as well. 

 

To be updated....

 

Edit: UPDATE

 

So here was my method.

First I tried with non turret td's but again could draw no clear conlusion.
Next I went to a TD with bad dispersion and a turret. The FV183. 
I traversed the turret in sniper mode. When the green circle of the gun reached the center of the arrow in the aiming reticle I started a stopwatch.

 

I did this 11 times with a GLD and 11 times without. Simply timing how long it took to get the aimed in sound after the green circle reached the aiming reticle. I found what I feel are conclusive results. As well as some interesting notes.

 

Times with GLD:
2.97, 2.87, 2.97, 3.06, 3.03, 3.0, 2.97, 2.88, 3.19, 2.94, 3.0 avg = 3.03 sec

Times without GLD (vents in place)*:
3.38, 3.25, 3.25, 3.25, 3.28, 3.25, 3.25, 3.28, 3.34, 3.34, 3.35 avg = 3.29 sec

 

*vents will have an effect on aim time as well but only around 2.5% based in a calc I did somewhere else on the forum many moons ago.

 

Conclusion: GLD (at least on the FV183 is having a clear effect when traversing the turret. In the amount we could expect if the GLD was properly working. 

 

Important notes:
The base aim time on the gun is listed as 3 sec and some of my results put the times above 3 sec and around 3 sec.

We should expect the aim time to be 3 sec and GLD to make it 2.7 sec. Why is this not the case. 

1. My reaction times may account for the difference but since my reaction time is there on both counts and I've taken a decent sample though we don't have an actual accurate aim time we can see that the GLD is in fact having an effect.
2. RNG may be to blame. The could be some RNG involved in these times as well. Again with the sample size RNG if affecting aim time would be averaged over both samples. It could very well be that the posted aim times in a tanks stats are an average aim time and not an absolute one!

 

Interesting note: 
When traversing the gun (hull stationary) when I got close to, but still about an inch away (iPad 9.7" screen) from the edge of the turret traverse range I noticed something interesting. When making large traverses the line indicating max traverse was vibrating, indicating that with larger more rapid movements on the gun there would be a vibration that would actually give longer aim times than if the movements were kept smaller. I used only smaller movements for my testing but I did find it interesting that the game physics are so intricate.

 

Edit 2: Another conclusion is that the GLD seems to be of minor value even if it does work. 

 

Edited by Zip_Zip, 06 November 2016 - 12:51 AM.

[reluctanttheist]

GLD has been fixed in 3.3.1

 

[Zip_Zip]

reluctanttheist, on 06 November 2016 - 02:52 AM, said:

GLD has been fixed in 3.3.1

 

 

I just checked. I have 3.3.1 installed. Blitz must have auto updated itself without my being aware, that's why it was working on my FV! 

Duh, didn't even think to check.

[Parrott_Cannon]

Zip_Zip, on 06 November 2016 - 12:12 PM, said:

 

I just checked. I have 3.3.1 installed. Blitz must have auto updated itself without my being aware, that's why it was working on my FV! 

Duh, didn't even think to check.

 

Yep, also was mentioned that with GLD equipped, there was a decrease in reload time. Which is not a value that should have been happening at all. 

[_WMX_]

Kanuuan, on 06 November 2016 - 09:07 AM, said:

 

Yep, also was mentioned that with GLD equipped, there was a decrease in reload time. Which is not a value that should have been happening at all. 

 

Man I needed all the help I could get!!!  xD

Edited by _WMX_, 07 November 2016 - 09:58 AM.

[Cybergyn]

Was this bug just on ios and android or was it a windows 10 bug also?  I can't find a 3.31 for windows 10

[dayton07277]

The battle count is still messed up.!

[Tuberculosis_Victim]

reluctanttheist, on 06 November 2016 - 02:52 AM, said:

GLD has been fixed in 3.3.1

 

 

Thank you for posting video evidence!! I'm glad it got fixed... who knows how long it has been broken.  I'm wondering if they would have even known something was wrong if I or someone else like me hadn't noticed it?

Edited by Tuberculosis_Victim, 10 November 2016 - 07:20 PM.

[Tuberculosis_Victim]

Cybergyn, on 08 November 2016 - 07:19 PM, said:

Was this bug just on ios and android or was it a windows 10 bug also?  I can't find a 3.31 for windows 10

 

Im on iPhone 6 Plus, but I'm assuming it was like that for all blitz platforms.  Like I said, that's an assumption.

Edited by Tuberculosis_Victim, 10 November 2016 - 07:14 PM.