CS2D
Scripts Imitating CS2D bullet [Solved]
Imitating CS2D bullet [Solved]
1 
Function e_add_sprite_line(x1#,y1#,x2#,y2#,r,g,b,alpha#) x1=((x1)*2)-640 y1=-((y1)*2)+480 x2=((x2)*2)-640 y2=-((y2)*2)+480 mesh=CreateMesh() EntityFX(mesh,16) surf=CreateSurface(mesh) verts = 0 AddVertex surf,x1#,y1#,640,0,0 AddVertex surf,(x1#+x2#)/2,(y1#+y2#)/2,640,0,0 AddVertex surf,x2#,y2#,640,1,0 AddTriangle surf,verts,verts+2,verts+1 ;EntityColor mesh,r,g,b ;EntityAlpha mesh,alpha# Return mesh End Function
Mora: That code snippet is just for rendering and doesn't help to solve your problem. MikuAuahDark says could actually be a good idea. Every call to a CS2D Lua API method comes with an overhead so caching things directly inside Lua may help. Definitely worth a try.
cache the movement vector instead of calling sin/cos every iteration (or even better: use a line algorithm like Bresenham) only do tile related checks if the tile the ray touches actually changed (by remembering the last tile it touched and comparing it with the current) mark all tiles which are overlapped by a player beforehand so you don't have to iterate all players for every ray pixel / or make a list of players which can potentially overlap the ray beforehand consider to skip pixels or to do some checks only every X pixels if you can afford to have less precision. e.g. only check for player collision every 2 pixels. 
Offlinelocal parts = math.floor(D/16)
local PD = {}
for i=1, parts do
px = px + math.cos(A) * ((i+parts))
px2 = px + math.cos(A) * ((i+parts+16))
py = py + math.sin(A) * ((i+parts))
py2 = py + math.sin(A) * ((i+parts+16))
PD[i] = image("gfx/mora/STALKER-LL/Items/1x1.bmp",0,0,1,0)
local rD = math.random(-4,4)
imagepos(PD[i],px+rD,py+rD,math.deg(A)+90)
tween_move(PD[i],200,px2+rD,py2+rD,math.deg(A)+90)
imagealpha(PD[i],0.7)
tween_alpha(PD[i],200,0)
imagecolor(PD[i],255,255,0)
timer(200,"parse","lua freeimage("..PD[i]..")")
end
Mora: mathfunctions are not localised and called globally every iteration
The variables are not localised so they might conflict with other similar global varibles. This is both slow and just generally bad practice. (px, py, ...) This code isn't contained within a function which isn't a big deal but probably means that the average Joe won't be able to as easily implement it in their code The timer will free the image even if the round ended which can cause visual glitches and problems. Generally not my cup of tea when it comes to spacing, or lack thereof 1