Forum Discussion
Not a word from EA/CM... Great!
- 3 years ago
I've just posted a separate report for this issue, I would suggest everyone else does the same - make them AWARE. I know it's a pain but I'm guessing they're now ignoring this thread because we're all just talking in it. As far as they know, it's just the OP who's reported it and nobody else.
Plus the OP reported it for multiplayer, whereas I'm getting it for every mode. They've probably only been looking for it in multiplayer.
- 3 years ago@s00zster It's pointless to make separate topics of the same problem. Im pretty sure they are aware of this issue, but they decided to ignore tis thread for watever reason, after @EA_Kent has responded earlier.
- 3 years ago
@Bas_Sie89I think they are at an empasse on how the resolve the issue (or if to do it or not) because doing so would require a reworking of the UI, plus substantial code variations to make it all work. This is not usual patch work but it requires more involvement than that and believe it or not the larger a studio is and the more complicated these sort of things get to properly schedule.
I think they seriously don't know how to approach the issue and if it is the case or not to fix it for this iteration of the game or let it stand until next title.
The only thing we can do is to ask for a fix but ultimately it depends on CM itself if they think the work involved warrants such a fix for this year.
- 3 years ago
@MatiasFCD wrote:Not a word from EA/CM... Great!
I don't really get the point of a Bug Report section if you have a thread go 7 pages and EA/CM doesn't even acknowledge it.
It renders this entire sub-form useless. It makes the Patch update threads that show the things they're investigated watered down.
It's just not a good look all around.
About F1® Franchise Discussion
Recent Discussions
- 21 hours ago
- 22 hours ago
Weekly Warrior Trophy
Solved12 days ago- 15 days ago