All protoss units have a Shield attach point defined for their model, and others don't. Since 1.3.0 patch, units without a shield attach point started generating this error: "Could not find e_attachShield or a dynamic shield attach on unit with model Marine" (or whatever the model is). I'm using the story mode dependency, haven't tested with others yet. It all worked well before 1.3.0 and the shield impact graphics were even visible on non-protoss units, but now it just creates the error.
I narrowed the problem down to the "ProtossShieldFacer" actor. If I disabled the "ShieldImpact" actor from using that as the "Actor - Visual Directional Facer" value, the error stopped, but the shield graphics weren't obviously visible anymore. I tried looking at and changing the values of the ProtossShieldFacer actor, including deleting all actor events from it, but the error persisted.
Any ideas how to get the shield graphics show up again? Maybe the solution could be related to the "or a dynamic shield attach" part of the error? My hotfix is just using validator "Is Shield Capable" and "Is Protoss" for the ShieldImpact actor creation event instaed of just "Is Shield Capable", so the graphics still show for protoss units and not for the others, which cause the error.
I don't think that it is now producing errors so much as it was always producing errors, and 1.3 just started to display them.
My guess is that 1.3 greatly increased error reporting capabilities.
I don't think that it now producing errors so much as it was always producing errors, and 1.3 just started to display them. My guess is that 1.3 greatly increased error reporting capabilities.
I second that, after fixing all my error messages, I can safely say, these were errors, which were present for a long time in my map, I just did not realize them (and I could explain some weird behaviors now).
Just tried to add a shield to a unit in my map and got the error. Never had this issue before (although Im not sure if I have ever added a shield effect before :D )...My guess is its the patch.
Rollback Post to RevisionRollBack
Feel free to Send me a PM if you have any questions/concerns!
Well, at least it reports the error now, But anyway, Just like before, to make shields show up, modify the unit's model data to add a shield attachment point, and make sure it has a shield radius and shield squib.
I don't get an error, but I cannot see the shields, it seems. The impact effects spawn at the correct location (just before hitting the unit), but no shield animation pops up. Any better solution than adding a behavior with a damage response + actor?
@Ranakastrasz: Go
Thanks, that worked... somewhat. It gives the large blue full shield bubble thing instead of the small white shield impact effects, though, but it's better than nothing.
Center instead of Origin might work better as the attach point for some models.
@Ranakastrasz: Go Thanks, that worked... somewhat. It gives the large blue full shield bubble thing instead of the small white shield impact effects, though, but it's better than nothing.
Center instead of Origin might work better as the attach point for some models.
So just following those steps gives you shield animation already? What am I doing wrong here?
it works for me if you follow it correctly
create new attachment property
set shield radius > 0
set squib to shield
For me, it seems to work for some units, for others not. For example the preserver models or the void seeker work properly, but Jim Raynor and Jim Raynor Commando just won't show up shields. The radius is big enough, I see incoming projectiles and attacks impact effects at quite some distance from the model, if the unit has shields.
Oh, one other thing, It has to pass the validator when the unit is created, specifically, on a certain shield actor, not sure which one it was, that says it has to have shielding, otherwise, no animation shows up. If you want an upgrade for an existing unit, you need to make the unit have a default of like one shield point, then remove it with triggers, or a behavior, and then add the shield back the same way.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
All protoss units have a Shield attach point defined for their model, and others don't. Since 1.3.0 patch, units without a shield attach point started generating this error: "Could not find e_attachShield or a dynamic shield attach on unit with model Marine" (or whatever the model is). I'm using the story mode dependency, haven't tested with others yet. It all worked well before 1.3.0 and the shield impact graphics were even visible on non-protoss units, but now it just creates the error.
I narrowed the problem down to the "ProtossShieldFacer" actor. If I disabled the "ShieldImpact" actor from using that as the "Actor - Visual Directional Facer" value, the error stopped, but the shield graphics weren't obviously visible anymore. I tried looking at and changing the values of the ProtossShieldFacer actor, including deleting all actor events from it, but the error persisted.
Any ideas how to get the shield graphics show up again? Maybe the solution could be related to the "or a dynamic shield attach" part of the error? My hotfix is just using validator "Is Shield Capable" and "Is Protoss" for the ShieldImpact actor creation event instaed of just "Is Shield Capable", so the graphics still show for protoss units and not for the others, which cause the error.
I get the same error.
I don't think that it is now producing errors so much as it was always producing errors, and 1.3 just started to display them. My guess is that 1.3 greatly increased error reporting capabilities.
I second that, after fixing all my error messages, I can safely say, these were errors, which were present for a long time in my map, I just did not realize them (and I could explain some weird behaviors now).
I was able to see the shield impact graphics before 1.3.0 when it didn't give an error. Now I can't see them and it gives an error.
Just tried to add a shield to a unit in my map and got the error. Never had this issue before (although Im not sure if I have ever added a shield effect before :D )...My guess is its the patch.
this is annoying... one strange thing: my pre patch saved and uploaded map, doesn't have this problem, only the new saved version
Well, at least it reports the error now, But anyway, Just like before, to make shields show up, modify the unit's model data to add a shield attachment point, and make sure it has a shield radius and shield squib.
I don't get an error, but I cannot see the shields, it seems. The impact effects spawn at the correct location (just before hitting the unit), but no shield animation pops up. Any better solution than adding a behavior with a damage response + actor?
the stone zealot for example had impact animations in patch 1.2
@Ranakastrasz: Go
how to do this?
http://forums.sc2mapster.com/resources/tutorials/8296-visual-shields-terran-or-zerg-with-shields/
@Ranakastrasz: Go
Yeah well, I did the exact same thing, no shield animation for me :)
hm is it possible to create an oval shield? the shield from the "guide" is always a ball
or at least increase the hightof the shieldball
@Ranakastrasz: Go Thanks, that worked... somewhat. It gives the large blue full shield bubble thing instead of the small white shield impact effects, though, but it's better than nothing.
Center instead of Origin might work better as the attach point for some models.
So just following those steps gives you shield animation already? What am I doing wrong here?
Did you increase the shield radius enough? If it's too small, it appears inside the unit and can't be seen.
@Kueken531: Go
it works for me if you follow it correctly
create new attachment property
set shield radius > 0
set squib to shield
@Ranakastrasz: Go
Thanks for help.
http://www.youtube.com/user/RussianMapster
For me, it seems to work for some units, for others not. For example the preserver models or the void seeker work properly, but Jim Raynor and Jim Raynor Commando just won't show up shields. The radius is big enough, I see incoming projectiles and attacks impact effects at quite some distance from the model, if the unit has shields.
Oh, one other thing, It has to pass the validator when the unit is created, specifically, on a certain shield actor, not sure which one it was, that says it has to have shielding, otherwise, no animation shows up. If you want an upgrade for an existing unit, you need to make the unit have a default of like one shield point, then remove it with triggers, or a behavior, and then add the shield back the same way.