PlaneShift

/target next item

I would suggest to use the bounding box of the to-be selected entity instead of only a little part of it in the center. If bounding boxes overlap and the user clicks in this area, the distance should be calculated from the point where the user clicked and the center of each of the target bounding boxes.

I am not sure if this is a general CS issue or PS specific. Assigning Jorrit to comment.

It is a PS issue.

Jorrit, is there a standard CS way of determining to what object the pixel you clicked on belongs to?

Yes, sector→HitBeamSector().

It now uses sector→HitBeamPortals (when not in mouselook+!first person). I will check if there is something wrong with the calculation of the beam begin and end points, but since it often does work, it cannot be too wrong.

Baletar reports difficulties when he’s trying to target NPC’s in the tutorial.

His OS is Windows XP.

Description: On first select, it works fine. Once clicking outside, targetting becomes difficult. A relog fixes the issue temporarily, until the first targetting + untragetting.

Update:
I (Lanarel) hijack this report as very recently in trunk with CS1.9 at least on windows targeting has become almost impossible. Not only for me, but also other testers. Maybe windows only. Increased priority to keep this visible enough to get fixed with other CS related problems

Actually in trunk with CS 1.9, the actual targeted point and the point where the user clicked are not the same. This is obvious when double left clicking a point on the ground not too close from your char in order to have him move to that point (try it and look what point is highlighted!). The same problem happens when targeting an item. One clicks on it but actually it’s another point that is targeted.

I’m not 100% sure if this is the same issue as the one mentionned in Talad’s original post though. With CS 1.4 on Laanx, I have no trouble targeting items/NPC but the lake mushroom : it’s just impossible to target them !

Adding PS#2598 as dependency since it had already been opened by ThomPhoenix and I’m not 100% sure it’s a duplicate of this one.

This is definitely a PS bug. It would be more helpful if PS revisions were given since the CS version doesn’t matter.

Fixed in CS.

Targeting of characters and items works ok again, but the lake mushroom still has a problem. F-rd found out it is a map problem, with an invisible square covering the mushroom (and clicked instead).

Perhaps change the name of the bug report, or open another?

Imho, the issue with the mushroom is more of a ‘map’ issue.
The mushroom is located below a plane that was put there in order to simulate mist (texture associated to the plane: bdcavemist). This plane is especially obvious on this pic because of the wrong interaction between it and the character’s shadow:

When this plane is between your camera and the mushroom, no way to target the mushroom. But if you change your view so that your camera is located below that plane and above the ground, you have no more problem targeting the mushroom.

Added dependency to PS#2468. Same causes.

Added the nohitbeam support to the exporter. We can now flag meshes that should not be clickable. I added this flag to the water in bronzedoors, so all items dropped in water should be selectable now. Available at next bronzedoor update.

Tested. Works fine :) It’s easy to pick up the mushroom now.
Also dropped something into the water: Targeted it with ease (camera above water level).

The nohitbean flag will also fix  FS#2468 .

Peeg, you are allowed to close bugs that are fixed :)