xzalek25 Posted November 8, 2016 Posted November 8, 2016 Hi, I am trying to start a multiplayer game on OpenRCT2. I am trying to use the latest version and every time I click multiplayer in the menu on the top, the whole game keeps crashing. Why is it crashing? Zach
imlegos Posted November 8, 2016 Posted November 8, 2016 Does a crash report appear when the game crashes? If yes, what does it say A slight bit more info is needed before the problem can be discovered 1
xzalek25 Posted November 8, 2016 Author Posted November 8, 2016 The game doesn't crash on other servers only mines. The crash report is attached in the following image. 1
imlegos Posted November 8, 2016 Posted November 8, 2016 Judging by this report, there was no crash files created, so not gonna bother asking about that. Now it's up to someone who actually understands this to figure out what "Line: 1280" is.
imlegos Posted November 8, 2016 Posted November 8, 2016 Just leave it until someone of greater intelligence regarding OpenRCT2 can address this problem. Also, don't bother replying with something along the lines of "ok"
xzalek25 Posted November 8, 2016 Author Posted November 8, 2016 I sent the problem to one of the administrators.
X7123M3-256 Posted November 8, 2016 Posted November 8, 2016 On 08/11/2016 at 21:17, xzalek25 said: So how should I report that error? Expand Bugs should be reported on the Github issues page. Include your OS, commit hash, the assertion that failed and any errors that were logged to the terminal. On 08/11/2016 at 21:14, imlegos said: Now it's up to someone who actually understands this to figure out what "Line: 1280" is. Expand What do you think it would be? It's the line on which the assertion failure occurred - specifically this one. Looks like an unhandled case in some string formatting code. 2
xzalek25 Posted November 8, 2016 Author Posted November 8, 2016 (edited) @X7123M3-256 what is a commit hash and an assertion failed? Edited November 8, 2016 by xzalek25
xzalek25 Posted November 8, 2016 Author Posted November 8, 2016 On 08/11/2016 at 21:54, X7123M3-256 said: Bugs should be reported on the Github issues page. Include your OS, commit hash, the assertion that failed and any errors that were logged to the terminal. What do you think it would be? It's the line on which the assertion failure occurred - specifically this one. Looks like an unhandled case in some string formatting code. Expand what is a commit hash and an assertion failed
imlegos Posted November 8, 2016 Posted November 8, 2016 On 08/11/2016 at 21:54, X7123M3-256 said: What do you think it would be? It's the line on which the assertion failure occurred - specifically this one. Looks like an unhandled case in some string formatting code. Expand I got that it's where the failure happened, but I just didn't know what that line was (nor did I really feel like looking it up)...
X7123M3-256 Posted November 8, 2016 Posted November 8, 2016 (edited) On 08/11/2016 at 22:00, xzalek25 said: what is a commit hash and an assertion failed Expand The commit hash identifies the commit from which the game was built. It should be displayed in the bottom left corner of the screen when the game starts up, along with the version number and OS. An assertion is a condition that is assumed to always hold at a certain point in the code. It's checked at runtime, and if it is violated then the program immediately terminates. The assertion that was triggered here is just "false" which seems to indicate that this branch was assumed to be unreachable, or possibly that this case isn't implemented. I am not familiar enough with the codebase to know which. Edited November 8, 2016 by X7123M3-256 2
xzalek25 Posted November 8, 2016 Author Posted November 8, 2016 On 08/11/2016 at 22:40, X7123M3-256 said: The commit hash identifies the commit from which the game was built. It should be displayed in the bottom left corner of the screen when the game starts up, along with the version number and OS. An assertion is a condition that is assumed to always hold at a certain point in the code. It's checked at runtime, and if it is violated then the program immediately terminates. The assertion that was triggered here is just "false" which seems to indicate that this branch was assumed to be unreachable, or possibly that this case isn't implemented. I am not familiar enough with the codebase to know which. Expand Did I do it correctly? Look below.
Broxzier Posted November 8, 2016 Posted November 8, 2016 (edited) You forgot to fill in the build you are using. You can find this on the bottom-left corner in the title screen, or in the launcher if you're using it. This number is the most important for debugging. Edited November 8, 2016 by Broxzier 1
xzalek25 Posted November 9, 2016 Author Posted November 9, 2016 On 08/11/2016 at 23:20, Broxzier said: You forgot to fill in the build you are using. You can find this on the bottom-left corner in the title screen, or in the launcher if you're using it. This number is the most important for debugging. Expand Better?
Nubbie Posted November 9, 2016 Posted November 9, 2016 On 09/11/2016 at 01:48, xzalek25 said: Better? Expand No, start the game and see what the commit number is, should be in the bottom left corner with the a combination of letters and numbers, like a934590 1
xzalek25 Posted November 9, 2016 Author Posted November 9, 2016 On 09/11/2016 at 06:25, Nubbie said: No, start the game and see what the commit number is, should be in the bottom left corner with the a combination of letters and numbers, like a934590 Expand 33749cc The folks over there closed my ticket! He didn't help at all and he said there's another case open but it has nothing to do with my issue.
jensj12 Posted November 9, 2016 Posted November 9, 2016 It's the same assertion that failed, but in another part of the game. If the causes are the same (which is likely, as it's the same assertion), fixing one will fix the other too. If the other issue is fixed and your problem still exists, feel free to re-open your issue (or open a new one).
X7123M3-256 Posted November 9, 2016 Posted November 9, 2016 On 09/11/2016 at 12:23, xzalek25 said: 33749cc The folks over there closed my ticket! He didn't help at all and he said there's another case open but it has nothing to do with my issue. Expand This is the issue in question, and as you can see it everything to do with your problem because it's the same bug - assertion failure at line 1280 in localisation.c. There's no point in having two open issues for the same bug, so yours was closed as a duplicate. The original issue remains open, so it's not that this bug will not be fixed, just that the developers already know about it.
xzalek25 Posted November 9, 2016 Author Posted November 9, 2016 Hi, The problem is solved. I reinstalled the game and it's fixed,. Thanks everyone for you help.
Recommended Posts