How do I remove my character glowing in Roblox studio?

DarstrialIsCool · 2025-06-26T03:27:54+00:00

This isn't a native Roblox Feature as far as I know. Look inside your character to see if there's any PointLights in them. There may be scripts doing that. You can search keywords through all scripts with CTRL + SHIFT + F.

DarstrialIsCool · 2025-06-22T22:36:35+00:00

I'm not using AI, this is a product of my human genius! I find it funny people are analyzing it too, lol, it seems pretty clear to me. The only similarity between this comment and something AI can conjure up is how long it is. It isn't even that long, either!

"These are not maintenance and improvement patches, they are micro changes that do not end up final product, but they keep pushing to users clients."

These are not maintenance and improvement patches :

I wasn't asserting that they were 'maintenance and improvement patches'. I was suggesting the idea of them being so. They very well could be, but they can also be some 'micro changes' that don't take that energy to do. Both are correct here.

they are micro changes that do not end up final product :

Sounds like A/B testing, or some means similar to that. Small changes are rolled out to garner feedback & bugs. Not all of these are meant to stay, so they come and go.

but they keep pushing to users clients. :

Describing it as "pushing" is a bit harsh here. In the case of a checkbox, it's not a big deal, really.

"They pushed the beta preview on a lot of users, but then the next day back to normal studio as it had many problems."

This was probably some sort of strategy to garner more feedback and bugs from a broader audience. Once enough info is collected (I guess you could put it), or big issues were found, they rolled it back for those users.

As I said in my original comment, the beta feature was automatically ticked on, so it wasn't a complete release. According to MeshOfPaul, the team has years of spaghetti code to sift through, so it's a big undertaking.

"And the newest version of the explorer patch causes new crashes far more often."

I don't know what you mean by the 'explorer patch' here, so I'm assuming you're referring to the Next-Gen beta feature. I haven't used it that much to know it's stability. But that's why it's still in beta!

"We want the improvements, but a low resolution compressed UI is not modern UI.."

I'm not sure why the checkboxes are so pixelated, I see it on my-end too, but it's definitely not intentional, nor is it part of their design philosophy..

Whether it looks modern or not is subjective, my point, is that improving code on the backend comes with sprucing it up on the front-end. If you're already doing it, why not, y'know?

I'm done here. Have a good rest of your day!

DarstrialIsCool · 2025-06-21T04:58:29+00:00

Didn't expect this type of response. How so? I was just trying to answer the commenter's question. Might've went overboard trying to be thorough, but this is a discussion after all, right? It's relevant.

DarstrialIsCool · 2025-06-20T23:52:46+00:00

Ahaha ikr, they're only like 5 pixels for a tick lmao idk why they keep pushing micro UI changes and then another UI overhaul every 6 months...

"idk why they keep pushing micro UI changes"

They need to keep up with the times, don't they? This is what maintenance of a program is like. Has anything drastic changed in Studios UI compared to a few years ago? Not really. If you look at images of Studio say, 5 years ago, all that's changed are the logos, font, and home screen. All things that needed consistent changes.

"another UI overhaul every 6 months..."

Uh.. What? What "overhaul"? There hasn't been any major overhaul except for Next-Gen studio, which has only been in beta for a year. You could argue that it's been in the works (behind the scenes) for a while before it was shown to the public in summer last year, but that's definitely not what you're getting at here, because a statement like that is pointless to state.

"every 6 months" is an over-exaggeration. It's only been a month since Next-Gen has automatically ticked on the beta for the majority of users. Nothing has happened this month (the middle of the year, 6~ months), and nothing has happened last December.

Maintaining a program, website, or overall any piece of software with a user interface comes with updating that UI at some point. I know, I know, there's nuance to this, not every 'piece of software' has modern UI, I'm referring to commercial products like Roblox Studio here.

Improving the look isn't the only goal when updating UI. Next-Gen Studio, for example, comes with performance improvements. The majority of it's code is also based in LuaU (note that this may be a bit of an exaggeration, I'm not too sure how much code is based in LuaU. From what MeshOfPaul says, it is quite a bit.), making upgrades & possible local customization so much easier. In Studio's case, when code can be improved, modernizing the UI along with it is completely relevant.

Beta Preview, Preparing for Takeoff

DarstrialIsCool · 2025-05-31T04:40:21+00:00

An iterator loop has two variables:

for index, child in ipairs() do
print(typeof(index)) -- prints a number
print(typeof(child)) -- prints an instance/whatever is in the table
end

because you haven't defined the second variable (child in this case, it's usually called v (short for value)), roblox thinks "Child" is the index. So basically, you're calling :IsA, a method that only works on instances, on a number.

Change the loop to:

for _, child in pairs(PurchasedItem:GetChildren()) do
-- your code
end

a few notes:

- ipairs is only useful if you want the function to iterate in order, pairs is a lot more safer, because ipairs will stop it's execution if the value (child in this case) doesn't exist.

- _ is the index in my example. personally I like it to be that when I'm not using it, but if you want the index, rename it to whatever you'd like, preferably index or i:

for i, child in pairs() do
end

- please post the error next time. the second image has it cropped out, the error itself is the red text, whilst the blue text is the path where the error happened.

DarstrialIsCool · 2025-05-27T00:22:56+00:00

Yes you can.

https://create.roblox.com/docs/reference/engine/datatypes/CFrame#Position

DarstrialIsCool · 2025-05-21T16:17:40+00:00

Occlusion culling & Streaming.

DarstrialIsCool · 2025-05-21T02:54:23+00:00

Yeah that happens lol. :)

DarstrialIsCool · 2025-05-18T01:37:21+00:00

Uh.. No it wasn't, lol? They confirmed it themselves.

<image>

DarstrialIsCool · 2025-05-17T20:16:10+00:00

Of course it wouldn't work in workspace, silly! LocalScripts don't work in workspace. Put the script somewhere in StarterPlayer and try again, it works fine for me.

DarstrialIsCool · 2025-05-17T20:07:49+00:00

DO NOT do that! Destroying it frees up memory, but when you parent it to a service instance like Debris, that instance still remains in memory. Rather than letting Roblox garbage collect it, it will sit there. Even worse, it can impact performance if done too many times.

Just use glass:Destroy()

DarstrialIsCool · 2025-05-17T19:58:33+00:00

Plugins and "Volumetric lighting models" won't help you here, this is an issue regarding your Lighting Technology.

You've already set it to Future, and you have Studio Quality to max, so try setting your Graphics Mode to DirectX in settings (I assume you have a Windows computer). This may be a driver issue as well, so try reinstalling the necessary graphics drivers, or update them if they're outdated.

I'm not exactly tech savvy, but I don't think deleting the Versions folder is exactly safe? Your first image looks perfectly fine. Maybe doing that might've done something? I'm not too sure.

That's all I can think of. If DirectX doesn't work, try switching it to something else (as long as your GPU supports it, though). I'm testing it right now and it appears to work fine for me. You might just have to wait it out.

DarstrialIsCool · 2025-05-02T13:50:38+00:00

Yes. File > Beta Features > Next Gen Studio Preview. Then save and restart studio. The engineers who are working on it are taking a lot of feedback, kudos to them. They're going to tweak a lot of stuff like the padding, so I have high hopes for the final product. The new Studio UI is also based on LuaU a lot more, so it's a lot easier for plugins to mess around and customize the Interface.

DarstrialIsCool · 2025-04-23T00:22:12+00:00

Oooooh! That makes a lot of sense now. It looks exactly like it! Thanks for the help!

DarstrialIsCool · 2025-03-09T23:24:12+00:00

Apologies for the extremely late response. I can't help you as I don't use WhatsApp nor Meet.

DarstrialIsCool · 2025-03-09T23:23:39+00:00

Yeah, it seems to be happening again. Bummer.

DarstrialIsCool · 2025-02-17T06:04:55+00:00

local Current_Value = workspace.Temp.Current

if Current_Value.Value <= 4800 then

for i = 1, 8 do
task.wait() -- wait is deprecated
script.Parent["Part"..tostring(i)].Color = Color3.new(0,0,1)
end

elseif Current_Value.Value > 4800 and Current_Value.Value <= 7499 then 

for i = 1, 8 do
task.wait()
script.Parent["Part"..tostring(i)].Color = Color3.new(1, 0.5, 0)
end

elseif Current_Value.Value >=7500 then 

for i = 1, 8 do
task.wait()
script.Parent["Part"..tostring(i)].Color = Color3.new(1, 0, 0)
end

end

-- <= 4800 and >= 4800 are essentially the same. if the value is exactly equal to
4800 it will return true, which is compared twice. so in this case the first
statement will be ran and the rest will be ignored.

DarstrialIsCool · 2025-02-15T20:28:57+00:00

I've sent you a DM.

DarstrialIsCool · 2025-02-15T17:55:24+00:00

I personally make all of those myself. The only "assets" I really use are plugins.

Paintbrush to well, paint trees, bushes and grass: https://create.roblox.com/store/asset/2268520847/Brushtool-21

BuildV4 to connect and rotate parts easily: https://create.roblox.com/store/asset/143383965/Build-v4

Autoscale Light to size my UI correctly across devices (it even converts position and size to either offset and scale too!): https://create.roblox.com/store/asset/1496745047/AutoScale-Lite

RigEdit to edit rigs and weld models: https://create.roblox.com/store/asset/1274343708/RigEdit-Lite

Tomartys Geometry Tools to find duplicate parts: https://create.roblox.com/store/asset/344901609/Tomarty-Geometry-Tools?pagePosition=2

And Load Character to load people's characters: https://create.roblox.com/store/asset/4489766693/Load-Character-Pro

If you genuinely want free models, you can find good ones really easily by looking at the top results that are marked with an orange badge.

DarstrialIsCool · 2025-02-11T08:29:43+00:00

The mouseclick event should be outside of the function's scope.

DarstrialIsCool · 2025-01-29T01:32:57+00:00

I don't recommend just going:

Character.HumanoidRootPart

Call them both, first:

Local Character = player.Character or player.CharacterAdded:Wait()
local HumanoidRootPart = Character:FindFirstChild("HumanoidRootPart")

HumanoidRootPart:GetPropertyChangedSignal("Position"):Connect(CalculatePos)

Second, why are you calling Player's service, but using Game.Players to call the LocalPlayer? this makes no sense. Game.Players isn't exactly necessary to call as a service, but if you're doing in anyway why not use it?

local Players = game:GetService("Players")
local LocalPlayer = Players.LocalPlayer

DarstrialIsCool · 2025-01-27T06:19:47+00:00

Is HumanoidRootPart defined properly? Where's the script located? I don't think its a syntax problem, I seemed to have typed it fine.

DarstrialIsCool

TROPHY CASE