Intent: I'm trying to attach a raven to the back of a zealot. I have a ModelAddition actor with the raven model that attaches to a zealot when one is created and uses local offset and rotation site operations.
Problem: The raven attachment does something strange while the zealot is standing still. It's hard to explain. The raven glitches/jumps/rotates around the zealot, as if it was having trouble finding an attachment point. The attachment behaves perfectly as intended while the zealot is in motion.
What I've Tried: I tried changing both the raven and zealot models to different ones and got the same effect. I've tried 3 different attachment points and tried using triggers instead of data in order to attach it. No dice.
I had a similar issue a while ago, where I attached an actor to a turret that rotated, but while the unit was standing still it didn't attach properly to the turret and just held position. When the unit with the turret moved it attached properly and rotated with the turret.
After I remade the exact same modeladdition actor again (it was the exact same, I checked it like 10 times and even redid it with the old name and it didn't work. Maybe I'm just insane, I don't know :D) with another name it worked completely fine. I have up to this day no idea what caused this bug. So I can't really help, but recreating the ModelAddition from scratch with another name and new SiteOps with other names might help.
So I was able to fix this problem but I'm still not sure why it occured. The Explicit Rotation site op actor I was using was supposed to point the raven upwards, so it had forward and up vectors of (0,0,1). After I changed the up vector to make it tilt a little bit, there was no problem at all. So I don't really know what happened, must've been some bug or glitch that related to that certain set of circumstances. Thanks guys.
So I was able to fix this problem but I'm still not sure why it occured. The Explicit Rotation site op actor I was using was supposed to point the raven upwards, so it had forward and up vectors of (0,0,1). After I changed the up vector to make it tilt a little bit, there was no problem at all. So I don't really know what happened, must've been some bug or glitch that related to that certain set of circumstances. Thanks guys.
Oh, no, thats no bug.
You basically tried to rotate two different sides of the model into the same direction (both the front and the top of the raven downwards). That causes some glitches (although it doesn't error immediately like it should normally) as you would expect :)
I'm glad you were able to fix it.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Intent: I'm trying to attach a raven to the back of a zealot. I have a ModelAddition actor with the raven model that attaches to a zealot when one is created and uses local offset and rotation site operations.
Problem: The raven attachment does something strange while the zealot is standing still. It's hard to explain. The raven glitches/jumps/rotates around the zealot, as if it was having trouble finding an attachment point. The attachment behaves perfectly as intended while the zealot is in motion.
What I've Tried: I tried changing both the raven and zealot models to different ones and got the same effect. I've tried 3 different attachment points and tried using triggers instead of data in order to attach it. No dice.
Has anyone run into this issue before?
WHat other SOps are being used by the actors?
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
SOpAttachHardpoint (this has been changed to a few different ones), an explicit rotation and a local offset all on the attachment.
I had a similar issue a while ago, where I attached an actor to a turret that rotated, but while the unit was standing still it didn't attach properly to the turret and just held position. When the unit with the turret moved it attached properly and rotated with the turret.
After I remade the exact same modeladdition actor again (it was the exact same, I checked it like 10 times and even redid it with the old name and it didn't work. Maybe I'm just insane, I don't know :D) with another name it worked completely fine. I have up to this day no idea what caused this bug. So I can't really help, but recreating the ModelAddition from scratch with another name and new SiteOps with other names might help.
@Bommes: Go
So I was able to fix this problem but I'm still not sure why it occured. The Explicit Rotation site op actor I was using was supposed to point the raven upwards, so it had forward and up vectors of (0,0,1). After I changed the up vector to make it tilt a little bit, there was no problem at all. So I don't really know what happened, must've been some bug or glitch that related to that certain set of circumstances. Thanks guys.
Oh, no, thats no bug.
You basically tried to rotate two different sides of the model into the same direction (both the front and the top of the raven downwards). That causes some glitches (although it doesn't error immediately like it should normally) as you would expect :)
I'm glad you were able to fix it.