Before the patch, using doodads for unit models was not without issues but now there's a really serious issue. It will no longer let you drag select, double click select, or even control+click select units of the same type if they are using a doodad. I'm guessing this is because of the absence of attachment points or something along those lines. I have been trying everything that I can think of to remedy this, but so far nothing has worked. I even tried attaching the "InvisibleUnit" model and making it _Selectable, but it seems to have the same issue as doodads. I also used it as a base model to test, and it cannot be group selected either. I'm wondering if anyone else has a solution to this? It's very frustrating because I can't find anything on this anywhere.
@strongfoe: Go It is most probably caused by the lack of Hit Tests, both Tight and Fuzzy. Patch 1.5 changed how the game handled it and maybe they changed it again. Have you tried attaching it to the Test Sphere model and make it invisible? I guess that was the model most people used to solve this issue.
@SoulFilcher: Go
This actually worked, omg! Thank you!! I was on the right track I guess, just wasn't attaching the correct model. I replaced the invisible unit model with the "HitTestSphere" and now I can do all the click functions that I previously couldn't. Luckily the hit test sphere is already invisible so all I had to do was change the model field and adjust the scale/selection circle to match the unit's size. I don't see why Blizzard didn't plan for this to begin with, did they really assume that map makers would not use doodad models as units? Or the bigger question, were they just lazy...
To anyone else who has this issue who comes across this thread, just create a Model actor of type ModelAddition, linking to a model using HitTestSphere.m3. Make sure the field "Actor: Aliases+" has the alias "_Selectable". Then attach it to your unit, either through the unit or the model actor events. I prefer to attach models through the unit actor events (ActorCreation>>AttachModel). The only downside is through this means the model does not show up in the object explorer, but I find this to be much quicker than setting up hosting for the model itself.
Does your solution suffer from the same problem that my first solution suffered from:
Changing the unit owner makes the unit unable to be selected?
If yes, I solved that and am working on a user friendly way to set that up. (My solution is already somewhere in the forum in a demonstration map with rotating, selectable question mark models).
Before the patch, using doodads for unit models was not without issues but now there's a really serious issue. It will no longer let you drag select, double click select, or even control+click select units of the same type if they are using a doodad. I'm guessing this is because of the absence of attachment points or something along those lines. I have been trying everything that I can think of to remedy this, but so far nothing has worked. I even tried attaching the "InvisibleUnit" model and making it _Selectable, but it seems to have the same issue as doodads. I also used it as a base model to test, and it cannot be group selected either. I'm wondering if anyone else has a solution to this? It's very frustrating because I can't find anything on this anywhere.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumdid you try making a copy of the doodad actor that is a unit type actor?
Still alive and kicking, just busy.
My guide to the trigger editor (still a work in progress)
@strongfoe: Go It is most probably caused by the lack of Hit Tests, both Tight and Fuzzy. Patch 1.5 changed how the game handled it and maybe they changed it again. Have you tried attaching it to the Test Sphere model and make it invisible? I guess that was the model most people used to solve this issue.
@SoulFilcher: Go This actually worked, omg! Thank you!! I was on the right track I guess, just wasn't attaching the correct model. I replaced the invisible unit model with the "HitTestSphere" and now I can do all the click functions that I previously couldn't. Luckily the hit test sphere is already invisible so all I had to do was change the model field and adjust the scale/selection circle to match the unit's size. I don't see why Blizzard didn't plan for this to begin with, did they really assume that map makers would not use doodad models as units? Or the bigger question, were they just lazy...
To anyone else who has this issue who comes across this thread, just create a Model actor of type ModelAddition, linking to a model using HitTestSphere.m3. Make sure the field "Actor: Aliases+" has the alias "_Selectable". Then attach it to your unit, either through the unit or the model actor events. I prefer to attach models through the unit actor events (ActorCreation>>AttachModel). The only downside is through this means the model does not show up in the object explorer, but I find this to be much quicker than setting up hosting for the model itself.
Assets\Units\Test\HitTestSphere\HitTestSphere.m3
Does your solution suffer from the same problem that my first solution suffered from:
Changing the unit owner makes the unit unable to be selected?
If yes, I solved that and am working on a user friendly way to set that up. (My solution is already somewhere in the forum in a demonstration map with rotating, selectable question mark models).
Made a wizzard for my solution and made my actor a bit easier to use via token.
With the wizzard, you should easily find scaling values for your unit
Have fun fixing selection problems of units with that. :)