At the moment, instead of just setting a part’s LocalTransparencyModifier to -1 in order to see the part in first person (if it’s in the character), we need to continually set the LocalTransparencyModifier on RenderStepped because ROBLOX keeps overwriting our changes to it. It would be super nice if we could just set the LocalTransparencyModifier once and not have to update it 60 times a second to make it work.
1 Like
Just use FE, it would be 10x easier and more efficient.
Allow me to elaborate: Anything you do with a client-side script (LocalScript) will NOT replicate to the server. For example, if yo use the transparency of an object through a LocalScript (say to 0.5), it will only replicate to the client it’s ran on. Any other person would see the original transparency (let’s just say the original transparency was 0). If you set the CFrame of an object through the LocalScript, it will only fire on that client, anyone else would see the original position/angle.
In a script:
local brick = game.Workspace.Part
brick.CFrame = brick.CFrame * CFrame.Angles(0,math.pi/4,0)Everyone sees the brick rotated 45 degrees along the Y axis.
In a LocalScript:
local brick = game.Workspace.Part
brick.CFrame = brick.CFrame * CFrame.Angles(0,math.pi/4,0)Only the client will see the brick rotated 45 degrees along the Y axis.
I am using FilteringEnabled – I don’t make games without it now. However, regular .Transparency can’t control transparency of body parts in first person. Only LocalTransparencyModifier can control that, and it gets overwritten every frame.
Isn’t this something you can change for yourself, using the new StarterPlayer ?
I am using FilteringEnabled – I don’t make games without it now. However, regular .Transparency can’t control transparency of body parts in first person. Only LocalTransparencyModifier can control that, and it gets overwritten every frame.[/quote]
Sorry, terribly misread.
LocalTransparencyModifier isn’t a member of the player – it’s a hidden property of BaseParts. ROBLOX uses it for hiding your body parts in first person, but they keep setting it over and over and over every frame. I don’t see any property in the StarterPlayer that would resolve this.
I have to use this a lot, and it definitely gets annoying having to continuously set the local transparency.
I’m aware that it is a property of a part. But on the test server I saw that all Scipts can be modified already, so perhaps this issue will fix it self ?