Jump to content
  • 0
Sign in to follow this  

Tyre wear bug - Wear depends on starting tyre?

Question

I´ve tested a lot in china with my league mates last week. 

Multiple Races on the same setups by clear weather, with the same driving style in the same cars ONLINE!

XBOX One - Online Mode - China - 50% - Clear Weather - Full lobbies - Same Setup ( Every Player got his own, but all players tested with the same in every race)

We have all  noticed the same...

Soft/medium: 5/6% tyre wear per lap on mediums
SS/medium: 7/8% tyre wear per lap on mediums

Just the Supersoft tyre wear never changed! All the time the new  supersofts are  at 75%  after 7 - 8 Laps

Summary: Starting on the supersofts in china is increasing the tyre wear of the softs and mediums massively. 

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0
Only just heard about the bug and makes so much sense now! How can this bug not be a priority, essentially ruining  practically everything.
We have a new practise program to help with strategy, this goes completly out the window now, also race runs do too i always do these in P2 and wondered why i couldnt replicate this in the race . So aparr from getting to know the layout out any extensive practise is pointless as you wont learn anything.
Really disapointed but atleast i know why my races have been frustrating. This issue lies in the heart of the game and anything other than a fix is unacceptable.

Share this post


Link to post
Share on other sites
  • 0
Will this be patched anytime soon? Apologies if you've already answered this. Don't visit these forums often. 

Share this post


Link to post
Share on other sites
  • 0
Slater123 said:
Will this be patched anytime soon? Apologies if you've already answered this. Don't visit these forums often. 

jenny said its an issue being looked at but if its not an easy fix it will be the next game. But an issue so key to the whole gameplay surely is a must fix.

Share this post


Link to post
Share on other sites
  • 0
Slater123 said:
Will this be patched anytime soon? Apologies if you've already answered this. Don't visit these forums often. 

jenny said its an issue being looked at but if its not an easy fix it will be the next game. But an issue so key to the whole gameplay surely is a must fix.
i think she actually said they are looking into it and if they can fix it they will, but if they havent got the resources to fix it then it will be fixed for the next game.

Share this post


Link to post
Share on other sites
  • 0
Demonr said:
Slater123 said:
Will this be patched anytime soon? Apologies if you've already answered this. Don't visit these forums often. 

jenny said its an issue being looked at but if its not an easy fix it will be the next game. But an issue so key to the whole gameplay surely is a must fix.
i think she actually said they are looking into it and if they can fix it they will, but if they havent got the resources to fix it then it will be fixed for the next game.

That's codesmasters-speak for "We're not doing anything".

This resources excuse, is one of the great lies. If there are resources for next years game, which also needs the fix, they could correct it for 16 as a means to test it for 17 in a live environment.


If I release bad code into production, if we discover it as part of the next project we don't forget about the past and only fix the issue going forwards, we correct production and verify its working correctly there again so we know that all future releases don't have that issue.

It does feel like the only way they wouldn't allocate resources is if there was no game coming for 2017, hence no budget whatsoever, why throw money after F1 2016 if it is the last iteration from Codemasters?


Share this post


Link to post
Share on other sites
  • 0
FRACTURED said:
Demonr said:
Slater123 said:
Will this be patched anytime soon? Apologies if you've already answered this. Don't visit these forums often. 

jenny said its an issue being looked at but if its not an easy fix it will be the next game. But an issue so key to the whole gameplay surely is a must fix.
i think she actually said they are looking into it and if they can fix it they will, but if they havent got the resources to fix it then it will be fixed for the next game.

That's codesmasters-speak for "We're not doing anything".

This resources excuse, is one of the great lies. If there are resources for next years game, which also needs the fix, they could correct it for 16 as a means to test it for 17 in a live environment.


If I release bad code into production, if we discover it as part of the next project we don't forget about the past and only fix the issue going forwards, we correct production and verify its working correctly there again so we know that all future releases don't have that issue.

It does feel like the only way they wouldn't allocate resources is if there was no game coming for 2017, hence no budget whatsoever, why throw money after F1 2016 if it is the last iteration from Codemasters?


Agreed. It's funny how stupid Codemasters think their customers are. "We might not have enough resources but we'll let you know", yeah right. It doesn't take 2-3 months to discover a reason for a bug and it's now been over three months since the topic was opened and a week shy from three months when Codemasters reacted to this topic for the first time. 

Only acceptable explanation for not fixing it would be that they didn't get the renewal for the F1 franchise. But even in that scenario it's really disrespectful for customers who have payed a lot of money for this game. And at least for me it will always be a negative thing if someone is asking something about Codemasters. 

I've pretty much already decided that if F1 2017 comes up made by Codemasters, I'm not going to buy it on release or at all. If I end up buying it, I'll make sure I'll buy it second hand. It would have been totally different if someone from Codemasters had been honest and said that "sorry, it's impossible to fix". That would have been an honest answer compared to this "we'll take a look and we are not sure if we even have enough resources". 

I'm quite new to this topic but for a reminder: Last reaction from Codemasters is from December 14th. Great communication with the community I must say. 

Share this post


Link to post
Share on other sites
  • 0
The resources argument always was a convenient excuse if anything.
Take a look at the Baku racing line glitch. What do you reckon? How much manpower does it take to fix it? How long would it take? 1 day? 2?
Yet, they can't even fix something they messed up with a patch.

The reason is simple, they do not have to. Sales are done and dusted, most people play the game for a year at best, and there are surely more than enough people already waiting to pre-order 2017. After all, there are plenty of people defending Codemasters and their business practices. And the few people who are disgruntled and are not willing to buy the next game are a slight annoyance that is easily ignored. I mean, it's not like they haven't perfected the art of ignorance years ago.

The only sad part is the continued brand loyalty displayed by some of the buyers. Instead of being loyal to quality, they think Codemasters can do no wrong, and if they do mess up, it is simply because we haven't supported them enough. Which is mental in my opinion.

Share this post


Link to post
Share on other sites
  • 0
I get the resources things but issues that lie in the heart of the game need fixing and like people said its an issue we dont want to creep into a future release and its a huge bug hugely effecting gameplay, just like the god awful screen tearing/stuttering which has been in the game since 2015s edition. Just done mexico and the frame rate and tears arw almost unplaying at the beginning of sector 2!



Share this post


Link to post
Share on other sites
  • 0
@Lozzy
@jennyannem

how about a patch or news? "Honestly, what are we doning here" - Sebastian Vettel 2k16

Share this post


Link to post
Share on other sites
  • 0

vvvili said:

...It's funny how stupid Codemasters think their customers are...

It's also funny that they're right... It's not game companies' fault when so many people eagerly line up year after year to pre-order & buy the next game(s) no matter how many problems were in prior games. Game companies are just delivering what everybody's wallets repeatedly demand: "Moar gamez rite now!! Who cares about quality?? Just hurry up & release the neXt gamez!!" Barely 4 months after F1 2016 was released, there were people already asking about F1 2017.

Game companies will gladly continue pumping out what people continue throwing money at.

Good quality will only happen when sales are significantly impacted by poor quality.

Can't hear issues being reported over the sound of the cash register. *Cha-ching! Cha-ching!*

Money talks, and if we want things to change, then it's solely up to us to make them hear our money talk by voting differently with our wallets.


Share this post


Link to post
Share on other sites
  • 0
wtsds said:
From what I read about it. So this bug can not be fixed?
NO... the correct sentence is:

"this bug WILL not be fixed"

Share this post


Link to post
Share on other sites
  • 0
@Nagrom Well if they can't take a joke, at least they know how to make one.. the game.

Share this post


Link to post
Share on other sites
  • 0
Lozzy said:
Updated the bug title. We'll have a look in to this.
Lozzy said:
No update yet but we are looking in to it.
Lozzy said:
I've not posted anything because I have no news to post at the moment. When there is I will post it.
Lozzy said:
I closed the other thread because it was a duplicate of this one. Surely that was obvious? Lets not worry about debating that though eh...

As Fractured kindly pointed out as I've said before when I have news I'll post it, but at the moment I have nothing new to post. I appreciate that's frustrating but that's the only update I have.
As @Lozzy has said previously, we are aware of this issue and we’re actively looking into it. Depending on the volume of work required to resolve this, it may not be something we have the resource to fix for F1 2016 – but we’ll keep you updated on our findings as and when we can! If, on this occasion, it’s something we aren’t able to resolve for F1 2016, then we will make it a priority to fix for future projects
Thanks for your feedback so far - as we've mentioned before, this is something that we're looking into. Delving a little deeper into the issue, it's become apparent that this isn't something that has crept in with a patch, and so the solution would be more complex than just rolling back to a previous version.
Whats the craic this month then Codies? Any information on fixes for any of the issues we have pointed out?
Any information on F1 2017?
Any news from the bi-weekly team meetings?

Share this post


Link to post
Share on other sites
  • 0
It's pretty clear where this is going isn't it so I'm going to close the thread for now. Sit tight, there will be some news forthcoming.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

×