Only thing is, as far as I have seen, we have no control on the graphics setting threshold for neon parts (I think it’s currently level 7 or 8?) which kind of makes me not want to use them at all. If my place is causing lag from too many neon parts then that should really be my issue to address and not pre-emptively solved by ROBLOX. It’d probably be more reliable to make an image that looks neon.
You could optimize the code to reuse neon where possible. For example, buttons could share one neon for mouse over effects. I also wonder if it’s worth taking screenshots of the effects and making them work graphically where possible.
If you guys want nice looking guis you can upload images. Create your own 9-slice frames if you’re hardcore. Neon parts certainly is not what you want to be using for a drop shadow / background.
If you guys want nice looking guis you can upload images. Create your own 9-slice frames if you’re hardcore. Neon parts certainly is not what you want to be using for a drop shadow / background. [/quote]
The use cases are limited but they certainly exist.
Is it practical as a drop shadow? No.
Is it practical as a background? Depends on the application.
At best, you get a translucent gui that applies a pleasant blur to whatever’s behind it. At worst, you get a translucent gui with no blur.
I definitely agree that the fact it exists in 3D would preclude much use in cases where the possibility exists of part surfaces intersecting with the viewport. That doesn’t matter so much in situations where the camera is fixed and not user-controllable.