September 2017
September 2017
September 2017
I think it is important that you pay attention to some of the more coherent posts. The problem is not an inability to purchase traits. The problem is one of cost display. More specifically when you purchase the trait and choose to "Submit" and save your choice, it takes an additional amount. For example: I'm trying to purchase Aggressive Catch for Chris Conley. It's cost is 2250 and I have 2711. I am able to "Increase" it, but when I choose "Submit", despite having 461 XP still available, it won't proceed and says the trait can not be purchased.
September 2017
I am having this same problem except that only certain players cannot be upgraded. I play with the panthers on CFM and Curtis Samuel a WR is a player i cannot upgrade but other players like Christian Mccafffrey work fine. To be clear when i try to spend xp on any trait for Curtis Samuel it tells me the trait cannot be purchased but on most other players it allows me to spend my xp on traits.
September 2017
September 2017
This really is quite frustrating...
We should at least be getting some kind of an update if there isn't a hotfix available. We can send you all the screenshots you want, but it's pretty clear what's going on. A month after release and there's still no update to fix this issue? I'd say unacceptable, but what choice do we have?
September 2017
September 2017
September 2017
@EA_Barry I think it is important that you understand this issue is not fixed. You marked my last comment as an accepted solution, but it isn't a solution. It was a clarification of the actual problem. Can we please get some sort of assurance that the cost display issue is being taken care of and not ignored? It seems like at this point they've swept this under the rug either because it isn't completely game breaking or they can not seem to repeat the problem in their tests. Those of us that play almost exclusively franchise should not be handicapped by an issue that causes us to spend way more XP than we think we are.
September 2017
Seeing this issue marked as "solved" is extremely disconcerting.
If it's solved, none of us has seen a solution.
@EA_Barry, come on man. You've got to give us something. Radio silence from you all week.