beam vfx problem

[eager crystal]

so i have this beam vfx and i am trying to figure out how to enable the beam the vfx does emit but parenting the beam workspace doesnt seem to make it enabled anybody knows the fix

local ceroEvent = game.ReplicatedStorage.ceroEvent
local beam1 = game.ReplicatedStorage.beam1
local beam2 = game.ReplicatedStorage:WaitForChild("beam2")

ceroEvent.OnClientEvent:Connect(function(plr)
    task.wait(2)
    
    local beam1Clone = beam1:Clone()
    local beam2Clone = beam2:Clone()
    beam1Clone.Parent = workspace
    beam2Clone.Parent = workspace
    beam1Clone.CFrame = plr.Character.HumanoidRootPart.CFrame * CFrame.new(0,0,-30)
    beam2Clone.CFrame = 

plr.Character.HumanoidRootPart.CFrame * CFrame.new(0,0,-5)

    
    for _, particle in beam1Clone:GetDescendants() do
        if particle:IsA("ParticleEmitter") then
            local emitCount = particle:GetAttribute("EmitCount")
            particle:Emit(emitCount)
        end
    end
    
    for _, particle in beam2Clone:GetDescendants() do
        if particle:IsA("ParticleEmitter") then
            local emitCount = particle:GetAttribute("EmitCount")
            particle:Emit(emitCount)
        end
    end

end)

[gloomy kayak]

What are the beam's attachments

[eager crystal]

the beams attachments are identified in the property itself (I didnt do the beam so idrk how they work)

[eager crystal]

what are u trying to hint at?

[gloomy kayak]

I'm hinting at the fact I don't think the attachments on the Beam are present so it cant find them.

With no attachments, the beam can't render

just because the properties aren't empty doesn't mean the attachments exist

[eager crystal]

i mean i am cloning the parts aka beam1 and beam2 which are parents of the attachements so shouldnt the attachements also clone?

[gloomy kayak]

Oh the beams are in the attachments?

[eager crystal]

wait wdym are u saying every beam should be a child of its attachement?

[gloomy kayak]

Sorry maybe I misread. Are the attachments under the beams?

[eager crystal]

all beams are parented to one attachement

[gloomy kayak]

Okay what is the beam's other attachment?

[eager crystal]

like attachement1?

[gloomy kayak]

Beams need two, so I'm assuming one of them is their parent, whats the other one

[eager crystal]

thats for beamnew6

[eager crystal]

both are attached to SE

[eager crystal]

different beams such as beam 7 are attached to different attachements tho

[gloomy kayak]

Both the same attachment? I don't think that'd work, as there's no distance to render over

[eager crystal]

i mean idk i wasnt the vfx artist who did it but it looks fine in the workspace?

[gloomy kayak]

Shouldn't you be chatting with the VFX artist then?

[eager crystal]

he is asleep rn so gonna have to wait till tmrw

i am clueless about how beams really work

[eager crystal]

ohhhhh I get it now

so there is two different se's

one in the first part and the second se attachement is in the second part

they both had the same name thats why i was confused

[gloomy kayak]

What are the attachments parented to

[eager crystal]

a part?

[gloomy kayak]

Are you supposed to be cloning the beams themselves and not those two parts?

[eager crystal]

isnt roblox gonna also clone the beam since it is a grandchild of the part?

[gloomy kayak]

I think you need to be patient and ask your VFX artist. You may not be cloning the effect correctly

[gloomy kayak]

Whatever you clone will also clone all descendants

[eager crystal]

yeah so i am technically cloning the beams too?

[eager crystal]

we tried working it out but he had to go to sleep and he didnt seem to know the issue

[gloomy kayak]

You should be cloning one thing so everything beneath that will clone automatically

[eager crystal]

thats what I am doing?

[gloomy kayak]

So why are you cloning the beams and putting them in the workspace all on their own

[eager crystal]

i am cloning the part not the beams

[eager crystal]

by beam1 and beam2 it is the part

[eager crystal]

these two parts

if anybody knows a solution ping me pls

[eager crystal]

i am like 95% sure it isnt a problem with the vfx

i tried looking for fixes online but there was nothing to find

[gloomy kayak]

What happens if you copy and paste from ReplicatedStorage? Like if you use the server view and copied and pasted it there

in studio not in a script

[eager crystal]

wdym the vfx goes invisible cuz we putting it in rs?

oh u mean if it is in workspace?

it is fully rendered and working fine

[gloomy kayak]

While the game is running and you're on server view?

[eager crystal]

ye?

[gloomy kayak]

Maybe on the script try manually setting one of the beam's attachments to see if anything appears.

[eager crystal]

alr

[eager crystal]

sadly nothing happens 😔

[gloomy kayak]

You need to check the object when it gets spawned in the explorer. Like look to make sure everything is where it should be

[eager crystal]

NVM

[eager crystal]

THIS WORKS

THANK U SO MUCH

OMG

FINALLY

🙏🏽

tysm

[gloomy kayak]

There's probably a more technical answer to why that worked, unfortunately I can't be bothered to work it out