Forums » Community Projects

TargetLess plugin

«123456789101112131415»
Jun 29, 2008 maq link
Think you forgot to remove printinfo when opening options :)
(and on startup but i get that will stay anyway)
Jul 06, 2008 blacknet link
interesting bug here.

Target List 1.6.0 loaded...
/targetless -> display options
*** Lua error: iup handle expected
*** Stack trace:
1 [C]:-1 in iupGetTable (global)
2 lua/iup/iuplua.lua:77 in (null) ()
3 if/if_chatlog.lua:47 in chatprint (upvalue)
4 if/if_chatlog.lua:522 in print (global)
5 plugins/targetless/main.lua:116 in printinfo (field)
6 plugins/targetless/main.lua:120 in usercmd (field)
7 plugins/targetless/main.lua:223 in ? (field)
8 vo/vo_cmds.lua:12 in func (local)
9 vo/vo_event.lua:62 in (null) ()
10 [C]:-1 in xpcall (global)
11 vo/vo_event.lua:86 in _do_event (upvalue)
12 vo/vo_event.lua:106 in (null) ()
13 [C]:-1 in GKProcessCommand (field)
14 if/if_chatlog.lua:80 in (null) ()
15 (tail call):-1 in ()
sent lua/iup/iuplua.lua:77: bad argument #1 to 'iupGetTable' (iup handle expected)
stack traceback:
[C]: in function 'iupGetTable'
lua/iup/iuplua.lua:77: in function <lua/iup/iuplua.lua:74>
if/if_chatlog.lua:47: in function 'chatprint'
if/if_chatlog.lua:522: in function 'print'
plugins/targetless/main.lua:116: in function 'printinfo'
plugins/targetless/main.lua:120: in function 'usercmd'
plugins/targetless/main.lua:223: in function '?'
vo/vo_cmds.lua:12: in function 'func'
vo/vo_event.lua:62: in function <vo/vo_event.lua:60>
[C]: in function 'xpcall'
vo/vo_event.lua:86: in function '_do_event'
vo/vo_event.lua:106: in function <vo/vo_event.lua:102>
[C]: in function 'GKProcessCommand'
if/if_chatlog.lua:80: in function <if/if_chatlog.lua:54>
(tail call): ?
Jul 06, 2008 drazed link
Thanks for the report blacknet =) Any additional details for what you were doing at the time (I'm guessing just logged in?) and what other plugins you might have installed, or if you were running custom (un-pushed) if code along side? I'll see if I can reproduce this.
Jul 08, 2008 roguelazer link
Yay dead website...
Jul 08, 2008 drazed link
dead website? Anyone else seeing this, somethings not right with my DNS settings, most ISP's picked it up, I've seen a few ISP's where it just won't load =( If you are having trouble with the site you can get the plugin directly at
http://targetless.com/targetless.zip

If anyone else experiences http://trac.targetless.com not working please let me know so I can get to the bottom of this =)
Jul 10, 2008 Scuba Steve 9.0 link
trac.targetless.com is unreachable via the public DNS servers that I use(4.2.2.1 and 4.2.2.2)
Aug 25, 2008 ezra-s link
http://trac.targetless.com is not working for me either, luckily http://targetless.com/targetless.zip worked.
Aug 25, 2008 MSKanaka link
It's working for me... hm. Drazed, did you do anything funky?
Oct 20, 2008 drazed link
Updated to 1.7.

Link at top of first page of thread (with additional info)

Changes include:
* new layouts
* cycle hostile/friendly (cycle ship types that show up in list)
* Display capship shields
* Add logo to ingame targetless dialog (branding)
* roid distance (show distance from roids)
* Use the new systemnotes area to save roids. (per-character ore lists)
* roid backup/recover (save/restore the ore list, incase something goes wrong)
* Ore Sort (sort by ore type)
* clear sector ore (clear an entire sector)
* Hide lists (show/hide the various types of lists)
* lots of config updates
* Cargo expand overlap (fix bug with expanded cargo info overlapping)
* much much more!

Note: the dns issues should also be resolved. Let me know if anyone still has trouble accessing the trac site.

Note2: I will not be responsible for lost ore data or any other damage. Make sure you backup your config.ini file and system notes files. Don't come crying to me because you forgot.
Oct 20, 2008 IRS link
Nice thus far- I do appreciate that the saved roid info is now placed in the system notes, and split among several files. I had overloaded config.ini with the older version of targetless, resulting in it simply crumpling under its own weight. That hopefully won't be an issue anymore. The extended hull status bars for local ships let me get that information much more quickly, which is always helpful when fighting.

Now for the downside, which I found mostly in the reworked roid functions. The ability to remove individual roids has been misplaced over the change, unless it's actually something absurdly simple that I overlooked. If I accidentally add an unwanted roid, the only option for removal I can find is to purge the whole sector and start over, or manually edit the datafile outside VO- which brings up the next issue, wherein it's absurdly easy to accidentally add a wrong roid because additions aren't shown until targetless updates itself. I've already experienced a few situations where I tried to add one roid, only to switch targets and have a different one added instead. Put the update delay to a high value, and it gets really annoying.

On a final note, something I'd like to see as an option/feature would be the re-introduction of the old roid sorting in the list. Listing by highest ore percentages is nice, but the old method, where roids were listed in the order you added them, also had its advantages- namely, that since I added roids as I progressed through a field, the list formed a "sector roadmap" that would neatly direct me from one roid to another in a logical path. I'd also like to see the ability to manually order the list, as while Denise may only have about 25% Denic, she's a big roid, and can take a lot before getting too hot. I'd like to be able to move her to the top of the list, ahead of her smaller, quicker to tire sisters.
Oct 20, 2008 drazed link
Thanks for the suggestions IRS.

To start, your first problem already has a solution, you just didn't realize ;) If you target a roid and type /editroid it will bring up the edit/remove dialog and you can add a note or remove the roid. Also, targeting any roid that you already scanned will display the ore and note data even if it doesn't fit in the list, above in the targetinfo. Also, if you double click on a roid in the /targetless->Scanned Ore tab, it will display that same edit/remove dialog for the selected roid. I plan to document this on the trac soon(tm).

As for the old sorting, that's not really likely to happen, sorry :( But I will be making it possible to pin roids as you can ships. And will make them stay pinned even if you log off/back on ;) So you'll be able to have your trail roids pinned, and use the notes to find which is which. Hope that is satisfactory for now. Eventually I will add some sort of trailing stuff so you will be able to tell it to lead you to a roid... but that's a long way off.

Sooo, problem one is solved already, just make sure you set up the right binds. Problem 2 is gonna have a much more creative fix, hopefully you can wait till that is done.

Thanks again for the comments :D
Nov 10, 2008 IRS link
Well, I had a rather unpleasant experience with system delay during the last Nation War, as did several others, that apparently stemmed from targetless getting swamped by large numbers of targets. I was experiencing very noticeable pauses of up to a half second every time the list updated. It was so crippling that I had to boost away and scramble to set the update delay to a larger value so I could actually fight.

My gut feeling on the matter is that targetless is trying to present and keep updated too much information. While all the information is valuable when you initially encounter a target, a lot of it only ever needs to be displayed once- the faction standings in particular come to mind. The standings only need to be noted once, and then they've served their purpose for the remainder of the time you and the target spend in the sector.

I would propose a "light display" setting that could be used for crowded situations. It would remove most of the extraneous information, leaving only the faction-colored names, distance, and one hull percentage indicator, which are the only pieces of information I find useful once hostilities have begun. In essence, a quick smacking with the KISS design principle.
Nov 14, 2008 drazed link
I'd just like everyone to know that I am aware of the performance issues, as well as some memory leaks. I'm working hard to fix both. Should have a release sometime towards the end of next week that negates most, if not all, these issues.
Nov 14, 2008 Daare link
drazed: Just a quick note to let you know how much your work on Targetless is appreciated. It's a testament to its utility that everyone keeps on using it despite any problems.
Nov 15, 2008 blacknet link
hud scaled!
Hud Updated
*** Lua error: deleted iup handle referenced
*** Stack trace:
1 [C]:-1 in Detach (field)
2 plugins/targetless/lists/Controller.lua:311 in update (method)
3 plugins/targetless/lists/Controller.lua:298 in refresh (method)
4 plugins/targetless/lists/Controller.lua:301 in (null) ()
sent plugins/targetless/lists/Controller.lua:311: bad argument #1 to 'Detach' (deleted iup handle referenced)
stack traceback:
[C]: in function 'Detach'
plugins/targetless/lists/Controller.lua:311: in function 'update'
plugins/targetless/lists/Controller.lua:298: in function 'refresh'
plugins/targetless/lists/Controller.lua:301: in function <plugins/targetless/lists/Controller.lua:301>
sent plugins/targetless/lists/Controller.lua:311: bad argument #1 to 'Detach' (deleted iup handle referenced)
stack traceback:
[C]: in function 'Detach'
plugins/targetless/lists/Controller.lua:311: in function 'update'
plugins/targetless/lists/Controller.lua:298: in function 'refresh'
plugins/targetless/lists/Controller.lua:301: in function <plugins/targetless/lists/Controller.lua:301>
plugins/targetless/lists/Controller.lua:311: bad argument #1 to 'Detach' (deleted iup handle referenced)
stack traceback:
[C]: in function 'Detach'
plugins/targetless/lists/Controller.lua:311: in function 'update'
plugins/targetless/lists/Controller.lua:298: in function 'refresh'
plugins/targetless/lists/Controller.lua:301: in function <plugins/targetless/lists/Controller.lua:301>
plugins/targetless/lists/Controller.lua:311: bad argument #1 to 'Detach' (deleted iup handle referenced)
stack traceback:
[C]: in function 'Detach'
plugins/targetless/lists/Controller.lua:311: in function 'update'
plugins/targetless/lists/Controller.lua:298: in function 'refresh'
plugins/targetless/lists/Controller.lua:301: in function <plugins/targetless/lists/Controller.lua:301>

Can I rewrite targetless from the ground up?
Nov 15, 2008 maq link
No, i forbid you from doing it!
Nov 15, 2008 slime73 link
Uh... drazed is already in the middle of rewriting large sections of it.
Nov 15, 2008 Ion link
drazed, I posted this to the bugs section, since I wasn't really sure if it was a patch 1.8.46 - TargetLS conflict, or just something pertaining to the new patch, but I figure that I had best post it to both sections. So, here you go:



This occured upon being a bit too frisky with the F5 scaling function, and once I ran headfirst into this wall of lua text, I could no longer scale the interface.

And, since I haven't commented on the latest version of this plug-in... Brilliant work! It keeps getting better and better, and it was already the most essential VO plug-in. Thanks.
Nov 22, 2008 drazed link
[link removed, beta long over, stable released]

If anyone can help test this at this weeks nation war it would be much appreciated. Should have considerably lower impact on fps now. Also fixes the F5 hudscale bug, and some other minor bugs...

This is a beta version for a reason, there's a good chance I broke stuff. Use at own risk!

--drazed
Nov 23, 2008 vskye link
I just tried it a few minutes ago, here's what I found so far.
Left the station after fresh install, just outside of the station I typed /targetless and changed from ship bar to icon, exited config and then the station guards (2) would flash on and off in the targetless list. Target numbers going from 2 to 0 also. (every 2 secs about) Docked and relaunched, flashing gone.. no icons next to list, still a bar. Human player shows up, icons for him, npc's are all bar. I'll get some screenshots and such later and will test this more this afternoon to see how the memory leaks are going.