Adventure levels’ plant seeds reward missing
I don’t know if the game intentionally removed it after the update or it’s a bug but I just played an adventure level for the first time and didn’t recieve 5 plant seeds as usual. Please fix this because I don’t want to play another level to waste a potential reward.
Game not executing input received
Since Season 5, the game routinely fails to execute inputs, from either mouse or keyboard. Could be anywhere from a few seconds, to a few minutes, between each failure. I can confirm the game is receiving the input - example, using the scroll wheel to cycle weapons on the little bird. Weapon doesn't change, but the sound for switching weapons plays. Additionally, I've separately tested other games and even a keyboard logger to verify that there's no missing inputs. Given this occurs numerous times each round, across every fashion of input, makes this game breaking. I have confirmed with at least 4 other PC users that this is happening for them too since S5, and one is experiencing the issue while using a controller. Typical EA/DICE
System Crashes with new 5060ti OC
So I played this game for about 80 hours on my old system when I had a 3060 12gb and it ran just fine. I upgraded my system to a 5060ti oc 16gb and a ryzen 9 5950x. I haven't had ANY issues with any games at all other than Battlefield 6. This is the ONLY game in my library where if I switch screens; even in the main menu it loses display, hardlocks my system, causes it to go into failsafe mode and ramps up my fans to 100% so I have to shut it off via the PSU. They claimed they fixed this issue with the update 2 months ago, and said it revolved around large bodies of water. But it happens ALL the time, even just switching through menu options. Once again this is the ONLY game this happens in. I can sit here with Crimson Desert, WarDogs or Call of Duty running for hours with absolutely no issues. So I know for a fact it is not my system. I haven't been able to play in months due to the issue.IMPORTANT: FC 27 ONE-TWO BUG – ONLY AFFECTS D-PAD USERS (NOT ANALOG STICK USERS)
Dear EA Technical Team, I have finally identified exactly when this problem occurs, and I would really appreciate it if you could reproduce it yourselves before closing this report. This issue specifically affects players who use the D-Pad (directional arrows) to move their players instead of the Analog Stick. I have been playing FIFA/FC for approximately 7 years using the D-Pad, not the Analog Stick. I also use R1 as my Sprint button, and I cannot simply change my playing style after seven years of muscle memory. PLEASE FOLLOW THESE EXACT STEPS TO REPRODUCE THE BUG: Go to Controller Settings. Change your movement control to the D-Pad (directional arrows) instead of the Analog Stick. Change your Sprint button from R2 to R1. Enter a match. Move your player using the D-Pad. Hold down R1 continuously to sprint. Do NOT release R1. While still holding R1 and sprinting, try to perform a normal One-Two / Give & Go using L1 + Pass. WHAT WILL HAPPEN? Instead of performing the normal One-Two, the player triggers the new Run Around / Trigger Run mechanic, making the player run behind and around the player who has the ball. The normal One-Two does not work correctly under these conditions. VERY IMPORTANT: I TESTED THIS MYSELF. When I switch to the Analog Stick for player movement, this problem does not occur. The problem happens specifically when: Movement is controlled using the D-Pad. Sprint is assigned to R1. R1 is continuously held while attempting a normal One-Two. WHY THIS NEEDS TO BE FIXED I have been playing this way for seven years. I cannot simply switch to the Analog Stick because it is extremely difficult for me to change a playing style and muscle memory that I have developed over so many years. I am not asking EA to change the way everybody plays. I am asking EA to make sure that both D-Pad and Analog Stick users can perform the normal One-Two without this control conflict. PLEASE TEST THIS EXACT CONFIGURATION: D-PAD + R1 SPRINT + HOLDING R1 WHILE PERFORMING A NORMAL ONE-TWO. You should be able to reproduce the issue yourselves. Please investigate and fix this problem so that players who use the D-Pad can enjoy the game without being forced to change their controls or relearn seven years of muscle memory. Thank you.
Force feedback disabled or violently throwing the wheel on new update
Everything was completely fine yesterday, but today on v1.25 at random times (seemingly after retrying/resetting a session or a session change) the force feedback breaks and starts violently throwing the wheel from one side to another. Turning the wheelbase off and on sometimes fixes it or just disables the force feedback. The wheelbase is a Fanatec CSL DD. No similar problems on any other game.
BATTLEFIELD 6 SEASON 5
ADDITIONAL TECHNICAL REQUIREMENTS – Beyond Bug Fixes: Technical Transparency, Quality Assurance and Long-Term Game Stability This additional report expands on the technical concerns already submitted regarding Battlefield 6 Season 5. Fixing individual bugs is important, but the development team should also address the underlying processes that allow technical problems to return after major updates. The goal should not simply be to repair the current version. The goal should be to establish a more reliable technical foundation for Battlefield 6. 1. PERFORMANCE REGRESSION MONITORING Every major update should be compared against previous versions. The development team should monitor: Average FPS. 1% low FPS. Frame-time consistency. CPU and GPU utilization. VRAM and RAM consumption. Loading times. Shader compilation. Performance during large-scale destruction. Performance during extended multiplayer sessions. A new update should not introduce measurable performance regressions without investigation and communication. 2. CROSS-PLATFORM PERFORMANCE EQUALITY Xbox, PlayStation and PC should receive dedicated optimization and validation. The objective is not identical graphical settings across different hardware. The objective is consistent gameplay quality, responsive controls and reliable performance within each platform's technical capabilities. 3. HIT REGISTRATION TRANSPARENCY The development team should provide more information about server-side hit registration and synchronization. A dedicated investigation should examine: Server processing delays. Client/server synchronization. Hit confirmation inconsistencies. Packet loss. Latency fluctuations. Network interpolation. Lag compensation. Players need confidence that their actions are accurately represented by the game servers. 4. VISUAL COMPETITIVE READABILITY Visual fidelity should never compromise competitive visibility. Investigate excessive darkness, lighting inconsistencies, visual clutter, smoke density, explosion effects and enemy visibility. Players should be able to identify relevant combat information without removing the visual atmosphere that defines Battlefield. 5. WEAPON BALANCE AND DAMAGE CONSISTENCY Investigate weapon behavior across different network conditions. Review: Damage consistency. Bullet registration. Recoil behavior. Weapon spread. Attachment functionality. Animation synchronization. Differences between weapon statistics and actual in-game behavior. Weapon balancing should be based on measurable gameplay data rather than isolated impressions. 6. ANTI-CHEAT AND COMPETITIVE INTEGRITY Continue improving anti-cheat detection while minimizing false positives. Investigate suspicious gameplay patterns, cheating reports and competitive integrity across all platforms. Players should have confidence that matches are decided by skill rather than unfair external advantages. 7. PATCH VALIDATION AND REGRESSION TESTING Before releasing an update, the development team should validate: Every multiplayer map. Every major game mode. Weapon functionality. Vehicle functionality. Respawn and revive systems. Audio and HUD. Network synchronization. Performance under maximum combat intensity. A fix should not introduce another problem in an unrelated system. 8. PUBLIC TECHNICAL ISSUE TRACKER I strongly recommend that EA maintain a regularly updated public tracker containing: Confirmed issues. Issues currently under investigation. Issues awaiting a fix. Fixed issues. Platform-specific problems. Known workarounds. Relevant patch numbers. This would significantly improve communication between developers and the community. 9. COMMUNITY-BASED REPRODUCTION AND VALIDATION The community should have a clear way to submit reproducible technical reports. Useful information includes: Platform. Game version. Map and game mode. Approximate time of occurrence. Reproduction steps. Video evidence. Network conditions. Whether the problem occurs consistently. Developers could use this information to identify patterns and prioritize fixes. 10. FINAL REQUEST Battlefield 6 deserves a long-term technical improvement strategy. The community does not expect every problem to be resolved immediately. However, it deserves transparency, measurable improvements and consistent communication. Please consider establishing a permanent technical quality program for Battlefield 6, with platform-specific performance validation, regression monitoring, server analysis and a public issue-tracking process. The objective is not simply to release more content. The objective is to build a Battlefield experience that remains stable, optimized, competitive and reliable throughout every season. Content attracts players. Technical quality earns their confidence and keeps the community engaged. Thank you for considering this additional feedback.BATTLEFIELD 6 – SEASON 5
COMPREHENSIVE CROSS-PLATFORM TECHNICAL AUDIT AND PERFORMANCE INVESTIGATION Xbox Series X|S | PlayStation 5 | PlayStation 5 Pro | PC Report date: October 31, 2026 Game version: Season 5 – Siege of Vegas Report category: Technical Issues, Performance, Stability and Constructive Community Feedback 1. INTRODUCTION – THE CURRENT STATE OF SEASON 5 I am submitting this technical report to highlight the problems affecting Battlefield 6 following the release of Season 5. Battlefield 6 has the potential to become one of the best large-scale FPS experiences available. However, the current technical situation raises important concerns regarding performance consistency, visual quality, server reliability, hit registration, audio, gameplay systems and overall stability. These concerns should not be interpreted as an attack against the development team. The purpose is to provide structured, constructive feedback that can help identify technical weaknesses and establish clear priorities for future updates. A major seasonal update should improve the overall experience without introducing regressions into systems that previously worked correctly. The problems described below combine officially acknowledged issues, recent community reports and technical areas that deserve further investigation. Not every reported issue has been independently confirmed across all platforms. 2. PERFORMANCE AND FRAME RATE – ALL PLATFORMS Platforms: Xbox Series X|S, PS5, PS5 Pro and PC. Performance consistency is one of the most important requirements in a competitive FPS. The following problems deserve investigation: Unexpected FPS drops during intense firefights. Frame-time instability and inconsistent frame pacing. Micro-stuttering during movement, aiming and camera rotation. Performance degradation during explosions, smoke, destruction and large-scale battles. Sudden performance drops after respawning. Performance inconsistencies between maps. Possible performance regressions following seasonal updates. Inconsistent CPU and GPU utilization. Potential memory management and asset streaming problems. Why this matters A game can display a high average FPS while still feeling unstable. Frame-time spikes can produce visible interruptions, negatively affecting aiming precision, movement and reaction time. Competitive gameplay requires consistent frame delivery, not simply a high FPS number displayed on screen. Requested improvements Investigate frame-time consistency across all platforms. Compare performance before and after Season 5. Optimize CPU and GPU workloads. Investigate memory allocation and asset streaming. Improve performance during destruction-heavy encounters. Validate performance across every multiplayer map and game mode. Ensure that performance improvements do not reduce visual quality unnecessarily. 3. GRAPHICS, TEXTURES AND VISUAL FIDELITY Platforms: Xbox, PlayStation and PC. Visual consistency is essential to Battlefield's immersive experience. The following areas deserve technical investigation: Delayed texture loading. Objects and environmental details appearing at low resolution before becoming sharp. Buildings, vegetation and environmental assets loading inconsistently. Texture streaming interruptions during fast movement. Visual pop-in at medium and long distances. Inconsistent shadow quality. Lighting transitions that make visibility unpredictable. Possible visual artifacts following updates. Inconsistent image quality between different graphics configurations. Excessive visual noise during explosions and environmental effects. Lighting and visibility Lighting should create atmosphere without compromising gameplay readability. Certain environments, especially darker maps and nighttime combat scenarios, deserve additional testing. Players must be able to distinguish enemies, environmental objects and movement without visual interference caused by excessive darkness, inconsistent exposure or poorly balanced effects. Requested improvements Review lighting and exposure calibration. Improve texture streaming and loading priorities. Optimize shadow rendering. Investigate visual artifacts and object pop-in. Improve visibility in dark environments. Preserve visual fidelity across performance modes. Test long-distance visibility and object rendering. 4. NETCODE, HIT REGISTRATION AND SERVER PERFORMANCE Platforms: Xbox, PlayStation and PC. One of the most frustrating problems reported by players is inconsistent hit registration. Community reports describe situations where shots appear to connect but do not produce the expected hit confirmation. Areas requiring investigation include: Hit registration inconsistencies. Delayed hit markers. Inconsistent damage confirmation. Possible discrepancies between client-side and server-side results. Network interpolation and reconciliation. Rubber-banding. Packet loss. Latency fluctuations. Inconsistent synchronization between players. Why this matters In a competitive FPS, players need confidence that the actions they perform are accurately represented by the server. When the visual feedback and server-confirmed outcome appear inconsistent, the player loses confidence in the game's combat system. This directly affects competitive integrity. Requested improvements Conduct a detailed netcode investigation. Analyze server-side hit registration. Improve synchronization between clients and servers. Review interpolation and lag compensation. Improve network diagnostics. Investigate regional matchmaking and latency distribution. Provide clearer information about server performance. Importantly, hit registration problems should not automatically be attributed to internet connections. Server processing, client synchronization and network conditions must be investigated separately. 5. AUDIO SYSTEM AND SOUND POSITIONING Platforms: Xbox, PlayStation and PC. Audio is fundamental to situational awareness. The Season 5 launch was followed by an officially acknowledged issue that could cause audio to cut out until the game was restarted. A hotfix was released to address that particular problem. However, audio quality deserves broader ongoing testing. Areas to investigate: Temporary audio interruptions. Missing or delayed sound effects. Inconsistent directional audio. Footstep localization. Difficulty distinguishing nearby and distant sounds. Audio masking during explosions. Inconsistent environmental sound levels. Synchronization between visual events and sound effects. Requested improvements Review the spatial audio system. Improve directional sound accuracy. Investigate audio prioritization during intense combat. Test audio consistency across different headsets and platforms. Ensure that critical gameplay sounds remain distinguishable. Players should be able to make reliable decisions using audio information. 6. RESPAWN, REVIVE AND GAMEPLAY SYSTEMS Several gameplay systems deserve particular attention. Officially acknowledged issues include reports of revive prompts failing to appear or activate in Battle Royale modes. Vehicle health regeneration has also been under investigation. Additional community feedback concerns inconsistent respawn behavior. Areas requiring investigation Revive prompts failing to appear. Revive interactions not activating correctly. Delayed interaction responses. Players experiencing abnormal respawn states. Respawn positioning inconsistencies. Vehicle health regeneration taking longer than intended. Inconsistent interaction detection. Requested improvements The development team should review the complete interaction process, from the initial player input to server confirmation. Respawn and revive systems must be reliable because they directly influence squad coordination, match flow and competitive fairness. 7. MAP STABILITY – VEGAS STRIP AND AREA 51 The introduction of new maps should expand the experience without compromising stability. An October 22 hotfix specifically addressed stability improvements on Vegas Strip and Area 51. This demonstrates why map-specific technical validation is important. Areas to investigate: FPS consistency in different map sectors. Texture streaming during rapid movement. Environmental asset loading. Performance around destruction-heavy areas. Lighting consistency. Collision detection. Object interaction. Audio propagation. Map-specific crashes and freezes. The development team should conduct separate performance tests for every map rather than relying exclusively on overall game benchmarks. 8. PC-SPECIFIC PERFORMANCE AND STABILITY PC players operate across a wide variety of hardware configurations. This creates additional optimization challenges. Recent community reports describe performance degradation following Season 5 updates, including lower FPS and frame-time instability. Additional reports describe crashes and complete system freezes. These reports require investigation and should not be considered confirmed universal defects. Areas requiring investigation CPU utilization and scheduling. GPU utilization. VRAM consumption. System RAM consumption. Shader compilation. Shader cache behavior. DirectX-related stability. Driver compatibility. Upscaling technologies. Frame generation compatibility. EA AntiCheat compatibility. Full system freezes. Crashes to desktop without error messages. Requested improvements Test different NVIDIA and AMD GPU generations. Investigate performance regressions following game updates. Review shader compilation and cache behavior. Test multiple CPU configurations. Investigate crashes occurring during matches. Improve error reporting. Validate graphics settings and upscaling technologies individually. Publish recommended configurations for different hardware levels. Performance optimization should not depend on owning the newest or most expensive hardware. 9. PLAYSTATION-SPECIFIC INVESTIGATION PS5, PS5 Digital Edition and PS5 Pro. Community reports on the EA Forums include: FPS drops. Stuttering. Delayed texture loading. Black screens. Unexpected crashes. Performance problems during gameplay. These reports do not establish that every PlayStation player is affected, but they justify further investigation. Requested tests Compare PS5 and PS5 Pro performance. Compare performance before and after Season 5. Test both visual and performance modes. Investigate texture streaming. Examine crashes during multiplayer sessions. Test prolonged gameplay sessions. Validate performance after respawning. Console players should receive a stable and consistent experience without having to rely on repeated troubleshooting. 10. XBOX-SPECIFIC INVESTIGATION Xbox Series X and Xbox Series S. Xbox deserves a dedicated technical validation process rather than being treated as an extension of PC testing. Areas requiring investigation: FPS consistency. Frame-time stability. Texture streaming. Memory management. Lighting and visual effects. Audio consistency. Matchmaking stability. Crashes and unexpected disconnections. Performance differences between Series X and Series S. The Series X and Series S have different hardware capabilities. Optimization should account for those differences while preserving stable gameplay. I also request confirmation that Xbox-specific regression tests are included in the quality assurance process before future seasonal updates are released. 11. USER INTERFACE, HUD AND GAMEPLAY FEEDBACK The interface is not merely decorative. It communicates important gameplay information. Community reports following the Season 5 update mention interface problems and delayed or inconsistent visual feedback. Areas requiring investigation: HUD elements disappearing or displaying incorrectly. Delayed notifications. Hit indicator inconsistencies. Scoreboard updates. Minimap visibility. Interaction prompts. Menu navigation. Incorrect or delayed gameplay notifications. The team should prioritize interface reliability because players depend on immediate and accurate information during combat. 12. MATCHMAKING, SERVER REGIONS AND COMPETITIVE FAIRNESS Matchmaking quality is another important part of the overall experience. Areas requiring continuous monitoring: Excessive matchmaking waiting times. Players being placed on distant regional servers. Unstable latency. Inconsistent lobby population. Unbalanced team composition. Unexpected disconnections. Competitive penalties resulting from technical failures. A fair matchmaking system should consider latency, regional availability and competitive balance. Ranked penalties should also be reviewed when a disconnect is demonstrably caused by a game or server failure. 13. QUALITY ASSURANCE AND UPDATE VALIDATION One of the most important recommendations is to strengthen regression testing. Every seasonal update should undergo comprehensive validation before release. A recommended testing process should include: Performance validation Frame-time measurements. CPU and GPU performance. Memory consumption. Long-duration gameplay testing. Visual validation Texture loading. Lighting. Shadows. Environmental rendering. Visibility at different distances. Network validation Server synchronization. Hit registration. Packet loss scenarios. Regional latency. Gameplay validation Respawn. Revive. Vehicle interactions. Weapon attachments. Matchmaking. Platform validation Xbox Series X. Xbox Series S. PlayStation 5. PlayStation 5 Pro. Different PC hardware configurations. A successful update should improve existing systems without introducing new regressions. 14. PRIORITY LEVELS FOR FUTURE FIXES I recommend the following order of priorities: Priority 1 – Critical Game crashes and freezes. Severe FPS drops. Hit registration inconsistencies. Server synchronization problems. Match disconnects. Priority 2 – High Texture streaming. Lighting and visibility. Audio positioning. Respawn and revive failures. Map stability. Priority 3 – Medium HUD and interface inconsistencies. Delayed notifications. Environmental rendering. Minor visual artifacts. Priority 4 – Continuous improvement Graphics optimization. Performance scaling. Matchmaking refinement. Audio improvements. Cross-platform quality assurance. 15. WHY FIXING THESE ISSUES WILL IMPROVE BATTLEFIELD 6 Resolving these problems would produce benefits beyond simply eliminating bugs. It would: Improve competitive fairness. Increase player confidence in hit registration. Deliver smoother gameplay. Improve visual consistency. Strengthen immersion. Reduce frustration caused by crashes and disconnects. Improve squad coordination. Increase the accessibility of stable performance across hardware configurations. Improve player retention. Strengthen the Battlefield community's confidence in future updates. A technically stable game is also a more enjoyable game. New content is important, but technical quality is what keeps players coming back. 16. REQUEST TO DICE AND ELECTRONIC ARTS I respectfully request that the development team: Acknowledge the main technical concerns raised by the community. Publish an updated list of known issues. Identify which problems are confirmed, under investigation or resolved. Provide more transparent information about planned fixes. Investigate platform-specific performance regressions. Improve cross-platform testing. Prioritize critical gameplay and server issues. Continue monitoring community feedback after every patch. I also encourage the team to communicate which fixes are already implemented and which still require additional development. Players appreciate transparency, even when a problem cannot be resolved immediately. 17. FINAL STATEMENT – CONSTRUCTIVE FEEDBACK FROM THE COMMUNITY Battlefield 6 has the foundation to become an exceptional FPS. Its large-scale battles, environmental destruction, maps, vehicles, squad mechanics and overall gameplay identity provide something special within the FPS genre. However, technical consistency must remain a priority. The community is not asking for perfection overnight. We are asking for consistent improvements, transparent communication and a development process that protects the quality of the game. A new season should represent progress, not introduce new frustrations into systems that were previously working. I hope this report reaches the appropriate technical and development teams and contributes to a more stable, optimized and competitive Battlefield 6 across Xbox, PlayStation and PC. The objective is simple: make Battlefield 6 technically stronger, more consistent and worthy of the community that continues to support it. Thank you to the Battlefield development team for reviewing this feedback. #Battlefield6 #Season5 #DICE #EA #Performance #Optimization #HitRegistration #Netcode #Xbox #PlayStation #PC #TechnicalIssues #CommunityFeedbackController not being recognized by FC 27
I've tried every troubleshooting step for this, but when I enter the game via the EA App, my controller doesn't get recognized on the settings file and it only shows KBM options. I use a Dualsense controller via USB, and I tried to contact EA support but they're not helpful at all. Anyone got a fix? heres all the stuff i tried: Tested the controller in other games and on PC (it works everywhere else) Checked Windows Device Manager. The controller is detected correctly. Checked the USB connection using USB Device Tree Viewer Tested Windows game controller settings while FC 27 was running. The controller still works there. Renamed/reset the FC 27 local configuration folder. Tested with Steam completely closed. Checked Steam Desktop Layout settings. Confirmed that I do not use DS4Windows, DSX or other controller emulation software. Restarted FC 27 with the controller already connected. Tried using only the controller when starting the game. Confirmed that the issue started after a FC 27 game update. does ANYONE have a fix? I really need help
