Forum Discussion

t0nyBF's avatar
t0nyBF
Seasoned Novice
2 years ago

Re: [FIXED] S6 - Patch 6.0 & 6.1 Causes Mouse Input Issues

It looks like its an CPU issue. The game can't handle now (After the Update) Cpu's with 8 cores or more. So you will have to limit the EA App correct Affinity to 6 or 7 cores. This should fix the Issue for now.

Still Dice needs to do something about that.

20 Replies

  • @t0nyBF  huh? We can fix it on our own somehow you are saying? limit the cores of the EA app? how?

    edit: anyway I now have both bugs battling each other, the bug I originally had since S6 started, mouse sensitivity jumping 10x every few minutes randomly, turning me around, etc. plus this new 6.1 bug of mouse becoming laggy, stuck, turning the wrong direction, moving on its own, etc. I can hardly ever get a moment of control over my mouse now. Sucks that its happening over the limited time event as well.

  • t0nyBF's avatar
    t0nyBF
    Seasoned Novice
    2 years ago
    @LaChup Task Manager > Details > EA App > affinity > and there you select only 6 or 7 cores/threads as usable.

  • @t0nyBF thanks, will this limit the performance of the actual BF game too or this is only "limiting" the EA app itself?
  • MightyDavidovsky's avatar
    MightyDavidovsky
    Rising Novice
    2 years ago

    When you say EA APP, if you mean EADesktop.exe Does not work, just tried it.

  • LaChup's avatar
    LaChup
    2 years ago

    I just tried this on EADesktop.exe in the task manager Details tab. 
    It does seem to have fixed my original S6 bug of my mouse sensitivity jumping 10x every few minutes for a few seconds. But I still have the newer 6.1 bug of laggy aiming every few minutes, maybe less frequent than before, but still happening.

  • @t0nyBF Ea app?
    And threads ≠ cores.
    if u uncheck 1 of 2 threads(0,1 - 1 core, 3,4 -2second core ect), this means that u exclude 1 core from the process.
    So what exactly we should try to do?
  • t0nyBF's avatar
    t0nyBF
    Seasoned Novice
    2 years ago
    @LaChup Yes it will limit the cores the game is using. So you will have less performance.
  • why should worth it if i loss lot of performance? Then it will be stuttering the game because of less cores :D 

  • t0nyBF's avatar
    t0nyBF
    Seasoned Novice
    2 years ago

    @purenrg12345Nowdays games don't use more than 6 cores. 8 cores is perfect and really enough for gaming. But yeah nobody said you have to do that method. They need to fix it anyway.

  • KGB-LtxRaven's avatar
    KGB-LtxRaven
    Seasoned Newcomer
    2 years ago

    This can't be true, my buddy has a 4 core cpu. Same issue is happening to him.

    Funny enough it happened at the same time with him and I.  Maybe server related? doesn't happen in the menus.

  • @AnfarilI turned raw mouse input on now, and now I no longer get my sensitivity jumping up x10 every few minutes and now get what everyone else originally had with S6 update. Now my sensitivity becomes super low every few minutes, which I think is a bit of improvement, not ideal though still lol. At lease limiting the CPU Processors via Task Manager from 24 to 7 removed the lag/ stutter aim issues I was also getting on top of this other sensitivity bug.

  • I have had the same issue since November 1st.

    I had occasional mouse delay earlier (as in before Nov 1st), where the mouse sensitivity would reduce by 90% for a few seconds. Often, this happened when ADSing close to an enemy - so I suspect that was related to some hidden auto-aim.

    After Nov 1st, I have started getting complete lockouts. The mouse does not respond to any input, and if I were firing while it happened, the firing button would be stuck.
    In other words, when timed "correctly", I can take my hand off my mouse, and the gun will continue firing.

    I have timed the lockouts for a few games, and they are extremely consistent.

    Based on over 30 samples, they happen roughly every 55.5 seconds +/- 1 seconds due to human reaction on the stopwatch.

    If it matters, I am running the game with quality settings on low and lower resolution due to the bad intermittent lag it had last month (and probably still does. I never went back).

    While writing parts of this post, I alt-tabbed out of the game. I can confirm the problem persists in Windows while the game runs and at the same interval. As soon as I closed the game, the problems stopped.

    (I have stripped down the DXDiag log since my message keeps getting auto-deleted).
    ------------------
    System Information
    ------------------
    Operating System: Windows 11 Education 64-bit (10.0, Build 22621) (22621.ni_release.220506-1250)
    Language: English (Regional Setting: English)
    System Manufacturer: System manufacturer
    System Model: System Product Name
    BIOS: 3801 (type: UEFI)
    Processor: AMD Ryzen 7 5800X 8-Core Processor (16 CPUs), ~3.8GHz
    Memory: 32768MB RAM

    ---------------
    Display Devices
    ---------------
    Card name: AMD Radeon RX 5700 XT

  • UP_Jaskaman's avatar
    UP_Jaskaman
    Seasoned Hotshot
    2 years ago

    I played yesterday, no any mouse lags issues, I played today, It was nearly unplayable because of constant mouse lags. I have never experienced this kind of problem with BF2042. I tried to fix it  by known tricks but none worked. 

  • @LaChup Now we are in the same boat=)
    i was also confused with this x10 sens. Bugfield.....
  • KrynoLen's avatar
    KrynoLen
    Rising Traveler
    2 years ago
    @LaChup This actually worked for me. it got rid of the stuck/laggy aim! no more freezes!

Featured Places