Upon doing some testing I’ve noticed that randomly, alpha planes will act very weird. There appears to be no single reason that this happens… however, it only seems to happen if the ship in the back is shooting. That alone is very strange, because they all use the exact same code (they are their own objects however). At first I thought maybe it was just a coding mistake, and that the endpoints were inaccurate, but again, the bug only happens if the ship in the back is shooting; if the two on the sides fire at the same time, they are accurate, but if the one in the back shoots with them, one or more of the lasers will appear buggy.
Also, I don’t know if it’s just my graphics card (I am doubtful) but depending on the camera angle the lasers also seem to dissapear completely.
Has anyone had this problem before? And is there a solution? I would really like to stick with BGE because I absolutely love how easy Python is, but more and more small problems like this are starting to drive me away.
Also, if I add more ships and tell them to shoot as well, they will all appear to start bugging out like that. (however, you can see for a brief period of time that they all hit the correct spot, and then the just flash randomly into the wrong spot when another ship decides to shoot) … I’m convinced that it’s a problem with the game engine.
This is how I’m placing the planes. But like I said, the bug only happens when more than 2 (usually) ships are firing their lasers. Otherwise it works perfectly and lands exactly where it should.
import math
def manageEndPoints(laser, ship):
if laser['laser'] is True: #This is inside the turret script but only needs to be used if the weapon is a laser
mesh = laser.meshes[0]
target = ship.target.obj
#print(target)
base = laser.parent #This is the barrel of the gun
offset = (base.position.x - ship.obj.position.x) #Get the actual hardpoint position
if offset < 0: #If it's on the negative side of the ship, account for that
offset = offset * -1 #No negatives!
#3d distance formula
d = math.sqrt((base.position.x - target.position.x)**2 + (base.position.y - target.position.y)**2 + (base.position.z - target.position.z)**2)
#Get the front 4 verts of the laser
v1 = mesh.getVertex(0,0)
v2 = mesh.getVertex(0,1)
v3 = mesh.getVertex(0,4)
v4 = mesh.getVertex(0,5)
v1P = v1.getXYZ()
v2P = v2.getXYZ()
v3P = v3.getXYZ()
v4P = v4.getXYZ()
#Move them to enemy position, accounting for the position of the hardpoint
v1P.y = d - offset
v2P.y = d - offset
v3P.y = d - offset
v4P.y = d - offset
v1.setXYZ(v1P)
v2.setXYZ(v2P)
v3.setXYZ(v3P)
v4.setXYZ(v4P)
yep but as far as I can tell there’s no scale method for KX_GAMEOBJECT
you can see at the end of this video that they don’t appear to be bugging… it’s just weird.
Hey thanks a ton! Previously I believe it was on Alpha Blend, I switched it to opaque by accident (because I clicked it and forgot what the default was haha) and that fixed the flickering issue, also the scaling works great (so I was correct in thinking it was a BGE problem… with the vert.setXYZ methods I suppose?) also that works out great because scaling will always be reliable whereas setting vert positions relied on those positions corresponding to the endpoints.
I don’t know how I keep missing these methods (scaling, etc) because whenever I do a google search or an API search, nothing comes up. Maybe I’m looking at a way out of date API… ?)
And hey if you ever need any help, don’t hesitate to send me a message! You’ve just saved me from hours of frustration haha
