PDA

View Full Version : FGU crashed and now won't load



RESmeCUE
January 24th, 2025, 00:49
While playing last night, FGU crashed. It froze first then shut down on its own.

Today I log in to work on my campaign, and it won't load. It's stuck on the error log window open, a map in use at the time if the crash, and the campaign setup window.
Normally only the campaign setup window is present and off I go.

What happened? How can I get this to load? I cannot even click on the screen as the mouse cursor turns into the blue wheel of death.

I tried patience....failed. never loaded.
I tried reinstalling FGU...failed. never loaded.
I tried rebooting my computer...failed. still stuck.

The task manager shows the game pulling up to 12,000 MB of memory, and up to 24% of the CPU at times.

Picture attached.

Help please!
Thank you in advance.

RESmeCUE
January 24th, 2025, 00:58
632886328963290

Mike Serfass
January 24th, 2025, 01:05
This is caused by one of the extensions. Disable all extensions then start the campaign.
The error indicates Points of Interest.
Have you updated extensions?
I'm running that extension with Savage Worlds without problems. So if PoI is updated and still causing the error, it could be the ruleset you're using or another extension.
Please give us a log file. That will help narrow it down and give the extension creator info to fix it.

RESmeCUE
January 24th, 2025, 03:05
This is caused by one of the extensions. Disable all extensions then start the campaign.
The error indicates Points of Interest.
Have you updated extensions?
I'm running that extension with Savage Worlds without problems. So if PoI is updated and still causing the error, it could be the ruleset you're using or another extension.
Please give us a log file. That will help narrow it down and give the extension creator info to fix it.

I uninstalled PoI but now it seems like the problem is with AD&D Options and House Rules (https://forge.fantasygrounds.com/shop/items/688/view) as my FGU just freezes upon loading with that ext selected

LordEntrails
January 24th, 2025, 03:26
I uninstalled PoI but now it seems like the problem is with AD&D Options and House Rules (https://forge.fantasygrounds.com/shop/items/688/view) as my FGU just freezes upon loading with that ext selected
Is that the only extension you now have enabled? Does the crash repeat in a new campaign with only that extension loaded? If so, report the issue, including the console.log file in the forum thread for that extension. It is listed on the product Forge page above the Description.
How to Compile Logs - Fantasy Grounds Customer Portal - Fantasy Grounds (https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1242136781/How+to+Compile+Logs)

RESmeCUE
January 24th, 2025, 21:23
Is that the only extension you now have enabled? Does the crash repeat in a new campaign with only that extension loaded? If so, report the issue, including the console.log file in the forum thread for that extension. It is listed on the product Forge page above the Description.
How to Compile Logs - Fantasy Grounds Customer Portal - Fantasy Grounds (https://fantasygroundsunity.atlassian.net/wiki/spaces/FGCP/pages/1242136781/How+to+Compile+Logs)

So I got the extension from a friend and replaced the file. the session works now but had to load a previous backup. now the issue is that, on the combat tracker the weapons are not loading on my (the DM) combat tracker to attack/cast from. the logs say something about "font"

63298

Not sure if I attached the log properly

LordEntrails
January 24th, 2025, 23:10
Thanks for the log. That helps tremendously.
So the Ruleset you are using is AD&D 2E and you have 9 extensions loaded.

One of those extensions is broken. Or possible the ruleset (doubtful). You should create a new campaign and see if it works with no extensions. Then turn your extension on one at a time until it breaks (I would start with the "options" ones, they are most likely the cause). Then turn off all but the last extension you turned on and see if its still broken. If so, then you need to get that extension fixed or stop using it. Otherwise it's a combination of extensions that are causing the things to break and you are going to have to spend more time figuring out which combinations break and which don't. And then getting all those extensions to work together.

Extensions are not supported by Smiteworks (but they are obviously allowed) and are the responsibility of the user and the extension creators to keep them working. Each Forge extension should have a "Forum Thread" listed on its Forge page that the creator should monitor for bug reports. If you got extensions from a friend, then you will have to figure out how to get that solved.

RESmeCUE
January 25th, 2025, 18:12
Thanks for the log. That helps tremendously.
So the Ruleset you are using is AD&D 2E and you have 9 extensions loaded.

One of those extensions is broken. Or possible the ruleset (doubtful). You should create a new campaign and see if it works with no extensions. Then turn your extension on one at a time until it breaks (I would start with the "options" ones, they are most likely the cause). Then turn off all but the last extension you turned on and see if its still broken. If so, then you need to get that extension fixed or stop using it. Otherwise it's a combination of extensions that are causing the things to break and you are going to have to spend more time figuring out which combinations break and which don't. And then getting all those extensions to work together.

Extensions are not supported by Smiteworks (but they are obviously allowed) and are the responsibility of the user and the extension creators to keep them working. Each Forge extension should have a "Forum Thread" listed on its Forge page that the creator should monitor for bug reports. If you got extensions from a friend, then you will have to figure out how to get that solved.

THANK YOU!

Took some time but found the source of the problem.

For any reading this thread, the extension 2E players option and more (https://forge.fantasygrounds.com/shop/items/78/view) had loaded twice and caused all of the issues.

Thanks to all who helped!