Possible Bug with RCA

I am running into a similar issue, as I mentioned in a discussion post earlier, and I want to add it here;

I'm running into situations where I match the CA with the RCA (after I edited some of the stats) and within an in-game month, most of the player stats drop in game. As a result, the shown RCA is actually lower than the CA. This difference between these two is different for each player, For some players this can be zero (meaning the stats don't drop after editing them) and for some players it can be up to 10 (See images down below). I have a player who does not drop in stats after I matched his CA with the RCA.

Would this be caused by the fact that the RCA is not calculated / shown correctly?

Additionally, I don't think checking the "match CA with RCA" changes anything with this problem.

Example explanation (steps in relation to the images):

- Player stats/abilities were edited to have a RCA of 149. I matched the CA with it by manually entering it. So the CA was also set to 149.

- Player stats dropped after a bit of in-game time and FMRTE now shows a RCA of 139.

- If I try editing it again, same thing keeps happening. For this player, the difference between RCA and CA seems to be reverting to 10.

So to be clear: The attributes I edited dropped back after a bit of in game time, after I matched the CA with the RCA that was given to me by editing the attributes. The steps are explained here. So to me it seems that there is difference between the CA and RCA for some players that are constant, and as a result will downgrade the player over time when the RCA and CA are set the same. I think the game recognizes the (edited) CA is too low, compared to the (edited) abilities of the player, thus downgrades them in the next training report (even though the RCA and CA have been matched).... To me the most logical explanation would be that the RCA is wrongly calculated, and it is in most cases actually displaying a number that is too low.

Previous post for reference: 

Game version: FM 22.2.0.0

FMRTE version: FMRTE 22 Build 16

Hello,

Regarding the PA < CA bug, yes when the option `Match CA with RCA` is enabled, FMRTE should also increase PA so that we won't have a lower PA.

About the accuracy of RCA, we don't know the formula that the game uses, so FMRTE has it's own formula to calculate RCA, and as a result it's expected that the value displayed in FMRTE might be slightly different from the one visible in IGE.

We could try to improve the formula that we use but it would take way too much time so honestly I don't have any plans to do it, but, of course, I'm open to any suggestion from the community, about how to improve the formula to make it more accurate.

To make this discussion easier for everyone to follow, I will re-open the following topic, and I will post in there (later this week) more details about how FMRTE is currently calculating RCA.

Cheers

@culturedleftfoot @Mark Janssen 👆 (forgot to mention you guys, I'm doing it now, so that you receive a notification 😅)

27 minutes ago, BraCa said:

Hello,

 

Regarding the PA < CA bug, yes when the option `Match CA with RCA` is enabled, FMRTE should also increase PA so that we won't have a lower PA.

 

About the accuracy of RCA, we don't know the formula that the game uses, so FMRTE has it's own formula to calculate RCA, and as a result it's expected that the value displayed in FMRTE might be slightly different from the one visible in IGE.

 

We could try to improve the formula that we use but it would take way too much time so honestly I don't have any plans to do it, but, of course, I'm open to any suggestion from the community, about how to improve the formula to make it more accurate.

 

To make this discussion easier for everyone to follow, I will re-open the following topic, and I will post in there (later this week) more details about how FMRTE is currently calculating RCA.

 

 

Cheers

Alright, thanks for the response. Even though it's not something that might be fixed soon or fixable in the long run, I appreciate the insight from you guys' perspective. The bug is not a big deal at all, it's just something that can be very confusing and annoying to work with. Unfortunately I don't know enough about the CA calculations etc. to be able to contribute.... Nevertheless, I'm looking forward to whatever happens regarding this bug. Any additional insight is greatly appreciated.

Cheers

Thanks for the update👍