Some of my new units can't be group selected by dragging the cursor. I can't find any flag or anything on these units that could cause it. I think it started with 1.5.
I am having the same problem! This is so strange, for the longest time this was not a problem, and now one of my hero units can't be drag selected. Point selection still works fine, but drag selection does not work at all. Even if I drag select with nothing else in the region it will still not select the unit. Someone please help!
Model - selection layer?
I don't really know more in that direction. Might be good to check the unit's flags, too.
Does that happen with other units, if they use that model?
Does that happen if you just copy the Marine's actor and link it to your unit + deleting your old actor (for testing purpose)?
@Ahli634: Go No unit flag that I could find. One of my units is a simple duplication of the Sentry's unit/actor/model data and I compared them to no result. Still I can select Sentries but not my unit. So I set the Sentry's actor to use the custom model and I can't select it anymore, so its the model data that is bugged. There's nothing there that could cause the bug.
The model selection layer does nothing. I changed it from 1 to 0, which seems to be the default value for units. I applied the model to a different unit as you suggested and the selection bug was not there. So that clears the model as the problem.
When I changed the unit to have the Marine's actor the selection problem went away. I suppose this means the problem is with the actor, but where?
@Ahli634: Goits the model data that is bugged. There's nothing there that could cause the bug.
Did you test this by using this model with a different unit? When I did this the problem did not carry over to the new unit. Unless we are having different problems here, my thought is that the problem is actually with the actor.
@DaBernMon: Go I gave the custom model to the Sentry's actor and then I got the bug. So the only variable here is the model data or the model itself. As the bug didn't exist before 1.5 I believe the patch broke something, so I created a thread in blizzard's forums about it.
That's strange. We are having the same problem but it seems mine exists within the actor data and yours within the model data. I agree, it must be something that the patch caused.
If you don't mind, if you get a solution to the problem in the blizzard forum could you please share it here?
Probably the easiest solution would be to attach the Hit Test Sphere model to the unit, which seems to be specifically designed for this. It is an invisible, clickable sphere, which extends the radius in which the unit can be selected. Just make sure, the Allow Hit Test model flag for the attached model is checked.
€ I misunderstood the problem, this is for models, which cannot be selected at all (eg interceptor). However, if it is a model problem, this fix should work as well, try it out.
The radius should be easily adjusted by changing the Scale of the attached actor. Make sure, the Scale and Model Scale flags for the Inherited Properties are unchecked, otherwise the attached actor will inherit its scale from the host, ignoring its own scale.
Newer models, at least those made with the Blender addon, won't have this problem as the addon properly imports and exports hit boxes.
I remember a Blizz dev said they'd fix it in a patch, but it looks like they didn't. They may not do it, as it seems the previous system was unnecessarily cpu consuming as it used a per-pixel calculation to know if the model should be selected, and now it uses the boxes.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Some of my new units can't be group selected by dragging the cursor. I can't find any flag or anything on these units that could cause it. I think it started with 1.5.
I am having the same problem! This is so strange, for the longest time this was not a problem, and now one of my hero units can't be drag selected. Point selection still works fine, but drag selection does not work at all. Even if I drag select with nothing else in the region it will still not select the unit. Someone please help!
Model - selection layer?
I don't really know more in that direction. Might be good to check the unit's flags, too.
Does that happen with other units, if they use that model?
Does that happen if you just copy the Marine's actor and link it to your unit + deleting your old actor (for testing purpose)?
@Ahli634: Go No unit flag that I could find. One of my units is a simple duplication of the Sentry's unit/actor/model data and I compared them to no result. Still I can select Sentries but not my unit. So I set the Sentry's actor to use the custom model and I can't select it anymore, so its the model data that is bugged. There's nothing there that could cause the bug.
The model selection layer does nothing. I changed it from 1 to 0, which seems to be the default value for units. I applied the model to a different unit as you suggested and the selection bug was not there. So that clears the model as the problem.
When I changed the unit to have the Marine's actor the selection problem went away. I suppose this means the problem is with the actor, but where?
Did you test this by using this model with a different unit? When I did this the problem did not carry over to the new unit. Unless we are having different problems here, my thought is that the problem is actually with the actor.
@DaBernMon: Go I gave the custom model to the Sentry's actor and then I got the bug. So the only variable here is the model data or the model itself. As the bug didn't exist before 1.5 I believe the patch broke something, so I created a thread in blizzard's forums about it.
@SoulFilcher: Go
That's strange. We are having the same problem but it seems mine exists within the actor data and yours within the model data. I agree, it must be something that the patch caused.
If you don't mind, if you get a solution to the problem in the blizzard forum could you please share it here?
@DaBernMon: Go Sure. I think they would have to fix it in an update, but I'll post their answer here anyway.
So far I posted several bugs caused by 1.5 in their forums and didn't get a single answer from Blizzard, let's see if I get lucky this time.
I'm having the same problem with some custom units... has anyone found a fix?
Probably the easiest solution would be to attach the Hit Test Sphere model to the unit, which seems to be specifically designed for this. It is an invisible, clickable sphere, which extends the radius in which the unit can be selected. Just make sure, the Allow Hit Test model flag for the attached model is checked.
€ I misunderstood the problem, this is for models, which cannot be selected at all (eg interceptor). However, if it is a model problem, this fix should work as well, try it out.
That worked quite nicely! Now I need to figure out how to adjust the various radii in order to have easy unit selection.
The radius should be easily adjusted by changing the Scale of the attached actor. Make sure, the Scale and Model Scale flags for the Inherited Properties are unchecked, otherwise the attached actor will inherit its scale from the host, ignoring its own scale.
Newer models, at least those made with the Blender addon, won't have this problem as the addon properly imports and exports hit boxes.
I remember a Blizz dev said they'd fix it in a patch, but it looks like they didn't. They may not do it, as it seems the previous system was unnecessarily cpu consuming as it used a per-pixel calculation to know if the model should be selected, and now it uses the boxes.