search

Bouncyrock / TaleSpire-Beta-Public-Issue-Tracker

Issue tracker for the TaleSpire Beta
33 stars 17 forks source link

Boards corrupting #990

Closed msifton closed 2 years ago

msifton commented 3 years ago

Describe the bug

I was adding the new fireplace asset to a large board (meant as a tileset to construct city buildings... it had a lot of stuff in it). I noticed the fire VFX in the fireplace wasn't functioning, and became concerned.

I decided I should reload the program, and attempted to quit Talespire - in hindsight, this was a terrible idea. It immediately hard crashed while trying to quit. When I tried to open my board after the crash, I received an Unhandled Exception window, and was ejected to the place between boards. The board now refuses to load.

This bug has happened to me twice now, on two different boards, both heavy with buildings, lights, and other assets. Interestingly, the first time the board was only partially corrupted - about half of the buildings and assets loaded correctly, but a large region of the board would not load, and was replaced with the large white grid you of the place between boards. I couldn't draw a selection box or even pan the viewport into this blank grid area, and some of my buidlings were sawed in half at the border.

I have a partial screenshot of this board as it attempts to load (see Talespire_Error_03.png). I'd send you a better visual, but the half-corrupted board is now fully corrupted and won't load.

To Reproduce Steps to reproduce the behavior:

  1. Add a light or fireplace to a large board with a lot of existing assets

  2. Notice the light's fire VFX is missing

  3. Try to quit Talespire, and suffer hard crash while quitting (perhaps trying to save)

  4. Reload Talespire, try to open board

  5. Get Error: Board Update Failed: Unhandled Exception.

  6. Get thrown into the Place Between Boards.

Screenshots/Videos/Twitch Clips Talespire_Error_01 Talespire_Error_02 Talespire_Error_03

Additional context I have 2 other boards in the campaign, including another large one that my players are currently adventuring through. For now, this board still loads correctly, but if it ever corrupts, this would really screw up my D&D campaign.

Kicking myself for not reporting the bug earlier, on the first board, as soon as I got it. I'd previously had Talespire loading difficulties that vanished after a day or so, and hoped this problem might just go away. Nope!

msifton commented 3 years ago

Okay! After several hours passed, and a cold boot of my PC, 2 of the 3 corrupted boards have loaded properly again, fire VFX and all. So that's great. However... my last board is still bugged. I'm able to open it (partially) but only half the buildings and assets load, many of them sawed in half. I was able to take a few screenshots. Talespire_Error_04 Talespire_Error_05 Talespire_Error_06

LuPro commented 3 years ago

If you are on the discord it would probably be a good idea to get in touch with baggers - campaigns are backed up with the 3 newest revisions so even if something is completely broken it should still be recoverable. Other than that the logs might help with diagnosing the issue, you can find them in %AppData%\..\LocalLow\Bouncyrock Entertainment\TaleSpire\ as "player.log" and "player-prev.log" (note: the logs contain your windows username, if you don't want that, search and replace it with something like ""

msifton commented 3 years ago

Thanks for the quick reply. Unfortunately I've done some work since the bug (beyond 3 revisions), and if the whole campaign was regressed beyond that, I'd lose more than the bug took from me. That said, if an individual board can be recovered, that might save me.

The damage to the board is frustrating, but really my own fault for not reporting immediately. I don't mind rebuilding. That said, if the bug continues to be a source of instability within the campaign, that's more dangerous, especially if it starts eating boards my players are actively going through.

Here are the logs.

Player.log Player-prev.log

LuPro commented 3 years ago

Taking a quick peek at the logs it does seem to have noticed some errors, though I can't tell whether they're related to this board stuff or not. Baggers is fairly quick on trying to get possibly data corrupting bugs out of the way, but as I don't know his schedule I don't know when he'll be able to take a look at this exactly - thanks for the data though :)

msifton commented 2 years ago

Forgot to close this back in June. Received backups and assistance from baggers on discord. Also followed these steps: