Once the main gun is shoot off, it wont ever go back to proper position.
When fixed, barrel is always facing front/ground, separately to turret movement.
Tank can still kill, but animation is broken.
"Porshe" King Tiger model
- Panzerblitz1
- Team Member
- Posts: 1720
- Joined: 24 Nov 2014, 00:12
- Location: Paris, right under the Eiffel tower.
Re: "Porshe" King Tiger model
Hmm we had this bug a long time ago, use the Blitzkrieg King tiger (H) not (P), this is an "old" Vcoh bug.
- Jagdpanther
- Posts: 260
- Joined: 15 Dec 2014, 03:33
Re: "Porshe" King Tiger model
Why there is a choice to make since one is broken and one is not? Just remove it
Re: "Porshe" King Tiger model
It's just a visual bug so there is no real reason to remove it imo
Some people prefer the Tiger 2 (P) because of the additional turret MG
Some people prefer the Tiger 2 (P) because of the additional turret MG
- Krieger Blitzer
- Posts: 5037
- Joined: 06 Dec 2014, 15:53
- Location: I'm from Egypt, living in Qatar.
- Contact:
Re: "Porshe" King Tiger model
Yup, I already never use this version of the KT mainly cuz of this visual bug.. but let me guys tell u a secret FOR THE FIRST TIME... I prefer the other KT not only because it actually doesn't have this bug; but in fact also because of that it does STILL have an active top turret MG gunner who is completely invisible and has no sound too like if he was somehow inside the tank itself However that yet u could clearly notice the bullets being fired as it deals great amount of damage which is another bug with the other version as well.
Though it's not a big deal after all
Though it's not a big deal after all
Re: "Porshe" King Tiger model
Armynator wrote:It's just a visual bug so there is no real reason to remove it imo
Some people prefer the Tiger 2 (P) because of the additional turret MG
Additional turret MG is an obvious choice, but broken animation is confusing.
Damaged KT is a "special care" unit. It's not easy to evaluate turret position from distance.
[Fixed in 4.9.6.] "Porshe" King Tiger model
To conclude this topic - in the next patch we will include a workaround for this bug so it should not appear anymore.