That worked - thanks so much!
I’ve just had a crash while searching, FYI - here is my log file. Seems to be related to SQL once again
log-v2.txt (331.3 KB)
and another unfortunately - I can’t search anymore without it crashing ~2 seconds after the search
log.txt (142.8 KB)
Seems you’ve come from a fairly old version of IA, probably from 2024.
Fixing a migration for the missing column, I’ll have a version up soon, just looking into the other issue as well.
I sent you a message. I think I need your database, I don’t know how to reproduce this issue.
Thank you, replied.
FATAL[EvilsoftCommons.Exceptions.ExceptionReporter]: BinaryFormatter serialization and deserialization have been removed. See https://aka.ms/binaryformatter for more information.
Anyone having IA crash upon start and encountering this error, update to the latest version of IA manually.
The cause is that some recent versions of IA have a problem with automatic updates, causing the update check to crash.
Manually download the latest version from the website or the latest release at Releases · marius00/iagd · GitHub
Install it and the problem should be solved.
There is no need to uninstall the previous version beforehand.
thx microsoft for constantly running some .net runtime optimization service/windows updates which are unable to even keep the runtime environment up-to-date leading regular-ass people to some download site for the sdk, asp .net core runtime, .net desktop runtime and .net runtime - whoever of these fucking morons thought that was a good idea? /rant_over
It didn’t even lead me to a download site, the link went nowehere for me. I had to manually search then install the wrong thing, install the other thing and now it works. ![]()
Hi, confirming I think the above version did solve the issue. I did a few large xfers of items and many medium sized xfers and no lockups.
Thank you very much!
I have just updated to the latest version (of both Grim Dawn and Grim Dawn Item Assistant) and can not perform the Load Database step - GDIA always crashes.
log.txt (58.4 KB)
-
Go to settings, then import/export.
-
Export your items to .ias
-
Then click “view logs”, go into the “data” folder, close IAGD and delete userdata.db
-
Then start IA (your items are gone! oh noes!)
-
Settings, import/export, and import the .ias file
That’ll fix the issue.
I know the cause, not quite decided on the solution yet.
The above steps should permanently solve the issue though.
Thank you very much. Issue solved.
I’ve been having not IA but Grim Dawn crash on me when GDIA is running. It’s usually either when I try to quit the game or while I’m scrolling through my character list on Grim Dawn.
Upon crashing and looking at the log tab on IA the app keeps telling me to parse the file again constantly. But after parsing the exact same thing just happens again.
[13/12 17:15:05] INFO Deposited item back in-game, did not pass item classification.
[13/12 17:15:05] INFO New GD patch? Go to the Grim Dawn tab and parse the game files again.
These lines are spat out for dozens of items and when you run Grim Dawn again they do show up in the second last tab.
Both IA and GD work fine, it’s just the crashing can be really annoying at times.
Any help would be much appreciated!
Also when opening the shared stash, I get the n triple dot and various other popups
Which version of IA are you running?
Do not reply “the latest”.
started encountering these crashes after i had updated from some old 1.2 version to somewhere around 1.4 (still getting them in 1.5.9460.34258). the most notable change between these versions was that instant looting from the last tab had been introduced. what hadn’t occurred to me is checking if the old style looting was still available and wouldn’t you know it, it is in the settings. gonna run with that for a bit and see how it goes.
Hi! Just returned to the game – and this app. I can run it and it does loot from the game – but when I try to open it on the desktop, I get a notification I need Visual Studio 2013. I’ve tried to download that but the file didn’t work. Visual Studio 2025 doesn’t seem to do the trick, either.
Any tips?
ETA: Just downloaded the file this morning so, the newest. I’m running the newest.
1.5.9460.34258