Getting slightly upset that the matchmaker keeps stalling on the match found page and then penalizing me for declining it when nothing happens after 10 minutes. Bug report: FS#4370
Yes I do have mods running and no, no I'm not going to disable all of them. I need Hotbuild2 and PA stats. Need them damnit! So not really an option really.
Well if you disable them and suddenly it never breaks then you could report to the authors of the mods so they may be able to fix it. Another thing to try is to have a look at the UI debugger while the issue happens. I describe the debugger here: https://forums.uberent.com/threads/pa-ui-modding-tutorial.68306/#post-1077127 You'll want to check the console of the matchmaking-something scene while the counter is at 0.
Well I've cut all my mods except HB2 and a couple of others, I was going to see how this pans out over the next few days/games as I re-enable the mods. It's not a very consistent bug but I'll certainly get on that ui debugger thing if that would expedite matters?
Well, it broke and just for the record, I found : Uncaught TypeError: Object #<Object> has no method '_trigger' [Blueprint Info Framework] Blueprint info not found in session storage determined current scene name to be main Although it' worth pointing out, I have no idea what I'm doing here :/
The TypeErrors are always there, don't worry about those. And I am not sure how the Blueprint mod could break stuff. And sorry that I wasn't clear early. I meant running PA with --nomods are a test to see if mods are causing this. The --nomods flag causes PA to ignore any mods, so if your problem then persists, then it means it's a vanilla bug and otherwise one of the mods is causing trouble. Since you get an error about the blueprint mod, it means some mods are still active.
those are all normal messages, however the scene name "main" is weird. Is that really the scene that is named matchmaking something? I thought the matchmaker has it's own scene. "main" is some other scene that does not matter for this.
Well, as far as I'm able to tell this is happening because of the PAStats mod. Almost no problems when it's disabled but staring at an idle screen for 20 minutes and repeated hanging and crashing of the matchmaking process when I have it on. Spending 30m playing and 2 hours waiting for something to happen because hangs, crashes and penalty timers is wearing a little thin. It's pretty pointless me bothering with the debugger thing, haven't got the first clue what I'm supposed to be looking at, where, how or why.
I'll try around myself a bit, however those debugger infos would be pretty helpful. Once it happens just click the big blue link that says something about matchmaking (instead of main) and copy paste the stuff from the console here like you did before. I also don't run much code in the matchmaking scene, to be precise 7 simple lines. The hanging happens before you reach the lobby correct? EDIT: random idea: with PA Stats enabled do you ever have problems where you have a hard time joining games? Can you try to enable "ubernet ajax" in the settings > PA Stats tab?
Yes I did save some stuff the last time used it, have no idea where it went, which was a bit annoying. And yes the hang happens during the countdown to accept, the act of clicking accept doesn't always affect the countdown in any way. This *may* be related to tabbing in and out while I wait for the matchmaker to make matches. Then again...
after thinking a few more minutes I think my random idea might be a good one. Since the introduction of the chat in PA Stats there have been a few users with weird issues caused by a bug in PA that is triggered by the chat. The option in the settings is a workaround I wrote for them. Basically the bug makes it impossible for your game to join a game-server, which is exactly what it needs to do when you click accept in the ranked search.
Option in settings? Oh I see it, something about Ajax. Not sure I want to try again for a while though. an hour is quite long enough of a penalty already thank you. It's weird that it can be fine for days, then just nope out for seemingly no reason.
