Occasionally, when I run /targetless from cmdline and change some setting, game will crash when:
+ jumping
+ launching from station

I posted crashinfo to devs.

It didn't ever happen before, when I used no plugin.

Thanks!

"I posted crashinfo to devs."

This doesn't help me at all, since I'm not one of the devs. Thought if the game full-on crashed it is likely not a plugin problem (though always possible it's an iup mishap).

Anyhow, I will try and look into this, but don't expect to find much with such limited information. Let me know if the devs get back to you with any other info pointing this crash at this plugin.

Drazed, can you release new version with that re-targeting bug fixed, please? I think you said it is already fixed in SVN. Thank you.

Patience is bitter, but its fruit is sweet. If you absolutely can't wait, pull it from svn and help test future versions :)

Yeah, true about patience. As well as that quote about real men keeping their word and so on.

Thanks, it is OK. I was just asking.

Pulled the latest svn a few days ago drazed, seems to be working just fine.

I am getting the crashes right after I set the binds.... targetless does appear to be the culprit

Also It would be helpfull to be able to display turrets only/first at times....

"I am getting the crashes right after I set the binds.... targetless does appear to be the culprit"

Crashes? Can I have more detail then that please?

As for having turrets/players/etc show up first, a future version will allow you to setup specific type of ships to auto-pin to the top of the list, soon(tm) ;)

Not much to tell - I clicked the bind key for # (reinstall) and then launched a few secs later..... the program immediately crashed leaving nothing in the log files. Targetless was the only change.

(I had to remove tls earlier as it was interfereing with my scan plug-in which also uses the radar.)

for a little while now, i've been having a rather annoying problem with targetless...

i can get in a warthog miner, or put a scanner on any other ship and go to a roid that i know isnt saved in TL, and try to manually or automatically save it and it either says "You need to scan it first!" or dosent say "Ore saved!" (as it would if it were automatically saved).

i've even went so far as to remove every other plugin except targetless to see if that corrected it.. nope, still doing it. and i also re-downloaded the targetless zip file and replaced everything in the plugins folder for targetless... still doing it. (currently using files from the fresh download just got tonight.. with absolutely no other plugins in... but still getting "you need to scan it first")

also.. i thought the on HUD roid list changed with the sort order in the targetless interface... or at least i remember being able to sort the roids in the hud list somehow.. so if say... i'm looking for apicene in odia M14, i could get all the apicene roids to the top of the list. at least i remember being able to do so.. but i cant get it to do this either (idk.. i might just be crazy on this one and its never been possible too)

"also.. i thought the on HUD roid list changed with the sort order in the targetless interface... or at least i remember being able to sort the roids in the hud list somehow.. so if say... i'm looking for apicene in odia M14, i could get all the apicene roids to the top of the list. at least i remember being able to do so.. but i cant get it to do this either (idk.. i might just be crazy on this one and its never been possible too)"

You can set the default sort in /targetless -> Options -> Ore interface. Additionally, you can set the "cycle sort" bind in /targetless -> Controls -> Custom (or bind /lssort manually).

As for the scanning not working, try restarting the game, also try a different sector. Is it just a particular roid not wanting to be scanned (in which case let me know where so I can go track it down) or all roids in general (in which case your targetless system notes file may be corrupt). If all else fails the next update (not sure on release date yet, but am planning for early-mid march) has a few lines of code to address adding roids and those may sort out your issues.

Cheers

the "You must scan it first!" has actually been going on for weeks or longer, through many restarts and total shutdowns of the vendetta client, and i've tried saving roid(s) in so many different sectors i couldnt even begin to try and count them all lol.

but roids that i've had saved forever still show up in the ore list and still function as far as i can tell is normal operation for TL... just i havent been able to save any 'new' roids into the TL ore list.

and the current TL in my folder was just freshly re-downloaded and replaced, also removed every plugin except targetless and it still gave me the "you need to scan it first!" (with a warthog ME or any other ship with a mineral scanner equipped)

Can you please try creating a new character and scanning on that? Roids are saved per-character... Just wondering if the problem is due to your current characters having a corrupt list or hit some sort of limit, or if it's due to something else on your particular setup.

Cheers

well awlrighty then..

after making a new character, clicking through the 3 tutorials and killing enough orun collectors to sell their scrap to get 2-4k to buy a scanner.. finally get to a regular station to buy that scanner and decide to manually bind the buttons i needed to test it out...

turns out + is not the button to save a roid with lol
but i tested hitting + anyway before hitting the 'default' button for adding a roid, and got the same thing i've been getting for a while now... then i hit = and got ore saved, then + again and got the window to edit a roid.

guess the plus side is my list notes or w/e that has all the previously saved roids in it isnt messed up lol

woot :D

1.7.12 released

This is mostly a bug-fix release. Addresses thee following and more.

* Fix option-reset on /targetless open/close (no longer reset fontsizes, faction icons, etc)
* station turrets now show up on capital-ship list (lists will be dynamic/configurable in the future)
* queens show up on cap-ship list, regardless of where they are (HS/static/etc).
* fix next/prev rollover after #key usage
* cleanup some code (especially unused locks)
* fix missile re-targetting after sector change (to re-aquired target)
* fix crash on /targetless ui close after reloadinterface
* other minor bugfixes
* you can now scan a roid with auto-save off, and it will save a temporary copy of the data until you change your target or officially save it. It also updates the display, so that you can see what was in the roid, even if you move out of range, as well as being able to save the roid if you move out of range. (contributed by draugath)

For screenshots, download, and lots of additional yum! go to [TargetLess.com]
or download direct [targetless.zip]

I installed 1.7.12 last night (on a Mac OS system, if that helps) but had to remove it after three game crashes and a UI freeze. The symptoms absolutely tracked the presence of TL (the only plugin I have installed), but they were otherwise random; one was at the loading screen (about 50% into the preload), one was in open space, one was idle in the station UI and the freeze was while accepting a mission.

Is there any data I can gather from these crashes that will help you? (I suspect not, but just checking...)

Hi Zippe,

Some quick answers to the below questions would be helpful, as well as last bit of your ~/.vendetta/errors.log file (on OSX I believe you right click [or 2finger click or whatever OSX uses for that] the application folder, select view contents, and the error.log file will be in there) after a crash occurs.

What are your system specs? Especially your available ram?

Your [targetless] section from the config.ini file (same folder as the errors.log file) might help too.

please email the errors.log and config.ini entries if possible, to drazed [@] gmail [.] com

I'm using the latest version on Mac OS X with no issues. Plox integrate cargolist! gg

Something like this should really be in-game native. Its a bit annoying to hit M, scanner log ETC... while in combat.