Zeus
June 21st, 2009, 18:23
Hey all,
I'm experiencing a weird issue under 2.3.6 which results in FG2 crashing upon restart/reload of a campaign which contains a specific open module. I am hoping someone can point me in the right direction or confirm if this is a known issue.
Firstly I am running FG2 on a 64bit Vista system with the latest 4E_JPG 1.51 ruleset. I am using a H1 KoTS module I created by compiling the story elements (through the FG2 interface) and using monsters, items etc. from parsed rulebook modules (using Tenians 4EParser) and then /exporting the whole lot.
Now in general everything is fine, ruleset/modules (including KoTS) work and my players are able connect to me and enjoy some fine virtual RPGing. I have run serveral sessions without any in-game incident.
The problem comes after I have shut down the server and restart FG2 and reload the campaign (usually the day after a game session to update notes etc). As soon as I start FG2, select the campaign and Start, FG2 crashes after about 3 secs. Attempts to reload FG2 and the campaign result in the same crash, FG2 is not responding blah blah.
Inspecting the campaign folder and specifically the modulesdb subfolder I find in all of the 1KB files a single file (4e H1 KoTS.xml) which reads at over 2548Kb! Opening the suspicious XML file reveals many recordname entries have double chained entries.
e.g.
<class>encounter</class>
<recordname>encounter.id-00016@4e H1 KoTS@4e H1 KoTS</recordname>
Some records even have triple or quadruple repetitions so am pretty sure something is wrong.
Manually replacing every duplicate/triplicate or quartet reference to @4e H1 KoTS with a single entry and resaving the file fixes the issue and FG2 loadd up the campaign without error.
Now at first I thought it was a one off but this is happening now after every sustained game session. Has anyone else encountered anything similar?
I admit to only using the 4E_JPG ruleset so cannot confirm if this occurs in other rulesets. However given the module in question was created using /export and given modulesdb is not specific to a ruleset I'm inclined to suspect the issue maybe with FG2 and how its maintaining modulesdb. Having siad that I am no expert so what do I know, it could be anything.
Any help would be much appreciated as the resolution whilst pretty quick is a pain in the a*@ to do after every session.
Thanks Z.
I'm experiencing a weird issue under 2.3.6 which results in FG2 crashing upon restart/reload of a campaign which contains a specific open module. I am hoping someone can point me in the right direction or confirm if this is a known issue.
Firstly I am running FG2 on a 64bit Vista system with the latest 4E_JPG 1.51 ruleset. I am using a H1 KoTS module I created by compiling the story elements (through the FG2 interface) and using monsters, items etc. from parsed rulebook modules (using Tenians 4EParser) and then /exporting the whole lot.
Now in general everything is fine, ruleset/modules (including KoTS) work and my players are able connect to me and enjoy some fine virtual RPGing. I have run serveral sessions without any in-game incident.
The problem comes after I have shut down the server and restart FG2 and reload the campaign (usually the day after a game session to update notes etc). As soon as I start FG2, select the campaign and Start, FG2 crashes after about 3 secs. Attempts to reload FG2 and the campaign result in the same crash, FG2 is not responding blah blah.
Inspecting the campaign folder and specifically the modulesdb subfolder I find in all of the 1KB files a single file (4e H1 KoTS.xml) which reads at over 2548Kb! Opening the suspicious XML file reveals many recordname entries have double chained entries.
e.g.
<class>encounter</class>
<recordname>encounter.id-00016@4e H1 KoTS@4e H1 KoTS</recordname>
Some records even have triple or quadruple repetitions so am pretty sure something is wrong.
Manually replacing every duplicate/triplicate or quartet reference to @4e H1 KoTS with a single entry and resaving the file fixes the issue and FG2 loadd up the campaign without error.
Now at first I thought it was a one off but this is happening now after every sustained game session. Has anyone else encountered anything similar?
I admit to only using the 4E_JPG ruleset so cannot confirm if this occurs in other rulesets. However given the module in question was created using /export and given modulesdb is not specific to a ruleset I'm inclined to suspect the issue maybe with FG2 and how its maintaining modulesdb. Having siad that I am no expert so what do I know, it could be anything.
Any help would be much appreciated as the resolution whilst pretty quick is a pain in the a*@ to do after every session.
Thanks Z.