If the unit that is trying to be selected is like an enemy to that player, it might be the default option of the map. You could disable this behavior in trigger editor, searching for action PlayerOverride ... then finding the appropriate option and then under tab Value decide to enable it or not. However this all might not be the case for you.
You see the Host , There are things like selectable in there .. this is passed down from the Parent ... this needs to be configured, can you tell me the ability which spawns that unit ?
I assume, you are talking about the unit using the PlasmaSurgeImpact model you created earlier?
Some models do not have a hitbox, they cannot be clicked. If you change it to a different model it should work again.
To fix this problem, create a new model, type Generic, call it Hit Test Sphere and change the Art - Model field to HitTestSphere.m3.
Then, create a new actor of type Model, based on Model Animation Style Continuous (with spaces), add a new Event: UnitBirth.YourUnit -> Create and change the Art - Model to use the Hit Test Sphere you just created.
Make sure, that Model Flags - Allow Hit Test is checked (it should be already). Now you should be able to select your unit. You can change the selection radius by adjusting the Scale of the actor.
I usually add Hit Sphere to custom models, for example the Reaver and Defiler. But I thought it was only to add a collision to the unit. (Without it the Reaver and Defiler do not interact with other physical objects, and it looks quite silly.) Never knew it also made them clickable!
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
What determines if a unit is selectable or not selectable?
For some reason I have a unit that can not be clicked. The flags of the unit look correct. I find nothing else that should make it not selectable.
Is this determined in some other way? In the actor?
If the unit that is trying to be selected is like an enemy to that player, it might be the default option of the map. You could disable this behavior in trigger editor, searching for action PlayerOverride ... then finding the appropriate option and then under tab Value decide to enable it or not. However this all might not be the case for you.
Hope it helps
I have no triggers on my map.
Imagie a Marine on the battlefield. You can click on it. Then you can move around with it, or attack.
I have created a unit that can NOT be clicked. Nothing happens when I click on it. Enemy units can attack it, but I can not select it.
Not sure what caueses it.
Any clue?
Under the unit flags check "Unselectable". It is near the bottom of the list.
That is what I thought too. But no matter if Unselectable or not is flagged, it still can not be selected.
If it is of any importance, the unit is spawned from an ability.
Under the Actor of the unit, go to Art: Model Flags -> Allow Hit Tests ... this might work, give it a try
Already flagged. Makes no difference.
You see the Host , There are things like selectable in there .. this is passed down from the Parent ... this needs to be configured, can you tell me the ability which spawns that unit ?
I assume, you are talking about the unit using the PlasmaSurgeImpact model you created earlier?
Some models do not have a hitbox, they cannot be clicked. If you change it to a different model it should work again.
To fix this problem, create a new model, type Generic, call it Hit Test Sphere and change the Art - Model field to HitTestSphere.m3.
Then, create a new actor of type Model, based on Model Animation Style Continuous (with spaces), add a new Event: UnitBirth.YourUnit -> Create and change the Art - Model to use the Hit Test Sphere you just created.
Make sure, that Model Flags - Allow Hit Test is checked (it should be already). Now you should be able to select your unit. You can change the selection radius by adjusting the Scale of the actor.
Thanks Kueken, i learnt a lot from that post.
Thank you Kueken. This solved it.
I usually add Hit Sphere to custom models, for example the Reaver and Defiler. But I thought it was only to add a collision to the unit. (Without it the Reaver and Defiler do not interact with other physical objects, and it looks quite silly.) Never knew it also made them clickable!