What if you try some recursion like this. Essentially it performs pretty similar actions to your code, it's just pruned down a bit since it's recursive. But CC may not like recursion (I don't know) so if it works terribly, you can change it back into a for loop and work with that. Or there's the possibility of moving all the actual Pixel addition to a separate function if that might help.
Also keep in mind that this almost certainly won't work quite right - aside from any mistakes I made, there's not much safety to make sure it connects back to the end point, so it'll probably miss most of the time haha. We'd have to add in a bit of checking to make it try to make it aim for the endpoint when it gets close to it. Probably the easiest way to do that would be when count == 0, check if the startpos is less than 10 away from the endpoint, and if it is, set the directionangle to be the angle we need to get straight to the endpoint.
Oh, and if all my talk of recursion makes no sense to you, here's a link
Code: function Create(self)
self.Dir = 0;
end
--Update function, I'm just using pseudocode here since it's straightforward
function Update(self)
--Cast an obstacle ray from start to the max range of the gun, if it hits a target do stuff
if ObstacleRay from muzzleoffset pos using Vector(Gunrange, 0):RadRotate(self.RotAngle) ~= -1 then
--Check for HFlipped, swap Dir's value if this is backwards
if self.HFlipped == true then
self.Dir = -1;
else
self.Dir = 1;
end
--Make the starting lightning glowball effect or whatever (lazy nonworking version)
MovableMan:AddMO(CreateMOPixel("starting glowball"));
--Call the function to make inbetween lightning effects, where startpos is the muzzleoffset and endpos is the point where it hit an obstacle
MakeRecursiveLightning(self, startpos, endpos, self.RotAngle + RangeRand(-0.8, 0.8), 0); --The 2 0s are prevangle and count, prevangle is the previous angle it was fired at and count lets us make somewhat straight lines instead of complete messes
--Now make the lightning hit effects at the endpos (lazy nonworking version)
MovableMan:AddMO(CreateAEmitter("ending glowball"));
end
end
--This is the recursive function that will generate our in between lightning for us
function MakeRecursiveLightning(self, startpos, endpos, prevangle, count)
if SceneMan:ShortestDistance(startpos, endpos).Magnitude < 5 --5 should be some small number, basically if we're pretty much at our endpos
return; --We've finished making all the lightning, so we can return and ultimately go back to the update function
else
--If we've travelled more than 6 - 10 pixels in one direction, change the direction
if count > math.random(3, 5) then
--Because we want to try to hit the endposition, we reverse the direction and then add a bit of randomness to it
prevangle = -prevangle + RangeRand(-0.8, 0.8); --NOTE: I think reversing the direction is probably not what should be done, more likely we have to add 90 degrees to it or something
end
local offset = Vector(2*self.Dir, 0); --The amount we want to offset by each time (with direction), 2 pixels in this case
--Make the glow, change its position based on the angle we picked, then add it to the scene
local glow = CreateMOPixel("Glow Here");
glow.Pos = startpos + offset:RadRotate(prevangle);
MovableMan:AddMO(glow);
--Now that this glow is done, call the recursive function again, setting the startpos as the glow's pos and adding one to count
MakeRecursiveLightning(self, glow.Pos, endpos, prevangle, count+1);
end
end
Also, a couple things to note:
1. When you want random values with decimals, there's a seldom used but very useful function RangeRand(val1, val2). It's basically the same as math.random except it does decimals. I don't know which is more efficient or whatever, math.random is a lua library function whereas I think RangeRand is one of Data's C++ functions.
2. This isn't too important, but when you make variables that you're going to use later, it's probably a better idea to set them to nil instead of an empty vector or whatever. Particularly when it's more than just a number or boolean or string (i.e. if it's a vector or some other object). It makes it easier for someone reading the code to know if a value is going to be used as is or if it's going to be used later, and it probably makes your script infinitesimally cheaper.
|
