Hi Duke
Interestingly - this is a Win10 issue - everyone will find I think that they are low admin accounts - Win10 does not give anyone full admin status - but admin rights - even then sometimes a pop up will say - only admin can do this - even with UAC set to off and only one account - looking at the account status it is not listed as admin - it seems to be a power user class. So even though mine is the only account - the 'users' accounts did not have write access to the dmp folder - but the administrator accounts did - so I could read/write - but ED-IBE could not. I can add the write status via security property but chose not to - I installed 052 instead.
A possible solution for this issue is to install ED-IBE in it's default paths.
The data part is saved by default in the users appdata folder (eg.: "C:\Users\Duke\AppData\Local\ED-IBE")
Even Win10 should give the user full access to files in this folder.
I recommend to do this - especially if you're running Win10.
052 - improvement - immediately corrected location error - found journal and sector/status and downloaded commodities - however the new install deleted my visited stations only - had visited sectors - so the current sector 2 stations details were downloaded - it also kept the data from the incorrect station previously seen - but somehow lost all other 30-40 stations/sectors I had visited even though I also import from CSV - it reported successful - but not seen in ED-IBE. I have attached my exported CSV from 042/050 which it will not read back it seems.
View attachment 112782
I also now had some filescanner logs
View attachment 112783
When I look at visited systems I only get 2 - not the list from the csv file from v 040 onwards?
So I deleted all data using delete older than 0 days - just in case it downloaded new data from EDBN even though I did not request it to - I just wanted my visited station data - I know the filter works like that as when I set to all - suddenly it was building a list for all stations - I thought that only happened if you changed to 20Ly bubble or 'Give me all' - but I seem to have a 100Mb csv file. I also used 'clean spacestations from no more existing commodities' - to try and wipe all the data - so I could try to reimport my csv backup (is there a delete/wipe all data backup????)
This resulted in no data or stations listed - and the previous data was not visible - has the import broken? Clicking on recollect did add Arkandi Agnesi Colony (current station/sector) correctly - but I have lost all previous data (050 backup)
Great steps forward seems to be working now - but unfortunately all previous data lost - any ideas (I can provide all data and folder info)
It's not fully clear for me what you have done exactly and which data you've have lossed now.
Do you mean the market data or the data from the Commader's Log ?
I must confess there's at the moment no possibilty to save or backup the data from the Commanders Log !
All data exports working only with the market data.
Yes, shame on me, but I had not the time to take care on it - there are so many other construction sites in the software.
So, If you've deleted all, then your Commander's Log will stay empty.
But it should not be too much work to re-import jump data from
the existing ED journals to refill or complete the Commander's Log
and set the visited flag for the systems.
But - of course - I have to program this function first.
I also now had some filescanner logs Logs 28 Oct v052.zip
They are very interesting:
In general the journal scanner is working and gets the actual location out of it:
Code:
submit ref event : latestFileHeader
submit ref event : latestLocationEvent
But after that it get no more new lines. Theres only the periodic entry from the check cycle.
(Ok, be aware: the cycle time is ONE SECOND. Perhaps you simply have to run the verbose log a bit longer ?)
Code:
28.10.2016 20:51:29 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:30 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:31 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:32 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:33 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:34 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:35 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:36 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:37 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:38 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:39 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:40 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:41 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:42 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:43 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:44 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:54 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:55 : check file for new events : Journal.161027205514.01.log (True)
28.10.2016 20:51:56 : check file for new events : Journal.161027205514.01.log (True)
Normally it should look like one of my verbose logs below. There are lines starting with "new line from : ...."
(Of course : if you do nothing in ED it will look like above !!! - In cause of this you must activate the verbose log
and do something in ED which creates some events in the journal. Have you done this ?)
Code:
28.10.2016 19:03:45 : check file for new events : Journal.161028155824.01.log (True)
28.10.2016 19:03:46 : check file for new events : Journal.161028155824.01.log (True)
28.10.2016 19:03:46 : new line from : Journal.161028155824.01.log : { "timestamp":"2016-10-28T17:03:45Z", "event":"ReceiveText", "From":"Kandrup Point", "Message":"$STATION_docking_requestfailnotyetclear;", "Message_Localised":"LANDEERLAUBNIS VERWEIGERT, EINGANG FREI MACHEN.", "Channel":"npc" }
28.10.2016 19:03:46 : write new time
28.10.2016 19:03:47 : check file for new events : Journal.161028155824.01.log (True)
28.10.2016 19:03:48 : check file for new events : Journal.161028155824.01.log (True)
28.10.2016 19:03:49 : check file for new events : Journal.161028155824.01.log (True)
28.10.2016 19:03:50 : check file for new events : Journal.161028155824.01.log (True)
28.10.2016 19:03:51 : check file for new events : Journal.161028155824.01.log (True)
28.10.2016 19:03:51 : new line from : Journal.161028155824.01.log : { "timestamp":"2016-10-28T17:03:50Z", "event":"DockingRequested", "StationName":"Kandrup Point" }
28.10.2016 19:03:51 : new line from : Journal.161028155824.01.log : { "timestamp":"2016-10-28T17:03:50Z", "event":"ReceiveText", "From":"Kandrup Point", "Message":"$DockingChatter_Allied;", "Message_Localised":"So ein Verbündeter ist hier stets gern gesehen.", "Channel":"npc" }
28.10.2016 19:03:51 : write new time
28.10.2016 19:03:52 : check file for new events : Journal.161028155824.01.log (True)
28.10.2016 19:03:52 : new line from : Journal.161028155824.01.log : { "timestamp":"2016-10-28T17:03:51Z", "event":"ReceiveText", "From":"Kandrup Point", "Message":"$STATION_docking_granted;", "Message_Localised":"Landeerlaubnis gewährt.", "Channel":"npc" }
28.10.2016 19:03:52 : new line from : Journal.161028155824.01.log : { "timestamp":"2016-10-28T17:03:51Z", "event":"DockingGranted", "LandingPad":2, "StationName":"Kandrup Point" }
28.10.2016 19:03:52 : write new time
28.10.2016 19:03:53 : check file for new events : Journal.161028155824.01.log (True)
Please check also, whether the file which is named in the verbose log
Code:
check file for new events : [COLOR="#FF0000"]Journal.161028155824.01.log[/COLOR] (True)
is defacto the current and active journal file from ED.
Look in the active journal file while you are running ED and ED-IBE and check if there are new
entries which should have been detected by ED-IBEs journal scanner.