Yup. Future (sort of) fixes the problem but a major downside is that it messes up my entire lighting setup.
I’m using SurfaceLights.
Also yeah? I know that. Problem is that studio doesn’t render the light below a certain height / distance from the camera (for me), and I want to fix that.
no i mean like what is cutting off? the image you showed doesnt look like stuff is getting cut off, i also meant not to change the material of the lights, but the literal material that your player looks through
What @F0xBirdmansBFF means is there some type of transparent Part between the camera and the lights/wall? I think F0x believes that the dark section is a floor. You didn’t really state enough details, assuming we know what is being shown in the picture ‘speaks for itself’ but we don’t know what is what in your picture.
I’m assuming (from the info you’ve given later) that the Neon lights are farther down the wall than the dark line, so they show up past that line.
Hiave you messed with the Value of your Lighting.Brightness to see if that is affecting it? The issue may be that if you’ve got your Brightness at 0 then objects at a distance may render darker automatically. This may happen at certain distances from the camera, especially if the engine is overloaded by other rendering/lag issues.
Why is the SurfaceLight in an Attachment and not in the Part itself?
yeah the reason i keep saying this is because the glass material messes with lights and stuff
to me the darker section just looks like another part of the wall but we cant really tell due the the picture and how there is literally no details and OP expects us to understand the picture
When you put any light object into an attachment, the attachment acts as a part. Basically, if you move the attachment, the light does too. I’ve noticed this bug before, fyi (and that was using lights parented to parts).
I did and still nothing. This all may be just a driver / GPU / Rendering engine issue.
@F0xBirdmansBFF I’m in the core chamber so there’s nothing possibly blocking the light.
For me it isn’t. The attachment acts like a normal part, and the glitch still works even if I use a normal part.
I’ll try joining the game in Roblox Player to see if anything changes since I’ve been testing this only in studio.
Okay everyone. I’ve thought of a genius idea / workaround. I’m gonna turn this bug into a “feature” (classic game developer move). Basically, I’m gonna add a fog tat covers up the part where the glitch occurs.
