-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting (or: 'My PC is on fire help')
Back shit up all the time. You should do this all the time for everything. Seriously, hardware dies and stuff is getting more and more expensive to replace. Protect your stuff.
Also, read the usage instructions first. If you did everything they said correctly, you'll never need to see this page.
Open Settings and choose Divine.exe, or set LSLIB_DIVINE.
Choose the folder named Baldurs Gate 3. Do not choose Data, bin, or the Steam library parent folder.
Check the GR2 path in the converted LSX or use the legacy Bounds Calculator plus LSF Patcher.
Skipped files are usually not VisualBank files, cannot be converted, or do not contain usable GR2 references. Check the log for the exact reason.
WHY WOULD YOU DO THAT. Close the Toolkit and inspect your files. If the Toolkit overwrote the output, restore from backup and run the patch again with the Toolkit closed.
Well, shit.
If you are asking for help, open up an Issue ticket, and make sure you include important information like:
- Which tab/tool you used
- The relevant log output
- The selected source path
- Whether a
.bak-*backup was created
The more information you give me about an issue, the better. I can't fix things if I don't have all the information needed to figure out the fix.
Do not upload private project files unless you are comfortable sharing them. I'm never going to do anything with them but still.
Too bad. Issue tracking is hard as it is and I don't want stuff buried in Discord also stop using Discord for issue tracking jesus christ. If it's not reported here in the repo, it's not getting fixed.
-
So you wanna use my little tool
Lmao it's an innuendo -
The Bounds Patcher
(or 'help, stuff do be invisible!') -
Import Repair
(or: 'I forgot to uncheck that box again...') -
Project Tools
(or 'Stuff that didn't deserve its own tab') -
Troubleshooting
(or: 'My PC is on fire help')