2.4.2014

Posted on by

Check out Chieftain’s article about T28 deployment in Korea!

- in test 3, HD Centurion 7/1 should appear
- gun damage (alpha) is an arbitrary number, two guns of the same caliber do not have to have the same alpha
- the same gun can have different rates of fire in different vehicles, the difference lies in “setup of the combat compartment”
- in current round of 9.0 test, there is a bug where users of AMD processor PC’s suffer from disconnects, this will be fixed in next round of test
- Storm is aware that the weakspot of current WoT graphics is the grass and trees/bushes, he mentioned increasing the radius of grass render and the multi-layer grass
- when considering squeezebore weapons, the number, used for the purposes of overmatch and other calculations where caliber is required is the nominal gun caliber, not the shell caliber (in case of Waffe 0725, that number is 75mm)
- apparently, the developers dealt with the bug (appearing on current live server), where due to strong unsynchronization between server and client reticle (aim circle), shots were flying wildly out of the client circle

41 thoughts on “2.4.2014”

  1. ‘Check out Chieftain’s article about T28 deployment in Korea!’

    i saw this yesterday, didnt want to open it, as i asumed it was another april fools

  4. “- apparently, the developers dealt with the bug (appearing on current live server), where due to strong unsynchronization between server and client reticle (aim circle), shots were flying wildly out of the client circle”

    This is happening more often lately…

    • Till now it was our fault, thanks to bad ping.
      Finally it was reclassified on bug :@)

    • Did you try to turn off Server side reticle ? It under Setting -> General -> (bottom) un check Enable server reticle. If you already have that, it could be lag or something else.

    • I always get caught in the screen that says synchronizing tankers after every battle I play in Karl.
      Is this possibly related to my problem?

  5. ‘the weakspot of current WoT graphics is the grass and trees/bushes’ ?

    A: like outdated Amiga500 grafic from the 80′s
    B: bad programming eating large part of GPU for low result

  6. So what’s the difference between T28 and T95 in WoT, as according to that article, it’s the same vehicle? Apart from those super cool detachable extra pair of tracks.

    • As far as I understand they are the same vehicle, the tracks are detachable to make transportation easier. IIRC the vehicle started as the “105mm Gun Motor Carriage T95″ early in development then was renamed the “Super Heavy Tank T28″ So the research tree should really be T95 >>T28 not the way it is.

      • Priory of Scion corrected me elsewhere. It was T28 > T95 > T28. So it had the name changed mid development then changed back to the original.

      • There should be no research, it was ONE vehicle. The wot T28 is kinda made up, because it never had that ledge up front and it had HVSS (as on easy eight) not VVSS (as on M4) suspension. The WoT T28 is made different for gameplay reasons.

        • When the T28 is remade to hd i assume they will correct the model and make it look like a t95 exactly just without the extra side tracks/armor. I read a fourm topic by Daigensui awhile back with a picture of the model correction dont know if its true though. But when alternate hulls come im sure they will become one tank, if the US has a tank destroyer able to fill in at tier 8.

          • Exactly. But there wouldn’t really be a point of having an alternative hull without the extra tracks. Sure you’d lose some weight, but you’d also lose lots of armour. Not to mention the now doubled terrain resistance because you now only have one pair of tracks. I hope they remain split, T28 should just get corrected.

  7. - apparently, the developers dealt with the bug (appearing on current live server), where due to strong unsynchronization between server and client reticle (aim circle), shots were flying wildly out of the client circle

    I reported this problem twice and was just given the usual ‘submit a ping plotter result’ both times (even though I did submit one on the second report). Both times it happened I had almost no lag for most of the battle (40-60ms, with occasional flickers on the red lag light). The second one I even had the server reticle up and I was still shooting at 90° angles from the gun and reticle. I ammo racked a teammate with 1 shot, while we were peak-a-boom-ing, at no time was my gun pointed in the direction that I fired.

    • They ask you for the pingplotter for a reason; it’s how they show to HQ if it’s their ISP or yours. Trust me, I’ve talked with NA support as they gathered pingplotters to send to HQ to show that Telia is shit and that they should get better internet service. Re 90deg, that sounds like the bug they’re fixing, though do remember that if you were peak-a-booming it could’ve actually been a straight shot, but your position lagged (i.e. it still thought you were behind your ally). Kinda like how tanks sometimes jump when you die.

      • What you missed was that I did send the pingplotter on the second one, they just responded with a form response without reading the ticket.

        As for the TK shot, we were side by side at the corner alternating who was peeking, when i shot i was pulled out and the ally was well back and to the side. It is conceivable at some point that my gun was pointed at the side of his turret as we swapped spots but it was at least 5s earlier.

  8. Increasing the range where grass is rendered is not the problem. its the fact that is super low resolution and 2d. Same goes for bushes and trees. Heck trees look like a twigs with arms and then bushes glued to them. Also trees that have suspended leaves not connected to anything. They should try using the current version of speedtree. They have a long way to go before this looks like a modern graphics engine. Even in 9.0.

    • That’s because it’s made with Flash, so it’s always gonna be slow as hell.

  11. ” when considering squeezebore weapons, the number, used for the purposes of overmatch and other calculations where caliber is required is the nominal gun caliber, not the shell caliber (in case of Waffe 0725, that number is 75mm)”
    Makes no sense.

    • Squeezebore guns have one caliber at the breach, and another smaller at the muzzle. Point of sqeezebores is to have a shell flying at higher speeds because of the narrowing of the barrel and increasing pressure inside of it and for shell to be smaller in diameter to reduce drag. Nominal caliber is the “unsqeezed” caliber and difference is usually just a few millimeters.

      • No, it’s a significant percentage like from 75mm to 55mm. The tungsten core is not squeezed. It is an light alloy or aluminum sheaf around this core that is squeezed down. When the shell hits armor the sheaf metal just splatters and doesn’t penetrate the armor, the core does.

  12. - in current round of 9.0 test, there is a bug where users of AMD processor PC’s suffer from disconnects, this will be fixed in next round of test
    ______________
    Lol, how they managed to create a bug that will disconnect only people with AMD processors xD CPU brand racism? :D

    - Storm is aware that the weakspot of current WoT graphics is the grass and trees/bushes, he mentioned increasing the radius of grass render and the multi-layer grass
    ______________
    Question is will it kill the fps.

    • Regarding the first question: they manage to do that by inserting some clever optimisation into the ‘net code – probably threading/semaphore related – that for some reason fails on certain processor architectures. They patch it by either adding an AMD-compatible version or disabling the optimisation on AMD.

  13. - apparently, the developers dealt with the bug (appearing on current live server), where due to strong unsynchronization between server and client reticle (aim circle), shots were flying wildly out of the client circle

    Oh look it actually wasn’t our fault? I don’t see no “oops sorry folks message” I knew it was their side of things screwing up

  14. - apparently, the developers dealt with the bug (appearing on current live server), where due to strong unsynchronization between server and client reticle (aim circle), shots were flying wildly out of the client circle

    This has been happening alot lately was playing my E50 today and 2 fully aimed shots at the side of a obj 704 were missing way up into the sky the 704 was a massive power donkey and tunnel visioned on a scout so i still killed him but really frustrating

  15. “- Storm is aware that the weakspot of current WoT graphics is the grass and trees/bushes, he mentioned increasing the radius of grass render and the multi-layer grass”

    About damn time. I get ca. 30 fps on city/desert maps, but on bushy areas, especailly in sniper view on a TD, my fps rate drops below 10, it’s unplayable that way :/