Forum Discussion
With the new update today it looks like this issue is still unresolved. What’s the point of even starting a dynasty at this point when you can’t even have accurate rosters available. Kind of sad this is a problem.
You can definitely load the new rosters into both online and offline. But there is an bug that affects a large number of players. It continues to be made worse with each roster update (including todays) because the nature of the bug.
I posted about it in another post that I am copying here:
So this issue started on Aug 29 with the roster update. It has been 56 days. We have seen a few minor patches, two major title updates (including today), and another roster update. And no acknowledgement or fix. Can we please at least know if the team is aware of this issue?
What it Affects:
-Any player who was added to the base roster in any roster update since launch.
-Any player who had their position changed in the base roster since launch.
-An estimated 15-40% of all the players in the game.
The Problem:
-These players' archetypes will change upon creating a new dynasty (offline and online).
-This can result in a massive drop in OVR.
-It will also affect player progression in dynasty, as the player will develop with the wrong archetype.
The problem seems to vary by position. Here are some examples:
-QB seem to default to Field General
For example: FAU QB Kasen Weisman should be a 67 OVR Improviser, but appears as a 63 OVR Field General
-HB seem to default to Receiving Back
For example: JMU RB George Pettaway should be an 85 OVR Elusive Back, but appears as a 76 OVR Receiving Back
-FB seem to default to Blocking
For example: NC State FB Jordan Poole should be a 78 OVR Utility, but appears as a 62 Blocking
-WR seem to default to Deep Threat
For example, Western Michigan WR Kaevion Mack should be a 72 OVR , but appears as a 71 OVR Deep Threat
-TE seem to default to Blocking
For example: Cal TE Corey Dyches should be an 83 OVR Vertical Threat, but appears as a 45 OVR Blocking
-OL seem to default to Pass Protector
For example, JMU LT Tyshawn Wyatt should be a 70 OVR Power, but appears as a 64 OVR Pass Protector
-DL seem to default to Power Rusher
For example, Coastal Carolina RE Jayden Bryant should be a 58 OVR Speed Rusher, but appears as a 50 Power Rusher
-OLB seem to default to Power Rusher'
For example, Texas ROLB Morice Blackwell Jr should be a 79 OVR Pass Coverage, but appears as a 65 OVR Power Rusher
-MLB seem to default to Field General
For example, Cincinnati MLB Monty Weedon should be a 67 Pass Coverage, but appears as a 65 Field General
-CB seem to default to Slot
For example, Duke - Tre'shon Devones should be a 76 Zone, but appears as a 71 Slot
-S seem to default to Hybrid
For example, Utah State SS Omari Okeke should be a 77 OVR Run Support, but appears as a 74 OVR Hybrid
- 10 months ago
Thanks for your reply I really appreciate it because it’s almost impossible to find any support for this type of bug issue. I see what you’re saying now after loading up a new dynasty with Indiana just now. I wonder if this bug affects the performance of CPU teams as well or not. But like you I would like to hear devs comment if possible.
- 10 months ago
Oh I have been saying this for about two months. No answer.
It doesn't seem to affect the underlying ratings. Just their archetype and OVR.
So initially it doesn't affect the CPU or user performance (or so I think).
But it does affect players development, as they will develop with the wrong archetype.
And a workaround is to change the affected players positions out of their position and then back (or just to another position if desired), but only during the offseason change position phase. This will reinstate their correct archetype.
But any user players will develop with the wrong archetype for one year. And worse, all affected CPU players for all 133 other teams will develop with the wrong archetype for their whole career as their is no way to change their positions (you can't use the edit player feature because the bug exists when making a position change using this method). This ruins these players developments.
It affects certain positions worse than others. OLB, HB, TE, OL, and FB see the biggest negative affect in my opinion.
- 10 months ago
Wow that’s very annoying for sure. Would be nice to get some support for an issue that seems very resolvable. I’m surprised it wasn’t fixed with all the new tweaks they did to dynasty.
About College Football 25 Dynasty
Recent Discussions
- 3 days ago
- 13 days ago