- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Engine → User Interface
- Assigned To No-one
- Operating System
- Severity Low
- Priority
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: PlaneShift
Opened by Piotr Rorot - 10.04.2008
Last edited by aurelynt - 01.08.2009
Opened by Piotr Rorot - 10.04.2008
Last edited by aurelynt - 01.08.2009
FS#1409 - can't target moving characters
I don’t know if targetting static characters was fixed (actually animating, but not running around), but it worked better than i checked last time.
Targetting moving characters is still missions impossible ;) lag, low FPS, other factors all make it extremaly hard to target moving object.
A good solution is to make it so that clicking an area close enough to the object will select it, not also clicking directly on the object. If there are two objects near, selected will be the closest one, so you will never end clicking thin air.
I have confirmed this in-game. When using Auto-run I have the mouse in a position where the object/person will be under my mouse and instead of “hooking” on the object/person, I get the green “move to here” symbol and my character goes off in that direction.
marking new due to Mythryndel’s comment
I have been playing with this further in a trunk build. This doesn’t seem to be a bug as much as trying to figure out exactly which part of the character you need to select. If i click almost exactly the middle of the character, then I can get it to select the character at almost any range, but If i select the upper body/head or the lower body/feet, it “hooks” the background and I head off in the direction of the green target select symbol.
Targeting works by determining which mesh is at the location you click (and what object that mesh is part of). This has been improved lately, so the problem may be gone. It is probably the same one that made you have to select a corps’ feet to target it.
Please retest.
Is this changed only in trunk or in stable (active on laanx), too?
(Iirc was I unable to target yet while autowalking, but when I walk targeting worked normal)
It is changed in trunk. Not sure if it was put on the stable client as well.
Let’s try to find out and get this one closed.
I was able to target normally while autorunning; so not able to reproduce in last days.
Sen
(Linux 32bit; nvidia proprietary drivers; self compiled client of unknown revision…)
It’s ok for me too.