killspree, on 16 November 2015 - 07:31 AM, said:
I know I'm being rude again but really there was not very much wrong with 4.1 and if the main goal of FS is to become BIG in the competitive side again they should perhaps ask the communities that host trusted well know public server´s who are mostly the only thing still keeping urban terror alive.
Well as far as I can see FS's mandated is to keep the game going/working another year in the face of obsolesces by design. 4.2 became a bigger project because 4.1 was fundamentally broken in critical areas and I/we figure that some still prefer 4.1 because they had adjusted and learned how to play around the bugs.
As a requirement of course is to have a complete package that would be attractive to new players to play a run and gun shooter that they would at the base level be familiar with but the collision mesh being used in 4.1 is broken and the torso part of the HM had exploded.
To tell the story I was ask to audit the player models, animations, and test the current condition of a very important part/requirement of the game which is the collision mesh which is not rendered and have no clue as to it's current state. The first feature request I made was the ability to render the collision mesh and animations so I could see what was happening and found that the torso looked something like this.
http://4.bp.blogspot...ffer_fish_5.jpg
But worst.
When and how this had occurred no one knows but could not be left in this condition as part of the 4.2 update which was “suppose†to be a simple bug fix release.
This as a problem created a ripple effect into other areas such as the first hit rule which the first shot fired would be 100% bound to the trace but Don Don being so kind did a test showing and demonstrating what he though as a problem with the 100% rule that a hit at distant would only occurred about 85% of the time.
In a way it was true that the 100% rule was broken but was not caused by a broken function but a broken hitmesh where the shots not being counted were passing through the HM with out even registering that a hit event had occurred. I assume that this is what is meant by bad hits.
The collision mesh is also on another channel so when warping occurs, where you can see your 3rd person in two places at the same time. This is a hiccup in the prediction code and when it kicks in there is no way to know where the collision mesh had landed up.
Granted some of the older players still prefer 4.1 as they had learned to take advantage using firing techniques, which is OK with us as long as they are playing Urban Terror, but 4.2 is a superior version for those new to the game who do not need to relearn how to aim and shoot.
By the way on a devmap you can render the hitmesh with I believe r_debugaries 1
Overall though I do agree there is nothing wrong with the game as it is now and if it does not need fixing leave it alone but what was fixed had to be fixed
MultiQuote
FS chief admin
head moderator
