Married couples become unmarried/partners after entering CAS
My sims got married, had all the marriage buffs. I entered create a sim via the custom tattoo option. Upon exiting CAS my sims got a pop up that they were now the partners of each other. They had to get remarried. Then I went to plan their outfits and the same thing happened. No mods or custom content. Playing on PC. Edit By crinrict: Adjusted TitleCustom Assets Not Working
There is a problem where the assets I add to my teambuilder are not porting over to the game itself on submitting and loading into franchise. I use a lot of custom assets on my builds and usually have assets that I lay over the helmet to give them a unique look. Last year for Madden 26 I had some really cool helmets that looked like this: you can see that I have a custom layer over the helmet to give it a unique matte/shiny finish. this is what it looks like after importing the build into Madden 27 teambuilder on the site: You can see that the same layer is there and I have it set to a custom finish for that look. This is a circle that is duplicated and laid over the entire helmet shell. I submitted this team and uploaded it to Madden 27, started a franchise and now the helmet looks like this in game: You can still see the color its supposed to be since I matched it up with the facemask but now the entire layer I put on there is either completely removed OR is defaulting to default shiny for texture. I have recreated this issue on every one of my teams and the same thing is happening no matter what I do. I have resubmitted multiple times, used different teams, used only 1 team in franchise, also uploaded multiple custom teams in a franchise file, etc. They all do the same exact thing.Why so antisemitic?
My name is Flyingcoconut666, I was banned for commenting back on antisemitism in the chat. I was banned for saying 2 things that evening. “Ty sped” and “low income comment”. The first comment I was addressing to my mate speed which I thanked him for something as he didn’t have his mic down. I abbreviated it and said Ty sped. Not bulling anyone. Second comment was because for some reason battlefield players began making antisemitic comments and jokes. So yes, I responded. “Low income comment”. As a Jew I’ve dealt with a lot of BS from the gaming community but battlefield certainly has taken the cake. Almost 700hrs. I get banned. Not suspended. no warning, just banned. Yeah I could disable the chat. So I can’t chat with my mates anymore cause of that. I have to block out hate cause the company doesn’t care? I guess nothing unusual. I’ve had to resort to making a discussion about it cause I can’t appeal it on my EA account cause I was banned. For anyone reading this. I was banned for standing up as a Jewish man to hate, Antisemitism is everywhere. But if I can’t even play a game where it comes up for no reason. Or they hear my accent and begin making remarks. Not too sure how to feel about the ban. Annoyed that I spent almost 700hrs and at the end of the day the company never even had my back as a customer, a player. If I do get my account back I would be grateful but also would have a nasty taste in my mouth now knowing that battlefield is what it is today.W Roster Update!!
Love seeing the new guys coming into the roster! I haven’t seen many discussions outside of Instagram for what other fighters we want in the future so my top priority list would be: Quillan Salkilld, Navajo Sterling, Valter Walker, Magomed Zaynukov High but not top priority: Malcolm Wellmaker, Lone’er Kavanagh, Gabriel Bonfim, Christian Leroy Duncan Legacy guys: Anthony Pettis, BJ Penn, Zabit Magomedsharipovdelay/lag/ freeze
these past 2 days i cannot even fathom to play the game i have 3-4 sec delay on everything i do squad battle in any offline mode/match its fine but any online matches whether its rivals or events it's laggy and freezes then the worst i get 4 sec delay is there any fix to this?? plus precise ping 34 and no network issues +good specsSUPERSTAR PLAYERS: STOP MAKING SEPARATE COMPLAINTS. LET’S MAKE EA HEAR ONE.
Superstar players, at what point do we actually make EA listen? Seriously, how many years are we going to keep doing this? We complain about the same problems or some variation of them, EA tells us what they’ve improved, we buy the next Madden and then we’re right back on these forums again. The CFB community just proved with #CFBPlayDontPay that organized pressure can actually work. Maybe Superstar players need to start doing the same thing. The frustrating part is Superstar actually has the bones of a really good career mode. The defense is good. Honestly, sometimes it’s TOO good, but I don’t want EA making defenders stupid. I want the guys on MY TEAM to have some of that same intelligence. I’m tired of watching receivers drop balls that hit them in the hands while defenders make ridiculous catches. I’m tired of DBs getting beat and magically recovering, suction tackles, ridiculous interceptions and having a playbook full of play-action early in your career while you don’t have enough control yet to get yourself out of bad plays. Then you have these manufactured scenario games. The snow game is a perfect example. Increased chance of fumbling in the snow? Cool. That actually makes sense. But when I’m coughing the ball up every other possession, sometimes right when I’m finally putting a scoring drive together, while the simulated CPU offense somehow goes on a 15-play scoring drive without fumbling, come on man. That’s not weather affecting the game. That’s the game affecting ME. Same thing with the games where your TEs are suddenly unavailable or you’re dropped into some manufactured situation because Superstar decided this week needs to be extra difficult. Why? Just let us play football. I’m not asking to win every game. Sometimes I should beat somebody 38-10 because I played my **bleep** off. Sometimes I should get smoked 31-7 because they did. Sometimes it should come down to the last possession. That’s what makes football fun. And yes, I’m winning. That doesn’t mean I’m enjoying it. Winning while feeling like I’m guaranteed to throw one or two INTs every game or waiting to see what the game is going to do to me next isn’t fun. There’s a difference between winning and actually being able to dominate when you’re playing well. If people like the scenario games, keep them. Just give the rest of us a toggle. Let me play my schedule, build my player and see what happens without Madden constantly trying to manufacture some storyline for me. And if you’re dealing with this stuff too, stop making 50 different posts that EA can ignore one at a time. Like/Me Too this one. Add what you’re seeing in your Superstar career. Tag other people dealing with it. Put it all in one place. Because we’ve been asking nicely for years. At some point, maybe Madden players need to do what the CFB community just did and stop paying until EA starts listening. #NoFixNoMaddenMadden 27 Franchise: Core NFL Simulation kills immersion again.
Madden 27 Franchise Feedback: Please Fix the Core NFL Simulation Before Adding More Features I have played Madden Franchise for years, and at this point I am not asking for more storylines, more menus, more scenarios, or more cosmetic additions to Franchise mode. I am asking for the basic functionality required for Madden to simulate a believable NFL season and offseason. I am perfectly willing to track my own league history, statistics, records, awards, player legacies, and storylines. What I need Madden to do is provide a functioning NFL ecosystem around the team I control. Unfortunately, even in Madden 27, major problems with simulation statistics, CPU roster management, and player retirements can create glaring immersion-breaking issues before you even reach Year 2. SIMULATION STATISTICS NEED MAJOR ATTENTION User-played games and CPU-simulated games need to exist within approximately the same statistical universe. They currently do not. This creates a major Franchise problem because realistic production by a user-controlled player can become artificially dominant in categories Madden under-simulates, while realistic production can become uncompetitive in categories Madden over-simulates. Running Back Receiving This is one of the most glaring problems. Running backs receive far too little production in simulated games. Even elite receiving backs can struggle to generate anything resembling realistic receiving numbers. Modern NFL running backs can catch 50, 60, 70+ passes and produce hundreds of receiving yards. Christian McCaffrey famously had 1,387 rushing yards AND 1,005 receiving yards in 2019. Madden does not need to regularly produce 1,000/1,000 seasons. That is an exceptional historical performance. But elite receiving backs need to be capable of approximately 500–900 receiving yards depending on their role, ratings, scheme, health, and season. Exceptional seasons should occasionally go higher. Traditional early-down backs should produce less. Receiving specialists should receive significantly more. Ratings, player archetype/tendencies, depth-chart role, playbook, and offensive personnel should all influence targets. Right now, a user can simply use a running back realistically and accidentally dominate the entire position in receiving production because CPU running backs barely participate in the passing game. That also contaminates Pro Bowl selections, Best RB voting, OPOY consideration, progression, and historical comparisons. Tight End Receiving Tight-end production is similarly too low. Elite receiving tight ends need to be capable of 1,000+ receiving-yard seasons. That should not happen for every TE, but a user-controlled TE producing 1,000 yards should be competing against other elite receiving tight ends—not automatically becoming the most productive TE in football because the simulation cannot generate comparable seasons. Quarterback Rushing Mobile quarterbacks need much better simulation logic. Players such as Josh Allen should be capable of producing realistic rushing yardage AND significant rushing-touchdown totals without their passing production automatically collapsing. Lamar Jackson should not be the only quarterback whose playbook happens to generate something resembling appropriate rushing usage. Player tendencies, physical ratings, scrambling ability, red-zone usage, and playbook should work together. A QB capable of 500–700 rushing yards and 10+ rushing touchdowns needs to exist naturally within the simulation. Quarterback Passing Passing touchdown totals remain too inflated across too many quarterbacks. There should be a wider and more realistic distribution of QB seasons rather than a large portion of the league routinely producing 30+ passing touchdowns. Mobile quarterbacks also should not require an unrealistic tradeoff where appropriate rushing production results in severely depressed passing statistics. Wide Receiver Production Top-end WR production can become inflated, which raises the statistical threshold user-controlled receivers must reach to compete for league awards. Again, the goal is not predetermined statistics. The goal is a believable distribution of outcomes. Defensive Statistics Tackles can become inflated. Sack totals need better distribution so realistic elite EDGE seasons remain competitive. Interceptions appear particularly top-heavy. In testing, multiple defenders were reaching approximately 7–10 interceptions. Exceptional seasons should occur, but they should actually be exceptional. The solution is not to script statistics. Madden needs realistic statistical ranges and distributions influenced by ratings, abilities, tendencies, scheme, playbook, usage, injuries, and randomness. EA has decades of real NFL statistics available as a validation dataset. Large batches of simulated seasons could be automatically compared against real positional distributions during development and testing. CPU ROSTER MANAGEMENT STILL CANNOT MAINTAIN BELIEVABLE NFL ROSTERS The CPU has improved somewhat at avoiding completely empty positions, but that is an extremely low standard. The bigger problem is roster quality and depth. CPU teams routinely retain extremely low-rated backup players while clearly superior replacement-level players remain available in free agency. For example, there can be usable players around 70 OVR sitting in free agency while teams carry backups in the 50s or low 60s. I also encountered teams entering Year 2 with extremely thin positional groups—for example, Baltimore carrying only three wide receivers. This means the real NFL rosters EA provides gradually deteriorate into poorly constructed CPU rosters. CPU roster logic needs basic safeguards involving: Minimum and preferred depth at every position. Replacement-level talent checks. Free-agent upgrades over clearly inferior rostered players. Age versus development/potential considerations. Scheme fit. Draft investment. Positional value. Existing contracts. Roster balance. Team competitive window. A CPU team choosing a younger 73 OVR player over an aging 76 can be a defensible football decision. A CPU team carrying a player in the 50s while a clearly superior affordable NFL-caliber replacement sits unsigned is not an interesting personnel decision. It is broken roster logic. Draft logic also needs to recognize previous premium investments and positional need so teams do not repeatedly make obviously destructive selections, such as unnecessarily investing premium picks at positions they recently addressed. CPU SALARY-CAP AND CONTRACT MANAGEMENT NEEDS TO SUPPORT THE NEW CONTRACT SYSTEM Adding deeper contract mechanics only improves Franchise if CPU teams can use them competently. The CPU needs to understand multi-year roster construction. When a franchise quarterback receives an enormous extension, the CPU needs to understand how that affects future roster building, restructures, extensions, veteran releases, replacements, and draft priorities. Otherwise, teams with elite quarterbacks eventually become terrible simply because the CPU cannot build around their contracts. If users feel forced to disable the salary cap simply to prevent CPU-controlled organizations from destroying themselves, the underlying roster-management system is not functioning properly. RETIREMENT LOGIC NEEDS TO BE REBUILT — AND COMMISSIONERS NEED AN OVERRIDE This was the most ridiculous result from my Madden 27 testing. After Year 1, T.J. Watt retired. Here was his situation when Madden decided he should retire: Age: 32 Overall: 92 OVR AFTER regression Season result: Pittsburgh reached the Super Bowl Individual result: T.J. Watt WON DEFENSIVE PLAYER OF THE YEAR Madden’s own legacy system: Watt was ranked approximately #2 all-time He was therefore still one of the best active players in football, had just won DPOY, had just participated in a Super Bowl run, remained a 92 OVR player after regression, and was considered one of the greatest players ever according to Madden’s own legacy calculation. Madden randomly retired him anyway. Even more unbelievably, his retirement DID NOT APPEAR IN THE NEW FRANCHISE NEWS SYSTEM. One of the most accomplished players in the entire league—coming off a DPOY and Super Bowl appearance—simply disappeared during the offseason. I only discovered what happened because I noticed Watt was missing and searched through the detailed transaction history. This exposes problems with both retirement logic and the new news system. Recent performance, current OVR, awards, career accomplishments, legacy, age, injuries, contract situation, and team success should heavily influence retirement probability. Unexpected retirements should still be possible. Randomness creates interesting Franchise stories. But a 32-year-old reigning DPOY who remains 92 OVR should have an extraordinarily low retirement probability. And if something that shocking DOES happen, it should be one of the biggest stories in the league news feed. Most importantly: ADD A COMMISSIONER “OVERRIDE RETIREMENT” OPTION. If the simulation produces an unreasonable retirement, commissioners need the ability to reverse it. Something as simple as: Commissioner Tools → Player → Override Retirement / Return for One Season would prevent a questionable RNG result from permanently destroying a player’s career and altering an entire Franchise universe. This is especially important for quarterbacks. Historically, elite NFL quarterbacks frequently play well into their late 30s, with occasional players reaching their early 40s or beyond. Madden has historically retired elite QBs too early, making it difficult for CPU-controlled stars to produce career arcs comparable to real players such as Tom Brady, Peyton Manning, Drew Brees, Ben Roethlisberger, Philip Rivers, Aaron Rodgers, etc. Regression sliders can help users manage rating decline. They cannot fix retirement logic. Commissioners need control over retirement. PLEASE PRIORITIZE THE SIMULATION BEFORE ADDING MORE COSMETIC FRANCHISE FEATURES The new Franchise news, conversations, contract mechanics, personas, presentation, and other additions can be enjoyable. But those systems cannot compensate for a league that does not function correctly underneath them. A news system does not create immersion if a reigning DPOY and historically elite player unexpectedly retires and the news system does not even mention it. A deeper contract system does not improve long-term Franchise if CPU teams cannot manage the resulting contracts. More player progression systems do not improve Franchise if progression produces an unrealistic talent distribution. The foundation has to come first. Franchise players need: Believable simulation statistics. Competent CPU roster construction. Competent free agency and draft logic. Sustainable CPU contract/cap management. Realistic progression and regression. Believable career longevity and retirement logic. Commissioner controls to correct simulation failures when they occur. That is the NFL ecosystem. Everything else should be built on top of it. I do not need Madden to create my stories for me. I do not need Madden to maintain decades of my historical statistics. I do not even need Madden’s legacy score to determine who the greatest players in my Franchise are. I am happy to track those things myself. What I need Madden to do is much simpler: Give me believable NFL statistics to record. Keep the other 31 teams competent enough that playing against them remains immersive. Allow great players to have believable career lengths. Give commissioners the ability to intervene when the simulation produces obviously unreasonable outcomes. Then let us play football. Franchise mode should not require controlling 32 teams, manually repairing depth charts, auditing free agency, manipulating playbooks, disabling the salary cap, adjusting progression/regression, checking transaction logs for unexplained retirements, and repeatedly reloading saves simply to maintain a recognizable NFL. These are not requests for an extraordinarily detailed football-management simulator. They are the basic requirements of an NFL Franchise mode. Please prioritize fixing the simulation underneath Franchise before adding more surface-level features to it.
