Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SurfaceAppearance.Color might be set to (0,0,0) by default instead of (1,1,1) causing black SurfaceAppearances #942

Closed
beam-roblox opened this issue Jul 19, 2024 · 3 comments
Labels
status: external An external project is the cause of this type: bug Something happens that shouldn't happen

Comments

@beam-roblox
Copy link

beam-roblox commented Jul 19, 2024

The new SurfaceAppearance.Color API will get released soon and we received this bug report yesterday that makes us believe Rojo might be setting the default value of this property at (0,0,0). This would multiply all SurfaceAppearances generated by black rendering them entirely black. The correct default value for SurfaceAppearance.Color is (1,1,1).

@beam-roblox beam-roblox changed the title SurfaceAppearance.Color is set to (0,0,0) by default instead of (1,1,1) causing black SurfaceAppearances [releasing soon] SurfaceAppearance.Color might be set to (0,0,0) by default instead of (1,1,1) causing black SurfaceAppearances Jul 19, 2024
@Dekkonot
Copy link
Member

Howdy. This is an underlying problem with our reflection database being out of date. I've left a response to the report here that should hopefully provide a bit more info.

This isn't really actionable on our end right now because it requires us to make a new release, which is easier said than done. I'm going to leave this open until I talk with my fellow maintainers about what our plans are and I'll update it here.

@Dekkonot Dekkonot added type: bug Something happens that shouldn't happen status: external An external project is the cause of this labels Jul 19, 2024
@Dekkonot
Copy link
Member

Howdy. Quick update on this one. We're moving forward with publishing Rojo v7.4.2 soon (should be later today) so this issue should be resolved after that. Going to close this issue.

@beam-roblox
Copy link
Author

Thank you so much Dekkonot! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: external An external project is the cause of this type: bug Something happens that shouldn't happen
Projects
None yet
Development

No branches or pull requests

2 participants