Forums » Community Projects
Version 1.0
Saves and categorizes all scanned asteroids
Allows data sharing with other players.
Determines and records the mass of mined asteroids.
Has a built in scanning aid.
Has an automatic junk jettison built in
See read.me file for commands and options
Anyone wanting to link up with me for mining data simply contact me in game.
Version 1.10
http://www.filedropper.com/filemanager/public.php?service=files&t=392ddb009a1796b7ebb295fe3750a399
Saves and categorizes all scanned asteroids
Allows data sharing with other players.
Determines and records the mass of mined asteroids.
Has a built in scanning aid.
Has an automatic junk jettison built in
See read.me file for commands and options
Anyone wanting to link up with me for mining data simply contact me in game.
Version 1.10
http://www.filedropper.com/filemanager/public.php?service=files&t=392ddb009a1796b7ebb295fe3750a399
awesome
Well... I guess I kind of like this. I'm not a big fan of targetless, because im old school and I'm not a miner; but on the otherhand I like to know where the miners are sooo...
Love the idea behind the mass calculation too!
Kudos
Love the idea behind the mass calculation too!
Kudos
Was trying to choose an ore list by sector via /ore command and got this:
plugins/Prospector/GUI/Display.lua:62: attempt to read from undeclared variable Dbg
stack traceback:
vo/error.lua:71: in function <vo/error.lua:70>
[C]: in function 'error'
vo/vo.lua:1319: in function <vo/vo.lua:1314>
plugins/Prospector/GUI/Display.lua:62: in function <plugins/Prospector/GUI/Display.lua:60>
(tail call): ?
plugins/Prospector/GUI/Display.lua:62: attempt to read from undeclared variable Dbg
stack traceback:
vo/error.lua:71: in function <vo/error.lua:70>
[C]: in function 'error'
vo/vo.lua:1319: in function <vo/vo.lua:1314>
plugins/Prospector/GUI/Display.lua:62: in function <plugins/Prospector/GUI/Display.lua:60>
(tail call): ?
OOPS - missed a debug - I will fix it.
You can comment the statement out for now with two --
or replace Dbg.Log with console_print if your in a hurry
Thanks for the report.
You can comment the statement out for now with two --
or replace Dbg.Log with console_print if your in a hurry
Thanks for the report.
Found and fixed a couple of other issues including a missing function that was needed during system jumps by other players to fetch the new system data.
Cant believe I missed that bug LOL
Cant believe I missed that bug LOL
hey PaKettle why haven't you added your plugin to voupr.com?
Does this share complete info with all online plugin users or just active scans? So far it seems just like active scans to me. Or do I have to add some else's name to the list in /pfconfig?
How does the /rs scanning thing work? I am observing it starting at roid 1 and targeting each roid till the end. This seems quite inefficient due to roids being randomly placed. Is there a way to instead target roids automatically when they get within range of the equipped scanner? And then remove scanned roids from a "to be scanned" list?
If not, what is the best way to to use roid scan command? Should I sit in an area for the scan period, let it run then move to a new area?
Thanks.
If not, what is the best way to to use roid scan command? Should I sit in an area for the scan period, let it run then move to a new area?
Thanks.
I beleive PaKettle said its quite slow to do limiting like that, so he disabled it until the sector is about 80% scanned. He suggested I set the ship to move at 1m/s with the best scanners, and just afk till I hit the end of the asteroid feild, then turn in a direction of more roids and continue.
The plug in only shares with the people in your access list, Both players must have each others name listed to be included. Also if you are in one network and your friend is in another then you wont be able to share either. I may change this later on to an all IM system but it would severely increase traffic issues.
Data is shared when scanned and when entering a new sector assuming someone is on with data to share. Note data received from other players is only shared if Broadcast is selected. This mode will share more data but any bad data that gets into the system will spread a lot more as well.
Data scanned by the user (locally) is considered to be more accurate then data from remote sources and is preferred in all cases. Local data will always overwrite remote data.
The scanner uses radar next until 75 percent completion. Its not very efficient but theres not really any better way to scan them at first. After the 75 percent mark it switches to unknown roids only but will not discover any additional roids. Usually i find manually scanning the edge areas first after a scanner pass thru the center works well for most fields. The scanner works best in dense areas while moving slowly. I tried scanning faster but there is a tendency for the roid data to be skipped a lot due to lagging and such. The random placement of the roids tends to make most algorithms useless in most sectors.
Data is shared when scanned and when entering a new sector assuming someone is on with data to share. Note data received from other players is only shared if Broadcast is selected. This mode will share more data but any bad data that gets into the system will spread a lot more as well.
Data scanned by the user (locally) is considered to be more accurate then data from remote sources and is preferred in all cases. Local data will always overwrite remote data.
The scanner uses radar next until 75 percent completion. Its not very efficient but theres not really any better way to scan them at first. After the 75 percent mark it switches to unknown roids only but will not discover any additional roids. Usually i find manually scanning the edge areas first after a scanner pass thru the center works well for most fields. The scanner works best in dense areas while moving slowly. I tried scanning faster but there is a tendency for the roid data to be skipped a lot due to lagging and such. The random placement of the roids tends to make most algorithms useless in most sectors.
The plug in only shares with the people in your access list, Both players must have each others name listed to be included. Also if you are in one network and your friend is in another then you wont be able to share either. I may change this later on to an all IM system but it would severely increase traffic issues.
so both players must have the same list of pilots in their access list?
so both players must have the same list of pilots in their access list?
Is there any plan to import from a targetless db?
Is there any plan to import from a targetless db?
I thought it allready did that, somote. Maybe not?
No plans to import from targetless for now.
Luxen it does help if everyone has all the same people in their list but not strictly required.
And I forgot - Prospector also gets an update whenever you access data via the /ore screen
Luxen it does help if everyone has all the same people in their list but not strictly required.
And I forgot - Prospector also gets an update whenever you access data via the /ore screen
I found an issue that may misplace remote roid data and fixed it in version 1.04.
Updating is strongly recommended
Updating is strongly recommended
V 1.05 Added buttons to purge remote roid data.
Is there a reason why, when I scan roids with a UDV, that they don't get added to the DB?
None I am aware of, The plugin is not really affected by the ship in use.
In order for a roid to be added it must be selected by the radar and actual data must be received. This can in fact take a few seconds. It is possible for a roid to be selected and no scan data recorded due to delays in data transmission from a slow connection.
A roid is only recorded when the new roid recorded message is displayed.
The auto scanning is not always helpful and at time you should in fact simply scan manually.
Also don't forget that the addon scanners are shorter in range then some of the built in scanners.
Put a different way , you must select the roid and wait for the scanner to actually display the stats for the roid before will you be able to save the data and get the new roid message.
If this continues to be an issue any additional info you can prove is helpful such as screen dumps, log data and the exact ship and scanner your using along with the location you were scanning.
In order for a roid to be added it must be selected by the radar and actual data must be received. This can in fact take a few seconds. It is possible for a roid to be selected and no scan data recorded due to delays in data transmission from a slow connection.
A roid is only recorded when the new roid recorded message is displayed.
The auto scanning is not always helpful and at time you should in fact simply scan manually.
Also don't forget that the addon scanners are shorter in range then some of the built in scanners.
Put a different way , you must select the roid and wait for the scanner to actually display the stats for the roid before will you be able to save the data and get the new roid message.
If this continues to be an issue any additional info you can prove is helpful such as screen dumps, log data and the exact ship and scanner your using along with the location you were scanning.