Looks like I’m not alone!
https://twitter.com/DarthBlox/status/794372845916680192
Also, a new interesting gif. I haven’t seen this behavior before. The sides of the window are somehow impacting how the neon renders.
2 Likes
Any updates on this?
2 Likes
Still unclear what to do with this - we can only investigate this if it happens to somebody in the office basically, and we haven’t had anybody with that issue. I’m not sure OTOH how many of us are running Sierra, I know I am and haven’t ever seen this 
1 Like
Is there anything I can do to help you guys find it? I’m finding myself not using neon in newer builds because I don’t know what it’s going to actually look like.
2 Likes
I’m not really sure. I’m trying to see if anybody at HQ can reproduce this but so far it does not seem like it.
So if you add a “really black” neon part, it doesn’t immediately become white, right? that is, it starts as black and quickly fades to pure white? What happens if you resize the window after it does - does the process of fading restart or does it stay pure white?
1 Like
It’s only really black for a split second, before turning greyer and greyer until it’s eventually pure white with ghosting issues. This whole process happens in under a second. I’ll try to get a video later if you need it.
Resizing the window does nothing, HOWEVER, simply clicking the top of the roblox studio window (where the minimize, fullscreen, etc buttons are) will change the part back to Really Black once I release the click. This too only lasts for a split second though, before turning greyer to white.
2 Likes
Hmm, ok. I have a hunch.
If you have a Neon part and add Blur effect with the max blur size, does the outline of the part become clearly visible despite the blur?
1 Like
Alright, cool. I now know what is happening, if not why. I have a few ideas for fixing this. I’ll try to get some Mac-specific fix together that may or may not help; if it doesn’t there’s a way to fix it in the color correction pipeline but this is kinda unfortunate because we’d need to special case something.
Of course the fun part is that since I can’t repro, we’ll have to iterate by me shipping fixes and you checking them… Oh well.
1 Like
Just want to note here that we got a repro for the Neon issue in house thanks to @spotco. We’ll investigate and figure out how to fix it.
edit: damn it, the repro disappeared when the laptop with the repro got upgraded from OSX 10.10. Oh well. We’ll use the backup plan of shipping fixes that may or may not help and slowly iterating towards something that works, I guess
Since the issue is Studio-only it’s also possible that the coming-soon Qt5 upgrade will fix this.
3 Likes
I’m back zeuxcg, noticing different behavior. Neon brakelights are remembering what the studio website page was previously on. Panning around looks like this. The neon is at half transparency so it’s not blown out on my screen.
9 Likes
You thought I was done @zeuxcg?!? THINK AGAIN!
Except this time around I’ve got some good news,
Neon is almost working again!
One very important thing to note. I checked my Studio files and found Studio hadn’t been updated since January 20th 2017. I was never prompted. What made me check my version was when I realized I still had the old brick and plank textures. I deleted studio and reinstalled. Since then is when I’ve been getting better luck with Neon.
Anyways, I can still see the roblox website in all neon bricks like the gif I posted above. What has changed though is that sometimes opening a script will completely fix the problem. Strangely enough, it sometimes doesn’t fix the problem, but instead will turn my neon bricks black.
So I’ve spent today trying to narrow down why this happens only part of the time. How can I get around this neon bug until it’s 100% gone.
- My script-opening fix works 100% of the time if I can open a file before the Start Page loads in. Neon bricks will be blown out with white until I open the script. Once I close the script, neon is normal!
- Closing the file (revealing a loaded Start Page) and then opening a new file breaks my solution above 100% of the time. I get the black bricks like seen above.
- Closing the Start Page tab doesn’t fix the problem, even if I do that before opening a script.
- If I open a new file while already in one, which opens a new studio window, my solution works again. It’s almost like the Start Page is somehow tied to neon not being fixed with my hacky solution.
This is what I’ve found. If you have any questions please let me know! I’ve never been so excited to see neon, it’s as if the feature was just announced. I can finally build with it again!
Thank you for being so involved with this issue!
3 Likes
Uh oh, this is a persistent issue. I checked in some changes earlier this year but apparently they changed nothing; we also upgraded to Qt 5 but apparently that also didn’t fix the issue (but may be the reason why you now see different behavior).
Without being able to debug this I feel like the only step we can take now is to change the post effect pipeline to kill output alpha so that it’s impossible for the window to get transparency. Unfortunately we have to keep the alpha for thumbnails to work so this means forking some code a bit…
1 Like
Ah, hmm, there’s one more thing I can try (which will ship in 1.5 weeks). If that doesn’t help either, we’ll use the nuclear option.
1 Like
Thanks for following up!
Bad news I’m afraid! The issue is still present.
Here’s the version I’m currently running.
Something NEW I’ve found, but it’s like not that new. Just a new discovery.
Resizing the properties window, causing the game window to resize, fixes neon. No more opening scripts!!
It even works when I’ve got the start page open!
1 Like
Alright, I think I implemented a change that will actually fix this problem 
Will update when it’s live which should be in a week or two.
3 Likes
The fix is live now (make sure Studio version is 287)
2 Likes
YOU DID IT! IT LOOKS GREAT!
I feel like I owe you 1,000 coffees.
Thanks for being so persistent in fixing this. Even as many months went by, you were still committed to fixing this. I seriously appreciate that!
6 Likes