speedycerv
Active Member
After doing my last file copying from the svn updated files, when I run the harvester, the pathing tab was gone again (this happened to me before). So i deleted/uninstalled everything then reinstalled everything, and last time this happened it fixed it. I tried it this time, and nothing. It's still not showing up. Any help would be appreciated.
edit: i see amadeas is working on it, that would explain it
edit#2: Ok, amadeas says to use eq2harvestlegacy, I could use it to set up a path. There was a couple bugs, like clicking the x didnt close it and every numeric value was set to NULL, but more importantly, when i was able to get the pathing co-ords into the start and finish destinations set and try to harvest, it wouldn't move. I'm assuming that there is some updating to do on the legacy version. Just wanting to confirm to see if everyone else seeing the same things I am.
A couple other bugs I've noticed with legacy is
1. when i tried to set the amount to keep, no window would come up.
2. the only way to close it is right clicking and choosing the close option, and once this is done, it cannot be rerun until i close out of eq2 and open it again, because it thinks legacy is still running.
edit: i see amadeas is working on it, that would explain it
edit#2: Ok, amadeas says to use eq2harvestlegacy, I could use it to set up a path. There was a couple bugs, like clicking the x didnt close it and every numeric value was set to NULL, but more importantly, when i was able to get the pathing co-ords into the start and finish destinations set and try to harvest, it wouldn't move. I'm assuming that there is some updating to do on the legacy version. Just wanting to confirm to see if everyone else seeing the same things I am.
A couple other bugs I've noticed with legacy is
1. when i tried to set the amount to keep, no window would come up.
2. the only way to close it is right clicking and choosing the close option, and once this is done, it cannot be rerun until i close out of eq2 and open it again, because it thinks legacy is still running.
Last edited:
