I'm trying to create a beam from one unit to another so that I could turn it on and off by using triggers. I've tried looking at how medic and void ray beams are done but the best I've managed so far is creating a new beam and destroying the old one every 0.5 seconds.
There's also an issue with the impact site ops. I'm creating the beam between two Motherships, and trying to set the impact site ops to attach to the target's center, and most of the time it does that, but at random it attaches to one of the "corners" of the Mothership instead of its center and I have no idea why.
I'd rather someone explained this from scratch than showing what I've done so far, because it's too screwed up to try to repair.
If you don't need multiple beams, the easiest way to do this would probably be by using global references. Send actor messages to the motherships, setting them as your references for the beam and set the launch and impact hosts of the beam to the references. To show and hide the beam, you can send actor messages to the beam again.
There are multiple motherships and each of them can have one beam active at a time to any of the others. One mothership can have multiple beams targeted to it, but can only send one itself.
Btw, almost forgot, major credit goes to Renee and his (her? I recall reading somewhere that Renee might be a girl) GAx3 mod, which made things much easier for me. You can use that mod as well, if you wish, it provides a similar function to create beams.
€ Once you teleport, you are static for about 5 seconds? While it certainly helps with making lag not an issue, it doesn't sound much fun, either. Seems to have very stale gameplay, if you do not plan to add some other twists.
I'm trying to create a beam from one unit to another so that I could turn it on and off by using triggers. I've tried looking at how medic and void ray beams are done but the best I've managed so far is creating a new beam and destroying the old one every 0.5 seconds.
There's also an issue with the impact site ops. I'm creating the beam between two Motherships, and trying to set the impact site ops to attach to the target's center, and most of the time it does that, but at random it attaches to one of the "corners" of the Mothership instead of its center and I have no idea why.
I'd rather someone explained this from scratch than showing what I've done so far, because it's too screwed up to try to repair.
If you don't need multiple beams, the easiest way to do this would probably be by using global references. Send actor messages to the motherships, setting them as your references for the beam and set the launch and impact hosts of the beam to the references. To show and hide the beam, you can send actor messages to the beam again.
There are multiple motherships and each of them can have one beam active at a time to any of the others. One mothership can have multiple beams targeted to it, but can only send one itself.
Then somewhat more like this, maybe? I was curious myself, so I experimented a little.
Ah, thanks. That piece of custom script to create the beam with triggers is all I needed! ^^
Now I can just create or destroy the beam with triggers whenever needed.
And here's what it's for!
Btw, almost forgot, major credit goes to Renee and his (her? I recall reading somewhere that Renee might be a girl) GAx3 mod, which made things much easier for me. You can use that mod as well, if you wish, it provides a similar function to create beams.
€ Once you teleport, you are static for about 5 seconds? While it certainly helps with making lag not an issue, it doesn't sound much fun, either. Seems to have very stale gameplay, if you do not plan to add some other twists.
That's not a gameplay test, just a test for the controls. The delay after teleport has nothing to do with Battle.net lag.