Loot collection accuracy

cookereptiles

Hello,
I have a question I’m hoping someone can help me with. I’m dropping items straight into the world for the player to collect (loot etc), I also have a hud that appears when cursor hovering over the item to show what it is. This works great in open areas on normal terrain but when in more dense areas I have to get camera angle just right for the over mouse hover to register on the item, else the hud won’t show and the player can’t collect it. Does anyone know how to improve the accuracy of this?

Thanks

GeneralK

@cookereptiles try making the collider larger on your prefabs or adding a collider to them that is big enough to get the mouseover easier.

I use loot from corpses and I have a collider set to is trigger that is actually disabled on the combatant prefabs and is enabled during the death schematic, it gives a much larger click box than the actual size of the combatant models

cookereptiles

Thanks for the tip. The colliders work perfectly in some areas but not enclosed dungeon areas even when the mouse is right over them. I’m thinking there must be a way to improve this through the layers but I’m not sure how to adjust it so or only checks certain layers.

GeneralK

@cookereptiles have you paused the game in play mode in editor, and looked at the collider to determine what is getting in the way of it?

Are you using a mesh collider on it which would make it small tight to the model or do you have like a sphere collider that gives a larger area to click?

If you know what is getting in the way and it is on it's own layer and does not need to be clickable then sure you can remove that layer from the raycasts. Or don't have an is trigger clickable collider on what is in the way maybe. Either way you first need to figure out what in the dungeons are blocking the loot. Is it like the ceiling going transparent but still in the way or the floor or rocks or ?

cookereptiles

Thanks. If I can find out how to filter raycast to the correct layers it’ll be fine but this is not being collected through a schematic where I can just filter the raycast layers. It seems to be an automatic system in ORK, so I’m not sure how to filter it. It’s probably really simple but I’m not sure where it is.

cookereptiles

There are other trigger colliders on different objects that I think are causing the issue. I’ve found a layer mask filter setting in game controls, cursor raycast settings, but this doesn’t seem to filter out the other triggers even though they’re in a different layer.

gamingislove

The raycast for this should use the raycast settings found in UI > HUDs > General Settings.

cookereptiles

Thanks GIL I’ll give that a try.

cookereptiles

Hey, I’m finding this isn’t resolving the issue. If there are any other triggers over lapping when trying to click on dropped loot, it gets in the way and I have to zoom in really close to register the click on the loot. Again, it’s fine in areas where’s there’s not lots of triggers. I’ve tried altering the ray cast in ui/ HUD’s- general settings and in the game controls, neither makes a difference with the dropped loot objects.

I could do this manually with my control schematics if I can figure out how to adjust the automatic clicking settings, as the loot collection upon mouse click seems automatic.

The HUD’s appear over the objects as expected now, it’s just the physical collecting.

gamingislove

For interactions the raycast is handled using the Interaction Settings > Cursor Raycast Settings in Base/Control > Game Controls.
If anything defined in the layer mask there is between the camera and the interaciton it'll be blocked by it.

cookereptiles

Hey GIL, I must be doing something wrong because setting this layer mask to nothing still doesn’t fix the problem, it’s still being blocked by other triggers in other layers. Is there a way I can turn off the default interaction on loot drops so I can use the item collect node from a schematic raycast?

gamingislove

Setting the layer mask to nothing will in fact not hit the item's collider, so it can't cause the interaction.
You can set your item collectors to have no start type, e.g. click on the None button on the component's start settings.

cookereptiles

Hey, actually, setting the layer mask to nothing makes no difference, I can still collect them if there’s nothing blocking. I’m not sure that setting works.

gamingislove

Can you show me your interaction settings (Base/Control > Game Controls) and the item collector's start settings?

cookereptiles

Hey,
Interaction settings:

Interaction control: interaction Controller
Interaction Key: Accept
Start cursor interaction: true
Max interaction distance: -1
Max Mouse Distance: -1

Interaction Controller Settings
Add automatically: false

Cursor Raycast Settings
layer mask: UI, Lootbox (have tried everything and nothing, doesn’t change it)
Raycast Distance: 20
Find Interaction: Only hit (have tried all, doesn’t make any difference)
From root:false (have tried both)

Line of sight
Use raycast: false

Move to interaction
Use move to interaction: false

Auto stop interaction
Only in control: false
Auto stop distance: 10
Ignore distance: all false
Ignore radius: false

cookereptiles

Item collector settings on the dropped objects:
Start type is set to interact

Machine type: none
Asset source: reference

Interaction: interact is true, all others false
Max iteration distance distance:3

Move to interaction is false.

cookereptiles

Versions I’m using:
Makinom: 2.15.1
ORK: 3.16.2

gamingislove

First of all, I'd recommend updating to the latest version - since ORK 3.16 was already some time ago, this might have been already fixed.

Otherwise, the Raycast Distance might be a little low, though that depends on your camera setup. The distance is from camera, i.e. if your camera is farther away this might miss your interactions - try 100 or more.

On your interactions, the Max Interaction Distance of 3 will also prevent using it if the player is farther away than that.

cookereptiles

Hey GIL
I’ve tried the distances etc all already and it’s not them. The raycast setting simply doesn’t make any difference on my current version, with no overlapping triggers it works fine. I am reluctant to upgrade as I attempted it a few months back and received multiple problems, especially with group members not spawning behind the player at certain distances and I had to roll it back, I also got a game breaking error trying to equip any dropped items from enemies. I’m over 2 years into a large project so sending over a copy of the project isn’t viable.

I understand I will have to pay to update to the latest version. Has this issue and the equipping dropped items error been fixed? I’d rather not shell out a load of money if I’m going to have to roll back to this version anyway.

cookereptiles

Hey, I have purchased the latest version of ORK (again), updated, and I can confirm that the raycast layer function still doesn’t make a difference and the equipping items bug I reported in December is still there making it unusable. Switching items between party members with items that can be used in multiple slots eventually throws out an error and stops working. This could be a problem with how my equipment slots are set up.

How to reproduce error: make 6 equipment slots that can all hold the same type of item, rings for example. Spawn in a group member and equip him with 6 rings via schematics. Unequip some of them and try to equip them on the player, this eventually throws out an error. Saving and reloading fixes it.

Spawn in enemies, equip them with a schematic, get them to drop their equipment via a death schematic, pick up the equipment and try to equip it, throws an error. Trying to sell the items also throws and error.