Reply to thread

The exception is being thrown by SDT.swf code (rather than Loader.swf code).  Loader doesn't interfere with the spit-strand logic; it simply allows users to alter global parameters (mass, transparency, etc) via the Settings file.  So what we're seeing is probably a conflict generated by one or more Loader mods - rather than the Loader itself.

• Ensure that you're running the latest version of Loader and Flash Projector.
  • This is boilerplate advice, akin to "try turning it off and on again" but there's a slim chance that it might fix the problem).
• Try disabling all of your mods (comment out everything in Mods.txt) and then restart Loader.swf.  Does the problem still occur?
• If the problem occurs even in an unmodded environment, then try reverting all of your Settings to default.  If you simply rename the Settings.txt file in the game's root folder and restart Loader.swf, then it will use defaults.  You can restore the filename after you've confirmed that the problem does (or does not) recur.
  • If the problem is resolved by the revert-to-default test, then we can assume that your non-standard Settings are causing the problem.  If you've made any changes to the Loader's settings file (e.g. boosted the max length of strands?) then post them here.  Or just attach the whole settings file if you can't remember which items you've modified.
  • In this case, you probably won't get a direct bugfix (because it would require a lot of testing and might generate new conflicts with existing mods).  The simple answer would be "adjust your Settings file, gradually approaching the default value for the problematic item, until the crash no longer occurs."
• If the problem still occurs in an unmodified environment with default Settings, then please post a more complete bug report.  PC specs, repro steps, time elapsed before crash (e.g. is this a random occurrence arising from poor code synchronization, or a gradual degeneration caused by a memory leak?).  Maybe include a few differential test results as well (e.g. does the problem go away if you disable strand shaders, or if you reduce the game's visual quality to Low?).
  • The reason that I'm asking for a more complete bug report is because I wasn't able to reproduce the crash behaviour on my end (Loader 5.45, strand shaders enabled, a few random mods loaded but none of them relevant to "spit" behaviour, allowed the game to run on Hard auto mode for 90 seconds).  It's tough to diagnose or fix a bug if it can't be reproduced.
• If the problem isfixed by disabling all mods, then gradually re-enable them until you discover which mod (or set of mods) seems to trigger the problem.
  • Try upgrading the problem mod(s) to the newest available version.  Does the error still occur?
  • If the problem is triggered by a minor mod (or something written by a modder who has since gone inactive) then the simplest fix is to simply disable that mod permanently.
  • If the problem is triggered by a major mod (such as animtools) which you're not willing to do without, then post a bug report in the modder's thread.