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.
@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.
@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.
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.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
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.
@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.
@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.
@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.
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.