as soon as i start my instances it crashes
System.NullReferenceException: Object reference not set to an instance of an object.
at FindersKeepers.Experience.ExperienceTick()
at FindersKeepers.FindersKeepers.Uptime(Object sender, EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Well, it's totally ****ed up for me. The only thing I have set up is a Legendary filter. Any yellow item triggers it. Also, even though I have the filter for Death's Breath turned off, even muted the sound, it still plays when DB drops...
1. The program works for awhile, then I start getting random custom wave files stating information that I know is wrong. (gems when I am in town or entering into a new zone before killing anything). Once that happens, the accuracy of the alerts drop and I have to close the program and restart it.
2. If I leave FK running too long, it will not close without using task manager to kill the process.
3. If I use FK for an extended time, then change something in the config or edit an alert or feature it can corrupt the XML files. If the XML files get corrupted, they will appear as ZERO byte files, they then must be deleted before the program will work again.
4. When making a new filter for Legendary items, you must select "Legendary" on the drop down, then change it to something else, then change it back to Legendary or you will get Legendary alerts for Rare items.
5. When running the program for an extended time or rapidly changing zones, the program will crash and a windows error will report an unexpected error has occurred.
6. It feels like FK has a memory leak.
I am running full screen window mode in D3, using 3 monitors. I move and position the popup window onto the right monitor. If I leave the popup window on my diablo screen it lags my D3 client severely.
Yeah , its not a memory leak (my stupidness forgot to change one debug option, so its dumping stuff when it shouldn't, not being written just dumping, happens when an Item drops, you can drop 10 items and see how FK eats up the CPU).
Almost all basic functionally is back working, will continue tomorrow and you'll have a nice release by tomorrow![]()
Running Windows 8 OS and I can't get the Beta to run. It just crashes immediately after creating a filter and hitting Play for the Multibox setup. Gotta Delete the config to get back into the program.
Previous version doesnt play any alerts for drops now. I can provide an error log or what not if someone lets me know how. ^_^
New version out:
Don't forget to delete FKConfig.XML and remake it and also redownload FKUpdater if you are using it.
Updated tutorials & guides are also coming soon
http://www.finderskeepersd3.com/Downloads
Originally Posted by 3.2.8
Last edited by Dolphe; 04-13-2014 at 05:13 PM.
How do you enable minimap overlay? I've gone into the xml and changed everything to enable.
<AppType Name="Minimap Overlay" GroupID="14" Enabled="true" MuteSound="true" Mode="true" Overlay="true" OverlayColor="0" OverlayTimer="3000" Sound="sound.wav" _GetInActive="" />
But in the app i cannot select what i want on the minimap overlay?
"minimap items" in the application tab of fk.
![]()
Sanguinary vambraces comes up as "unknown legendary"