Drawing projectile curves

Help and Feedback Scripting Support
#1

How’dy!
If you’re familiar with shooters, or games in which you have the ability to throw items (Ex. Grenades, Boxes, etc) you may notice that they help you estimate where your item is going to land with a visual curve displaying it’s estimated path.
I’m wondering the best possible way to achieve something similar to that, I’m thinking some sort of raycasting based on the bodygyro, although I’m not 100% sure how I’d go about that.

Throwing items is going to be a very big part of the game, so if it’s clunky or hacky (Basically if I made it without knowing how) the game won’t be enjoyable to play.

Thanks for reading!

5 Likes
Projectile Curves System
#2

For most customization on the beam (glow, transparency, color, texture) you probably want to use beams. Whatever you use (beams, parts, GUI) you will still need to figure out the actual flight path. The best way to ensure you are predicting the correct path is to not estimate the flight curve and set that as the display, but to calculate a custom flight curve and use that for both your display and the actual projectile flying; that way Roblox physics can not interfere with your indicator.

#3

What’s the best method to accomplish this?
Some sort of raycasting?

#4

Beams and ray casting could be a working solution but the problem is that rays are a line that is finite in one way but not in the other, so it means that curves cannot be accomplished with a single ray I guess

#5

what i recommend is you find the angle between the start lookvector and finish lookvector, like

angle = math.acos(startLookVector:Dot(endLookVector))

then in a loop, rotate it each iteration by the divison of angle / times
like

local throwSpeed = 2.5
local duration = 10

for i=1, duration do
     grenade.CFrame = grenade.CFrame * CFrame.new(0, 0, -throwSpeed) * CFrame.Angles(angle / duration, 0, 0)
     game['Run Service'].Stepped:Wait()
end

you will have to adjust it a lot, but this is a pretty good way of doing it

1 Like
#6

Would I use Bezier curves?

#7

That might work, but in the case that it fails or doesn’t work properly two things will happen:
1 The item will freeze in place if it is anchored, if it’s not it will behave odd
2 It will eat up a lot of memory regardless

#8

true, and ik this sounds like a ton of work, but you could make it extremely reliable and smooth if you fire to each client to do that math

#9

Yes, Bezier Curves would be good in a case of a grenade launch trail for example. You would need to get the initial position of the grenade and the final position that the grenade achieves. Now you would need to get a method to display that (Parts, GUIs or beams).

#10

Beams will work, but how would I get the ending position?

#11

Well, you could get the maximal set magnitude and add it with the direction the object goes at, because I’m sure you would want to limit the distance so the object doesn’t fly at 500 studs.

#12

Raycasting is not necessarily required, but it can help to predict a point where your projectile will stop/hit/bounce in the world. The basic premise is to create a function for the flight path dependant on starting location, starting velocity (usually the player’s character velocity plus their “arm strength”), and flight direction. Optionally you want a custom curve function for each projectile you make (heavier projectiles might fly less far, paper planes might fly very far). The ideal curve is a parabola (that’s how gravity works) but the more factors you implement the more it can differ. Here’s an example using only air resistance as a factor (projectile gets slower the longer it goes):

Flight path 45° arc: https://i.imgur.com/hPOYYHI.png
Same path but blocked by a wall: https://i.imgur.com/wPO3D7W.png

You can play around with the code if you want to increase the curve resolution.

local GLOBAL_GRAVITY = 2

local function path(steps, position, velocity, gravity)
	local gravityVector = gravity*Vector3.new(0, -1, 0)
	local d = velocity + gravityVector
	local newVelocity = (velocity+gravityVector)*.8
	if steps == 1 then
		return position + d, newVelocity
	elseif steps == 0 then
		return position, velocity
	end
	return path(steps-1, position, newVelocity, gravity) + d, newVelocity
end

--Starting position for our indicator, and parent of beam attachments
local p = workspace.Part

--Variables
local position = Vector3.new() --Attachments are in part center
local velocity = Vector3.new(0, 1, -1).Unit * 20 --Length of vector is throwing speed in studs/s

local function makeBeam(a1, a2)
	local b = Instance.new("Beam")
	b.Attachment0 = a1
	b.Attachment1 = a2
	b.Color = ColorSequence.new(Color3.new(1, 0, 0))
	b.Transparency = NumberSequence.new(0)
	b.Width0 = 0.2
	b.Width1 = 0.2
	b.FaceCamera = true
	b.Parent = a1
end
local function makeHitIndicator(pos)
	local part = Instance.new("Part")
	part.Name = "Indicator"
	part.Anchored = true
	part.CanCollide = false
	part.Color = Color3.new(1, 0, 0)
	part.Shape = Enum.PartType.Ball
	part.Size = Vector3.new(0.4, 0.4, 0.4)
	part.Position = pos
	part.Parent = p
end

--We will draw the curve until it hits something, or 100 cycles pass
local lastAttachment
for i = 0, 100 do
	local pos, vel = path(i, position, velocity, GLOBAL_GRAVITY)
	local ray = Ray.new(p.Position+pos, vel)
	local raycastResult, hitPos = workspace:FindPartOnRayWithIgnoreList(ray, {p})
	local a = Instance.new("Attachment")
	if raycastResult then
		a.WorldPosition = hitPos - p.Position
		if lastAttachment then
			makeBeam(lastAttachment, a)
		end
		makeHitIndicator(hitPos)
		a.Parent = p
		break
	else
		a.Position = pos
	end
	a.Parent = p
	if lastAttachment then
		makeBeam(lastAttachment, a)
	end
	lastAttachment = a
end
13 Likes
#13

To add on to my first reply, you can then save the calculated points in a table everytime you make a new indicator, and iterate through that table to (with a second-long tween) reposition your projectile every second. Your projectile will then follow the exact flight path you previously calculated.

You need to mess with the server-client boundaries here because indicators should be local but the flight path needs to be server-side.

1 Like
#14

So i actually did something similar with my basketball tool
local Tool = script.Parent
local Handle = Tool:WaitForChild(“Handle”) – Assuming the ball mesh is named Handle
local Player = game.Players.LocalPlayer
local Mouse = Player:GetMouse()

local RunService = game:GetService(“RunService”)
local Workspace = game.Workspace

– Constants
local GRAVITY = Vector3.new(0, -196.2, 0) – Gravity in studs/s²
local TRAJECTORY_RESOLUTION = 50 – Number of points on the curve
local THROW_FORCE = 100 – Initial velocity multiplier

– Variables
local isHolding = false
local trajectoryPoints = {}
local beam = nil
local attachment0 = nil
local attachment1 = nil

– Helper: Create a beam for trajectory visualization
local function setupBeam()
if not beam then
attachment0 = Instance.new(“Attachment”)
attachment1 = Instance.new(“Attachment”)

    attachment0.Parent = Handle
    attachment1.Parent = Workspace.Terrain -- Temporary parent; will be positioned dynamically

    beam = Instance.new("Beam")
    beam.Attachment0 = attachment0
    beam.Attachment1 = attachment1
    beam.Color = ColorSequence.new(Color3.new(1, 1, 0)) -- Yellow
    beam.Width0 = 0.1
    beam.Width1 = 0.1
    beam.CurveSize0 = 0.5
    beam.CurveSize1 = 0.5
    beam.Parent = Handle
end

end

– Predict trajectory and generate curve points
local function calculateTrajectory(startPosition, initialVelocity, resolution)
local points = {}
local timeStep = 0.05

for i = 1, resolution do
    local t = timeStep * i
    local position = startPosition + (initialVelocity * t) + (0.5 * GRAVITY * t * t)
    table.insert(points, position)

    -- Check for collision with ground
    local ray = Ray.new(points[i - 1] or startPosition, (position - (points[i - 1] or startPosition)).Unit * 10)
    local hit, hitPosition = Workspace:FindPartOnRay(ray)
    if hit then
        -- Stop calculation at the point of collision
        for j = #points, resolution do
            table.remove(points, j) -- Remove excess points
        end
        table.insert(points, hitPosition) -- Add the landing point
        break
    end
end

return points

end

– Render trajectory visualization using Bezier approximation
local function renderTrajectory(points)
if #points < 2 then return end

-- Use the first, middle, and last points to approximate a curve
local startPosition = points[1]
local midPosition = points[math.floor(#points / 2)]
local endPosition = points[#points]

-- Update beam attachments
attachment0.WorldPosition = startPosition
attachment1.WorldPosition = endPosition

-- Curve details
beam.CurveSize0 = (midPosition - startPosition).Magnitude * 0.5
beam.CurveSize1 = (endPosition - midPosition).Magnitude * 0.5

end

– Throw the ball
local function throwBall(landingPosition)
local newBall = Handle:Clone()
newBall.Parent = Workspace
newBall.Position = Handle.Position

local velocity = (landingPosition - newBall.Position).Unit * THROW_FORCE
local bodyVelocity = Instance.new("BodyVelocity")
bodyVelocity.Velocity = velocity
bodyVelocity.MaxForce = Vector3.new(1e6, 1e6, 1e6)
bodyVelocity.Parent = newBall

-- Cleanup after 5 seconds
game:GetService("Debris"):AddItem(newBall, 5)

end

– Mouse button down
Mouse.Button1Down:Connect(function()
isHolding = true
setupBeam()

-- Predict trajectory while holding
RunService.RenderStepped:Connect(function()
    if isHolding then
        local startPosition = Handle.Position
        if Mouse.Hit then
            local targetPosition = Mouse.Hit.Position
            local velocity = (targetPosition - startPosition).Unit * THROW_FORCE

            trajectoryPoints = calculateTrajectory(startPosition, velocity, TRAJECTORY_RESOLUTION)
            renderTrajectory(trajectoryPoints)
        end
    end
end)

end)

– Mouse button up
Mouse.Button1Up:Connect(function()
isHolding = false

-- Throw the ball
if #trajectoryPoints > 0 then
    local landingPosition = trajectoryPoints[#trajectoryPoints]
    throwBall(landingPosition)
end

-- Clear trajectory visualization
if beam then
    beam:Destroy()
    beam = nil
end

if attachment0 then attachment0:Destroy() end
if attachment1 then attachment1:Destroy() end

end)

1 Like