-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The game window never shows up... #377
Comments
I have the same problem.
|
I don't see any issue in this log. also you can use our paste site https://aofpaste.com what launcher are you using? how much ram is allocated? is there a crash log? can someone post a full log? |
The log ends here. |
5GB ram allocated |
This is the full log, it looks the same as the one my friend sent me, the game just doesn't load. The launcher my friend and me are using is Plain Craft Launcher 2, 7GB of ram is given. There is no actual crash log, this is what the launcher produces after cancelling launch. |
This is indeed a genuine issue, and it seems to be caused by KubeJS, Rhino. https://aofpaste.com/vitutoxohi.yaml As this log snippet shows, if for some reason Rhino won't finish it's socket connection to something, the launch will completely stall right after the 'Done in ###.##ms' message in the log output. If one is able to successfully break the socket connection Rhino made, loading execution will continue as normal and the game will load. In the log above, I was able to get Rhino to break in just a couple minutes, but sometimes it will wait for hours or seemingly longer if left alone without tampering. Tested with PolyMC. |
Thanks a lot for the information! Rhino is indeed the cause. My friends and I solved this problem according to an issue of Rhino (KubeJS-Mods/Rhino#26). |
Update: Their rendering went wrong and they gave up trying. However it's probably on me because I forgot to redownload mapping before sharing the file. Anyway, I believe this is the solution. |
A friend had this problem but it seemed that not enough ram was allocated. |
That happened to me, too. |
This problem happens to some of my friends.
When they attempt to launch the game, the window never appears (after more than half an hour). There is no crash, just game not seems to be running. Java is not taking up any CPU usage.
We are using the same launcher, but mine works completely fine. Has anyone else encountered the same issue?
The text was updated successfully, but these errors were encountered: