![]() |
|
#1
|
|||||
|
![]() Since I don't have github account, I will report an issue here. I downloaded the latest 0.51 dev version. I'm running it from source on Linux. I over wrote old files with the new ones and start nparser. I got error msg, that nparser log file is missing. This must be new. So I created file 'nparse.log' inside folder 'logs' within nparser folder.
Nparser tehn started and log file is being used. But looks like, there is a problem. Nparses complains, that path to eq99 log file is not set, and that I should set the proper path through nparser taskbar icone. I tried several times, went to settings, and there is no where, where I could set proper path to EQ99 logs. It was there in previous version. There is proper EQ99 logs path set in nparse.config.json, but new nparser is probably checking if I set it again through nparser, which I didn't, hence error and my location is not being plotted on the map. So I overwrote new nparser-dev with previous version and all is OK on my end, just reporting if it can be of any use to you ;-) Quote:
Quote:
| ||||
Last edited by pivo; 05-08-2020 at 02:36 PM..
|
#2
|
||||
|
![]() Quote:
The other issue you are seeing, is that the directory you set is your Everquest directory and no longer your actual log directory. I wanted to link your spells_us.txt so I don't have to distribute it in the releases anymore. eq_log_dir is obselete eq_dir is what is used now You need to set that to where your Everquest installation is. You can set the value by going to settings -> General -> Everquest Directory and then set. I would love to know any issues you face and am grateful for your comments. Feel free to PM if you don't want to sign up for Github. Between programming, work, etc, I don't have much time to test everything [You must be logged in to view images. Log in or Register.] edit: I will also update the error message to explain where to set the directory. edit2: All this has been fixed in the latest dev commit. | |||
Last edited by Mirox; 05-08-2020 at 07:49 PM..
|
#3
|
||||
|
![]() Quote:
If I find any bugs in the future, I can use PM. But here, public may be better. It keeps thread at the top and new members may find about nParse that other wise wouldn't [You must be logged in to view images. Log in or Register.] | |||
![]() |
|
|