Originally Posted by: Old Hippie 1 
Originally Posted by: sirtra 
T10 has mucked up the leaderboards between the in-game "show results" leaderboard (correctly shows peoples finishing position) and the post-game lobby "previous results" leaderboard (incorrectly jumbles the order and what gets used for the point calculations) again.
It used to incorrectly sort the DNF's alphabetically, then it was patched and sorted them incorrectly by some sort of finish time where all DNF's had differing times for the last second. Now i have no idea **** its sorting DNF's by but its also affecting non-DNF's too, so it's even worse than ever before.
You'd think scoring for a racing game would be pretty high up on the priority list for pre-release testing and checking to ensure re-introduction of such an embarrassing issue wouldn't happen... seems T10 think differently :)
Mucked up? You sound like you believe it was intentional.
Have you ever written complex code? It's rather common for an update that adds to a game or fixes something in a game, to cause even more problems than it fixed. Even after testing, it's impossible for a small team to find every possible bug. It's usually when the update gets into the large community, for actual use, that the bugs are found.
Relax, the issues have been acknowledged by Turn 10, and they said they are working on a solution.
Peace
What gives the impression i believe it was intentional?
Mucked up to me means an error that could and should have been easily avoided had more care or diligence been taken.
I've written more than my fair share of complex code and i dare say i know more about development if you believe the issue here is code related. Do terms like agile, user stories and sprints mean anything to you? Well they do to me and relate to just one of the many development cycle methodologies that many software houses employ for rapid development. I mention this as whilst the bug may lie in the code the real failure here is the overarching process around changes to the code and its testing.
Simply put, you cant avoid bugs or errors in the code but you can and should have adequate testing and checking to ensure simple and rather blatant problems, like a miscalculation of points for leagues, doesn't make it to the general public especially when this isnt the first occurance of it happening.
The fact this is a repeating issue can really only mean a handful of things:
1) T10 does little or no testing before releasing updates to the general public
2) T10 employs non attentive and ineffective beta testers and/or testing processes
3) T10 willingly and knowingly release updates with significant flaws to the general public
It's complacent attitudes like yours which lend to companies like T10 carrying out #3 as though it's par for the course and we should all just accept it. I don't prescribe to that kind of thinking or drink the koolaid.
Sure obscure and infrequent bugs will always make their way into the wild, but an issue with league point scoring that affects nearly every single race and more than half the field - not to mention its not just the nascar league but all leagues.. thats just a massive embaressment which could and should have been avoided.
PS - care to point me to where T10 have acknowledged the issue, from my experience their customer communication is terrible and i'd love to know where your getting your info from