Thygrrr#26219
My feedback
3 results found
-
unable to submit deck friendly play
-
2.png 2924 KB -
1.png 2555 KB -
Screenshot 2023-12-14 125049.png 686 KB -
asdasdasdwqa.PNG 579 KB -
Log20231213_220705.log 1003 KB -
MTG Screenshot.docx 660 KB -
IMG_0001.png 2918 KB -
IMG_0002.png 1869 KB -
Log20231212_032331.log 4 KB -
Log20231211_195304.log 161 KB -
Log20231210_182824.log 1285 KB -
Log20231210_155800.log 173 KB -
pick deck.png 2642 KB -
vs screen.png 2510 KB -
wait for opponent.png 1710 KB -
draw screen.png 1993 KB -
Log20231210_185338.log 2690 KB -
Log20231210_173010.log 10 KB -
Screenshot_20231209-223936.png 2197 KB -
Screenshot_20231209-223919.png 2122 KB -
Log20231208_214916.log 22 KB -
image (2).png 186 KB -
image (1).png 196 KB -
image.png 269 KB -
Captura de pantalla 2023-12-07 180758.png 1991 KB -
Captura de pantalla 2023-12-07 175515.png 2753 KB -
Captura de pantalla 2023-12-07 175429.png 2458 KB -
Captura de pantalla 2023-12-07 175424.png 2770 KB -
Captura de pantalla 2023-12-07 175200.png 3070 KB -
Captura de pantalla 2023-12-07 180746.png 1587 KB -
Captura de pantalla 2023-12-07 180721.png 1982 KB -
Captura de pantalla 2023-12-07 180734.png 1591 KB -
Captura de pantalla 2023-12-07 180406.png 453 KB -
IMG_0002.jpeg 276 KB -
UTC_Log - 12-03-2023 20.03.10.log 1252 KB -
Screenshot_20231124-111904.png 630 KB -
Screenshot_20231203-102603.png 831 KB -
arenaded.png 1318 KB -
Screenshot_20231130_135310_Magic.jpg 495 KB -
Screenshot_20231130_135319_Magic.jpg 1264 KB -
Log20231127_200747.log 17 KB -
Screenshot_20231126-193055_Magic.jpg 424 KB -
Log20231125_235023.log 14227 KB -
Log20231124_112359.log 3 KB -
Screenshot 2023-11-24 112243.png 4482 KB -
Screenshot 2023-11-24 112131.png 4431 KB -
Log20231117_215547.log 3 KB -
Player-prev.log 89 KB -
Player.log 2275 KB -
Screenshot_20231109_124736_Magic.jpg 717 KB -
Screenshot_20231111_085002_Magic.jpg 108 KB -
Screenshot_20231111_084919_Magic.jpg 410 KB -
image_2023-11-09_201821375.png 125 KB -
image_2023-11-09_201749432.png 78 KB -
image_2023-11-09_201728976.png 146 KB -
Log20231109_174402.log 3579 KB -
Log20231105_063842.log 273 KB -
Log20231102_225731.log 3 KB -
Log20231031_095251.log 5294 KB -
Desktop 10-26-2023 11-40-23 PM-471.png 328 KB -
Desktop 10-30-2023 11-11-46 PM-930.png 1810 KB -
Desktop 10-30-2023 11-11-53 PM-10.png 829 KB -
Desktop 10-30-2023 11-12-12 PM-756.png 582 KB -
Screenshot_20231030_223302_Magic.jpg 419 KB -
Screenshot_20231030_223230_Magic.jpg 1029 KB -
Screenshot_20231030_223238_Magic.jpg 514 KB -
C367E4AF-6A12-4817-B747-6FC6E4261A6B.png 1336 KB -
Screenshot 2023-10-29 205956.png 43 KB -
IMG_2830.jpeg 2060 KB -
Log20231028_182646.log 4 KB -
Screenshot 2023-10-28 103915.png 684 KB -
Screenshot 2023-10-28 103905.png 704 KB -
Error Screenshot.jpg 125 KB -
Connection lost.jpg 151 KB -
Log20231027_233344.log 14 KB -
Screenshot 2023-10-26 212327.png 529 KB -
Post failed connection.png 2185 KB -
Waiting for server.png 978 KB -
Cancel Challengs.png 751 KB -
Connection Lost.png 724 KB -
Network Error.png 718 KB -
Capture.PNG 1475 KB -
Capture d’écran (15).png 769 KB -
Screenshot 2023-10-25 220240.png 763 KB -
Log20231025_220327.log 80 KB -
Screenshot (47).png 509 KB -
Screenshot (46).png 487 KB -
MTG Friend Challenge Not Working.png 893 KB -
Untitled1.png 604 KB -
Untitled2.png 62 KB -
Untitled.png 1508 KB -
Log20231021_215116.log 997 KB -
Screenshot (28).png 736 KB -
Log20231021_150554.log 3 KB -
Screenshot_20231020_231859_Magic.jpg 477 KB -
Log20231020_151028.log 10 KB -
Log20231019_204834.log 3 KB -
IMG_2688.jpeg 2099 KB -
Screenshot 2023-10-19 171705.png 8 KB -
Screenshot 2023-10-19 171529.png 1290 KB -
Screenshot 2023-10-19 171540.png 798 KB -
Screenshot 2023-10-19 171622.png 855 KB -
Screenshot 2023-10-19 171653.png 62 KB -
Screenshot 2023-10-19 171703.png 19 KB -
Log20231018_194949.log 1263 KB -
16976566533968431715895776992691.jpg 3271 KB -
Log20231018_123116.log 3 KB -
Screenshot 2023-10-16 at 3.02.15 PM.png 257 KB -
IMG_0248.png 1490 KB -
Screenshot_20221228-033943_Magic.jpg 741 KB -
Log20221014_124209.log 64 KB -
Log20220727_183820.log 12 KB -
Log20220511_182901.log 25 KB -
MTGA 4-5-2022 14_44_20_small.png 2229 KB -
MTGA 4-5-2022 14_44_01_small.png 3467 KB -
MTGA 4-5-2022 14_43_34_small.png 1046 KB -
Log20220312_080916.log 7 KB -
FHONe1iXwAkYIXR.jpg 306 KB -
Log20211002_013242.log 13 KB -
Log20210916_103739.log 11 KB -
4 opponents screen.png 2282 KB -
5 opponents error.png 359 KB -
3 stuck on screen.png 601 KB -
2 unable to submit.png 198 KB -
1 direct, tournament mode.png 645 KB -
Friend challange pt2.png 2072 KB -
Friend challange.png 183 KB -
Friend challange pt2.png 2072 KB -
Friend challange.png 183 KB -
Log20210825_200012.log 78 KB -
Log20210607_115301.log 302 KB -
Log20210319_230830.log 15 KB -
Log20201217_215006.log 35 KB -
Log20201020_144924.log 1751 KB -
Log20201020_144924.log 1751 KB -
Log20201020_144924.log 1751 KB -
Log20200427_173248.log 199 KB
1,229 votesAn error occurred while saving the comment An error occurred while saving the comment Thygrrr#26219 commented
When the error occurs, even after a restart of the client, I can often not log in or stay connected for the first relaunch.
Only 2nd relaunch works. PLEASE FIX THIS. I want to play with my brother. Ranked and Play queue is boring.
An error occurred while saving the comment Thygrrr#26219 commented
It got WORST with the recent release.
As a test, I tried to turn of IPv6, that didn't do anything.Attached is a log file that shows the timeout in line 303
[Social.Chat] Received message prefixed with challenge command sequence, ignoring.
Timeout
[UnityCrossThreadLogger]==> LogBusinessEvents {"id":"e7fe236e-30d2-40cf-81e4-4ba86e612a0a","request":"{\"Type\":1912,\"TransId\":\"e7fe236e-30d2-40cf-81e4-4ba86e612a0a\",\"Payload\":\"{\\\"Title\\\":\\\"Network Error\\\",\\\"CurrentSceneName\\\":\\\"Home\\\",\\\"Duration\\\":\\\"00:00:02.4489807\\\",\\\"Message\\\":\\\"Unable to submit deck. Please try again later.\\\",\\\"EventType\\\":31,\\\"EventTime\\\":\\\"2023-11-16T19:40:23.971392+01:00\\\"}\"}"}
[Social.Chat] Message received by recipient.
[Social.Chat] Canceled challenge to Jazzman: Canceled
An error occurred while saving the comment Thygrrr#26219 commented
Among friends and other users, we have the recurring, intermittent error that we cannot play Direct Challenge matches against friends in our friend list.
Bug Description:
In a Direct Challenge, the "Waiting for Server" spinner upon clicking play (after deck selection) lasts longer than usual (normal is < 500 ms), usually around 3-5 seconds.
Then a popup informs **"Network Error: Unable to submit deck. Try again later"**.Frequency:
This bug occurs persistently, and has begun occurring in the last 2 weeks. At least one of (us) four players appears to be affected on any given evening, for the majority of that evening. More people seem affected, see reddit.com/r/MagicArenaReproduction:
1. Challenge a friend on your friends list to a direct match, Bo3 or Bo1.
2. The error occurs after Deck Selection. If it doesn't occur, it may be possible to play a number of games without encountering it. Once it has occurred once, it will keep occurring.Observations:
The bug does NOT affect normal Play Queue and Ranked Queue.After closing the "Network Error: Unable to submit deck. Try again later", popup, MtG Arena is in a broken connection state afterwards, and generally requires restart to play even non-challenge games. The UI may present as if choosing another deck is possible, but it won't work. Sometimes, you get the "Reconnect" dialog for connection loss.
Once the bug has occurred, for a reasonably long amount of time (hours, not minutes), it is impossible to play direct challenge games on the affected computer. We have, so far, not been able to successfully play a single game including an affected player on the same day.
The next day, it may be fine. It may also have been fine earlier the same day, often up to the very moment of first failure.
This bug can occur in 3 flavors:
- Challenger experiences the bug (other player will be in Waiting for Opponent screen until forced draw, cancel button does not work)
- Challengee experiences the bug (other player will be in Waiting for Opponent screen until forced draw, cancel button does not work)
- BOTH experience the bugIt appears random as to who is affected. We only tested in the afternoon and evenings CET.
The bug has been "cycling" beetween the four of us, but sometimes two of us had it, and it also occurs between other pairs of players (see reddit).
Logs:
I don't have a log file at the moment (becuase the bug is not reproducible on my machine today - but on a friend's machine, it is, we literally can't play!). The logs themselves don't say much - literally just "Timeout" after the Social Component mentioned the incoming challenge request.Stuff I can personally confirm/reproduce: This exact bug keeps recurring for at least 4 users so far, on very different systems. Likely many more are affected, just look for "unable to submit deck" on reddit.com/r/MagicArena . I can say that all our computers and major or mid-size ISPs are in Germany, and although I use 1.1.1.1 as DNS, the others use their ISP's default DNS. (We assumed this to be some sort of routing issue.)
Workarounds do not seem to exist:
- Router restart doesn't help.
- Computer restart doesn't help.
- Restarting Arena doesn't help.
- netsh winsock reset and ipconfig /renew /all won't help.
- selecting a different deck does not help, in fact, a deck that was perfectly fine to play may encounter the bug just as well, and then be no longer able to "Submit".
- windows firewall reset won't help
- superstition remedies such as resetting sleeves or avatars do not help, regardless of what people on Reddit claim. (there may have been a bug in the past that had this issue)An error occurred while saving the comment Thygrrr#26219 commented
Among friends and other users, we have the recurring, intermittent error that we cannot play Direct Challenge matches against friends in our friend list.
Bug Description:
The "Waiting for Server" spinner upon clicking play (after deck selection) lasts longer than usual (normal is < 500 ms), usually around 3-5 seconds.Then a popup informs "Network Error: Unable to submit deck. Try again later".
Frequency:
This bug occurs persistently, and has begun occurring in the last 2 weeks. At least one of (us) four players appears to be affected on any given evening.Reproduction:
1. Challenge a friend on your friends list to a direct match, Bo3 or Bo1.
2. The error occurs after Deck Selection. If it doesn't occur, it may be possible to play a number of games without encountering it. Once it has occurred once, it will keep occurring.Observations:
The bug does NOT affect normal Play Queue and Ranked Queue.After closing the "Network Error: Unable to submit deck. Try again later", popup, MtG Arena is in a broken connection state afterwards, and generally requires restart to play even non-challenge games. The UI may present as if choosing another deck is possible, but it won't work. Sometimes, you get the "Reconnect" dialog for connection loss.
Once the bug has occurred, for a reasonably long amount of time (hours, not minutes), it is impossible to play direct challenge games on the affected computer. We have, so far, not been able to successfully play a single game including an affected player on the same day.
The next day, it may be fine. It may also have been fine earlier the same day, often up to the very moment of first failure.
This bug can occur in 3 flavors:
- Challenger experiences the bug (other player will be in Waiting for Opponent screen until forced draw, cancel button does not work)
- Challengee experiences the bug (other player will be in Waiting for Opponent screen until forced draw, cancel button does not work)
- BOTH experience the bugIt appears random as to who is affected. We only tested in the afternoon and evenings CET.
The bug has been "cycling" beetween the four of us, but sometimes two of us had it, and it also occurs between other pairs of players (see reddit).
Logs:
I don't have a log file at the moment (becuase the bug is not reproducible on my machine today - but on a friend's machine, it is, we literally can't play!), but it doesn't say much - literally just "Timeout" after the Social Component mentioned the incoming challenge request.This bug keeps recurring for at least 4 users so far, on very different systems.
All our computers and (different, major and mid-size) ISPs are in Germany, though I use 1.1.1.1 as DNS, not sure about the others but they usually use their ISP's default DNS. We assumed this to be some sort of routing issue.
Workarounds do not seem to exist:
- Router restart doesn't help.
- Computer restart doesn't help.
- Restarting Arena doesn't help.
- netsh winsock reset and ipconfig /renew /all won't help.
- selecting a different deck does not help, in fact, a deck that was perfectly fine to play may encounter the bug just as well, and then be no longer able to "Submit".
- superstition remedies such as resetting sleeves or avatars do not help, regardless of what people on Reddit claim. (there may have been a bug in the past that had this issue)Thygrrr#26219 supported this idea ·
-
-
Cards changing during drafts
-
no_memory.jpeg 132 KB -
p3p15.jpeg 66 KB -
Log20220526_193408.log 4326 KB -
Untitled.png 2224 KB -
Log20220526_183045.log 33280 KB -
Log20220526_182750.log 4654 KB -
Log20220526_000524.log 31 KB -
mtga bug.jpg 796 KB -
Screenshot_20220525-144120_Magic.jpg 983 KB -
photo_2022-05-24_12-15-25.jpg 112 KB -
photo_2022-05-24_12-15-46.jpg 106 KB -
Log20220523_140106.log 27 KB -
1E4443C5-F9F6-478F-AE32-AB4D9FB74077.jpeg 3983 KB -
Log20220517_111103.log 5 KB -
Log20220515_133904.log 9087 KB -
Log20220513_230759.log 36870 KB -
Log20220513_215324.log 1635 KB -
Log20220511_210944.log 48742 KB -
Log20220511_210944.log 48742 KB -
draft bug 2.png 4076 KB -
draft bug 1.png 3070 KB -
Cabaretti land changed back to jackhammer.log 67 KB -
Jackhammer exchanged for cabaretti land.log 61 KB -
Log20220504_231653.log 28327 KB -
Log20220501_232218.log 5 KB -
QQ图片20220501233247.png 2561 KB -
QQ图片20220501233242.png 2633 KB -
屏幕截图 2022-05-01 233331.png 1515 KB -
Log20220501_185417.log 1212 KB -
Log20220501_115417.log 20 KB -
Log20220501_114008.log 8 KB -
Player.log 9637 KB -
Log20220428_201625.log 9636 KB
1,864 votesThygrrr#26219 supported this idea ·
-
-
542 votes
Thygrrr#26219 supported this idea ·
After consistent trouble (see log file earlier this week), my gf suggested I whip out Wireshark because I was unable to play direct challenge and I am massively disappointed in Arena at the moment.
Guess what - today it worked for me, but TO ADD INSULT to INSULT now it fails for my brother (it was the exact opposite just yesterday)
I just want to play :(
I think about asking for a refund. This is several nights of play, which I bought hundreds of euros of cards for, just gone without as much as an excuse or proper acknowledgement.
Nobody reaching out to ask for logs.
Nobody reaching out to ask for a reproduction.
Nobody acknowledging recepit or logs.
Nobody asking questions about logs and patterns.
Just a shrug in the patch notes.
It's as if your QA team does not care.