The "game is null" error
-
I played FAF normally, but at one point after the 2024.v1 update, I could not and cannot create a game and cannot connect to the game. Replays work fine, and if you run the game separately, then it works. I have a licensed steam game. An endless connection and at the same time, no matter how long I wait for the connection to end, the RAM used will always remain at the same level.
Client Version: 2024.1.1
java.lang.NullPointerException: Cannot invoke "com.faforever.client.domain.GameBean.getTitle()" because "game" is null
at com.faforever.client.game.GameRunner.askForGameRate(GameRunner.java:425)
at com.faforever.client.game.GameRunner.handleTermination(GameRunner.java:417)
at java.base/java.util.concurrent.CompletableFuture$UniAccept.tryFire(CompletableFuture.java:718)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:614)
at java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:914)
at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188) -
@mukatim Go to top left menu > Settings > Notifications > After Game Review > Uncheck. Some users have reported issues creating games & it seems that's the cause, which is under investigation.
-
It didn't help. Now I don't get this error when I cancel the connection. When I wait too long to create a game. He writes that the connection is too long.
-
@mukatim In the FAF client, go to the top left menu > Settings:
- General > Write ICE Log File > check,
- Forged Alliance Forever > Use FAF Debugger when starting Forged Alliance > check > click "Get the latest version of the debugger",
- Allow the ICE adapter to use IPv6 > unchecked,
- Preferred Coturns for ICE > select only Global,
Next, quit the client (check Task Manager). Once it's completely closed, open the client again & play.
The next time you join a game & have connection issues, please click the Reply button at the bottom between the
(View) icon & the "Mark unread" button. Next, go to client > top left menu > Show logs folder > logs > sort by Date Modified, then drag/drop these files into the Reply message window so those that can help (not me) have that data to look at:- client.log file (the Text Document file without the date),
- ice-adapter.log & advanced-ice-adapter.log (both in a separate folder)
- If the game actually launched, then also the most recent game_21xxxxxx.log file (should be of the last game that had the issue)
-
client.log advanced-ice-adapter.log ice-adapter.log
These instructions didn't help either, unfortunately, thanks for the help. -
hello. same issue
client.log
advanced-ice-adapter.log
ice-adapter.log
game_21638094.log
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login