Sharing one map causes all players to crash and disconnect

[cwsoots]

I will start by saying that this issue first occurred last Sunday (pre-ruleset update). However, when I tested it today, I was able to recreate this issue and I'm not sure how to diagnose or fix it.

Problem: When I shared a particular map with a party of four other players, the map opened fine and without issue on my system (the host). However, it caused all of my players' FGU instances to instantly crash and disconnect. There was no console errors shown, according to the players—FGU simply crashed. We had used this map in a previous session, but I had made some recent updates to it.

Since this is a campaign-specific map with modifcations, I'm not sure how I could recreate the problem in a 'clean' test campaign, so I'm including my entire campaign folder at this link for review: https://1drv.ms/u/c/a1f9cc571d6f2f87/IQDSvx_6D7pnRpOiE8-EzdChAZdQlVXYSUiKY8gWtrt5odg?e=bRjqG5.

The map name is "Ruined Town of Leilon [120 x 130]" and I'm aware that it is a larger map, but it's worked well for a large scale battle in the past. I don't know why it's causing the clients to crash now. Any suggestions are appreciated. Thanks!

[Trenloe]

I had something similar happen in my PF2 Kingmaker game - before the recent update. It was an existing map with a number of layers (primarily small images and text labels on a regional map) that we'd used many times before. I added approx. 10 text labels and put them in a folder - then when shared with the players the player instance hangs and eventually disconnects and has to be force closed. I can reproduce this with a second instance (player) running on the same computer as the GM instance. I was working on trying to troubleshoot to see if I could "fix it" and then break it again to try to narrow down what suddenly caused the issue.

As a workaround, if the image/map has been shared before, drag the image link to chat and ask the players to use that link to open the map - it should open fine. It appears that the issue is within the sharing process and not the opening of the map itself.

EDIT: I can recreate the issue with your test campaign. As a player, if I open the map from the Images list it opens fine - it's previously been shared so it's available to open. However, if as the GM I re-share the image, it results in the connected players hanging.

Doing more testing - if I unshare the image first, then share it opens fine on the player side. But, once shared, if I re-share the image the player side hang results.

@cwsoots - your image has a lot less layers than mine. Thanks for sharing, hopefully this will allow the devs to work out what the issue is.

[cwsoots]

Thank you, Trenloe, for taking the time to test and verify; and I'm glad to know that it is repeatable. I'll try the temporary workarounds, if needed. Hopefully this can be resolved soon, before my next session on Sunday. 🤞🏻

[HywelPhillips]

I had this happen with the map of Lankshorn in the Dolmenwood campaign book a few weeks ago. I circumvented by screen grabbing and sharing that instead, but it would be good to get a proper fix.
(I had the Dolmenwoid stuff loaded into a Shadowdark campaign, only extensions were a theme and my hacked Universal module ext to allow the load).

Hywel

[BobM]

I had the identical problem last month (FG Game Day) with a map that 1) had multiple layers, with effects and simple line paintings and texts on various layers (I don't think I have occluders on multiple layers but maybe), 2) In a clean copy of the campaign with the same combination of extensions the problem did not happen, 3) I shared my logs and campaign through the suport > Create a Ticket interface. I can do so again if it will help. Just that one map two later maps (including one that was even more complex) shared with no problems.

[Trenloe]

I shared my logs and campaign through the suport > Create a Ticket interface. I can do so again if it will help.
If the ticket is still open with support could you point them towards this thread please?

[BobM]

If the ticket is still open with support could you point them towards this thread please?

I would, but I couldn't figure out how to get to the ticket I opened. Ticket SUPPORT-31086 from the confirmation email I received, but I cannot get back to the ticket, only create new ones it looks like, and I didn't want to duplicate my report. Am I missing something?

BobM

[Trenloe]

@BobM - I don't usually log tickets, so I don't know the interface or how to re-access a ticket.

I've reached out to the devs directly. Hopefully the data already in this thread will be enough for them to recreate the issue and also fix it. Thanks for the ticket number and for offering to re-report the issue - I think we're OK for now.

[Moon Wizard]

We just pushed v5.1.9 that Carl believes should fix this issue. Can you please run a new Check for Updates, and let us know if you're still having an issue?

Regards,
JPG

[Trenloe]

We just pushed v5.1.9 that Carl believes should fix this issue. Can you please run a new Check for Updates, and let us know if you're still having an issue?

Regards,
JPG
This has fixed the issue with my map. Thanks Carl and JPG!

[BobM]

We just pushed v5.1.9 that Carl believes should fix this issue. Can you please run a new Check for Updates, and let us know if you're still having an issue?


Fixed it for me as well.

[cwsoots]

We just pushed v5.1.9 that Carl believes should fix this issue. Can you please run a new Check for Updates, and let us know if you're still having an issue?

Regards,
JPG

This also fixed my map sharing issue. The client now receives the map and doesn't crash. Thank you!