Add troubleshooting section (with model architecture and custom node troubleshooting subpages) #136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #101 by adding Troubleshooting section with various subpages (can be re-organized later). The major benefit of having these pages here is so that we can quickly link to them whenever someone reports an issue on the forum, discord, reddit, wechat, or GitHub Issues/discussions.
In this initial PR, I included troubleshooting subpages for 2 errors that have been repeatedly reported by users (each time requiring someone to re-explain the troubleshooting process or solution manually):
Over time, more common issues or pitfalls can be documented with solution and troubleshooting steps.