Chrythm
(Chrythm)
September 4, 2024, 2:39am
#1
As of about an hour ago, I can no longer see beams or trails in any studio sessions, and not in test mode either. I can still see them in game, though.
CPU: 12th Gen Intel(R) Core™ i9-12900K
Base speed: 3.20 GHz
Sockets: 1
Cores: 16
Logical processors: 24
Virtualization: Enabled
L1 cache: 1.4 MB
L2 cache: 14.0 MB
L3 cache: 30.0 MB
Utilization 4%
Speed 3.17 GHz
Up time 3:03:17:51
Processes 216
Threads 3839
Handles 115835
GPU: NVIDIA GeForce RTX 3060 Ti
Driver version: 32.0.15.5585
Driver date: 5/13/2024
DirectX version: 12 (FL 12.1)
Physical location: PCI bus 1, device 0, function 0
Utilization 65%
Dedicated GPU memory 1.7/8.0 GB
Shared GPU memory 0.2/15.9 GB
GPU Memory 1.9/23.9 GB
28 Likes
I was one of the people to observe this, it completely makes any beam disappear:
Expected Behavior:
[image]
Output Behavior:
[image]
Can confirm this issue on at least 3 other individuals’ ends as well.
2 Likes
baadtiger
(George)
September 4, 2024, 3:37am
#3
Make sure they have two attachments; attachment1 and attachment0.
2 Likes
KumiNeku
(Kumi)
September 4, 2024, 3:43am
#4
Everything related to beams and trails are invisible. I’m having this issue too.
4 Likes
same for me, trails don’t work in studio
2 Likes
Dapale
(Dapale)
September 4, 2024, 4:02am
#6
Can confirm. This bug is only occurring in Studio for me. The Roblox client don’t seem to have this issue (old and new servers).
1 Like
TokensArk
(Token)
September 4, 2024, 4:13am
#7
was about to go crazy, thanks for bringing this up
3 Likes
imNiceBox
(imNiceBox)
September 4, 2024, 8:26am
#8
We experienced the same issue in our game.
The problem was the Roblox engine sometimes incorrectly calculating the distance between attachments, causing Transparency to be close to 1 for the entire beam (NumberRange).
Setting the Transparency to specific number instead of NumberRange fixed the issue.
1 Like
Experiencing this too! I hope this can be resolved quickly.
1 Like
Aeresei
(Aeresei)
September 4, 2024, 9:42am
#10
Can confirm, this is also happening to me which really sucks because I have a system that is highly dependent on trails…
SlussBat
(Seraphim)
September 4, 2024, 9:50am
#11
Can confirm this just started happening to me a few minutes ago.
1 Like
Ru1PT111
(Ru1PT111)
September 4, 2024, 9:54am
#12
Same thing happening in my studio.
Edit: In the Roblox app works just fine.
12345koip
(12345koip)
September 4, 2024, 9:56am
#13
I also can confirm trails and beams do not show up. I am using Roblox Studio version 0.640.16400735 (64-bit) on Windows 11. It happens in any place I create in studio.
loudbytes
(loudbytes)
September 4, 2024, 11:37am
#14
Experiencing the same issue.
Roblox Studio Version 0.640.1.6400735 (arm64)
MacBook Air M2 2022, MacOS Sonoma 14.6.1
1 Like
This has been driving me nuts.
farokeetak
(farokeetak)
September 4, 2024, 12:36pm
#16
It happened to me once, and then it went back to normal. But now it’s happening again
I think there’s nothing we can do about this issue, we have to wait til it back to normal
Did you do anything that might have fixed it before it started working again?
I have met this issue about 10 hours ago. Finally somebody helped report it. It does affect my act work and hope Roblox could fix it ASAP.
steechyy
(steechy)
September 4, 2024, 1:15pm
#19
experiencing same issue w/ rblx studio, hope this is fixed soon !!
This is a very new issue seemingly everyone is experiencing. But don’t worry, it’s only in Roblox studio, so in-game it’s visible.
1 Like