- Thread starter
- #31
༺Ƥeຮ༻
Championship
- 13 July 2020
Small PES 2021 online emulator progress update.
Last time I posted, the client was only reaching the Terms of Use / Privacy Policy stage. Since then, the project has moved quite a bit further.
The emulator now gets through the early online flow, including the agreement screens, login/account responses, server list/account handling, and it reaches the Create User Data / Profile screen.
Current state:
Terms / Privacy Policy: passed
Login / account flow: passed
Create User Data screen: reached
Profile creation request: accepted
Current blocker: final post-profile confirmation / transition
After pressing OK on the created user data screen, the game enters the next loading phase. It waits for a while, keeps the connection alive for some time, and eventually disconnects with the “connection to the server was lost” message, and that is for the last 3-4 days....
The expected flow should be:
Create User Data
→ OK
→ loading
→ User Data/Profile created successfully
→ Live Update
→ Main Online Menu
The current flow is:
Create User Data
→ OK
→ loading
→ heartbeat(s)
→ disconnect
We have also been doing a lot of reverse engineering around this part. The focus is now on the internal post-profile finalization logic, not the basic login anymore.
Some of the important areas currently being traced are:
FUN_140FE0370 - post-player-data / profile flow gate
FUN_1411E4390 - slot completion polling
FUN_1411E3BF0 - slot manager state machine
FUN_14121C350 - internal event queue pump
FUN_14121D6A0 - event handler path
FUN_1412402B0 - final slot/profile clear callback
The simplified finding is this:
The game accepts the created profile,
but the internal profile slot never reaches its final completed state.
Because of that, the client keeps waiting instead of showing the “profile created successfully” popup and moving on to Live Update.
We have already tested and rejected a few ideas, including extra route-transition commands and synthetic server-pushed events. Those did not change the behavior, so the next work is focused on identifying the real trigger that makes the client finalize the created profile internally.
So yes, progress is slow, but it is real progress. We are much further than the Terms screen now — the blocker is deep inside the post-profile finalization / slot-state logic. Nobody says that it will be easy, fast, or that success is guaranteed.
Last time I posted, the client was only reaching the Terms of Use / Privacy Policy stage. Since then, the project has moved quite a bit further.
The emulator now gets through the early online flow, including the agreement screens, login/account responses, server list/account handling, and it reaches the Create User Data / Profile screen.
Current state:
Terms / Privacy Policy: passed
Login / account flow: passed
Create User Data screen: reached
Profile creation request: accepted
Current blocker: final post-profile confirmation / transition
After pressing OK on the created user data screen, the game enters the next loading phase. It waits for a while, keeps the connection alive for some time, and eventually disconnects with the “connection to the server was lost” message, and that is for the last 3-4 days....
The expected flow should be:
Create User Data
→ OK
→ loading
→ User Data/Profile created successfully
→ Live Update
→ Main Online Menu
The current flow is:
Create User Data
→ OK
→ loading
→ heartbeat(s)
→ disconnect
We have also been doing a lot of reverse engineering around this part. The focus is now on the internal post-profile finalization logic, not the basic login anymore.
Some of the important areas currently being traced are:
FUN_140FE0370 - post-player-data / profile flow gate
FUN_1411E4390 - slot completion polling
FUN_1411E3BF0 - slot manager state machine
FUN_14121C350 - internal event queue pump
FUN_14121D6A0 - event handler path
FUN_1412402B0 - final slot/profile clear callback
The simplified finding is this:
The game accepts the created profile,
but the internal profile slot never reaches its final completed state.
Because of that, the client keeps waiting instead of showing the “profile created successfully” popup and moving on to Live Update.
We have already tested and rejected a few ideas, including extra route-transition commands and synthetic server-pushed events. Those did not change the behavior, so the next work is focused on identifying the real trigger that makes the client finalize the created profile internally.
So yes, progress is slow, but it is real progress. We are much further than the Terms screen now — the blocker is deep inside the post-profile finalization / slot-state logic. Nobody says that it will be easy, fast, or that success is guaranteed.