VS Code 1.57 breaks Vibrancy (Do not update to 1.57) #108
Comments
is Vibrancy working for 1.56.2 ? |
Yes it works just fine, I downgraded to 1.56.2 and blocked updates for now @denewito Edit: I think it might have something to do with the security features they added with 1.57 but I’m not sure. When I first opened it after the upgrade even the theme was set to default until I trusted my workspace’s parent folder |
Yeah can confirm, it broke for me too in VS Code 1.57 |
Doesn't work in 1.56.2 for me. :( |
After getting the update vs code vibrancy gonna stop. My heart is break for that case .What can I do for this case |
yes, I have installed it, and it was working before I make the upgrade of vs code to the 1.57 |
after getting the upgrade it's not working.. |
fix it please fast |
Color theme changes but no transparency is applied |
Can you please explain how can i prevent vscode from autoupdate? Where can i find the preferences json file? |
I made it already but this theme need to fix this bug it's important and
the terminal is not also getting transparent glass effect
…On Mon, Jun 14, 2021, 10:34 PM Branislav Zivanovic ***@***.***> wrote:
@denewito <https://github.com/denewito> Try to reinstall Vibrancy, are
you using something like Customize UI too?
@sohancms <https://github.com/sohancms> Well you can downgrade, download
1.56.2 from here <https://code.visualstudio.com/updates/v1_56> and before
starting the installer save this to your preferences json file:
"update.mode": "none"
Can you please explain how can i prevent vscode from autoupdate? Where can
i find the preferences json file?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#108 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQAKA5INL7VUKEGRY3CT5HTTSYZDJANCNFSM46RPVMXQ>
.
|
Open the Command Palette (check more here) then search settings json and it should show up. Open it, add that line inside the brackets then save it. After you have done that you can downgrade and it won’t auto update. @BranislavZivanovic |
Facing the same issue (no transparency) with 1.57. Apart from the new safety features, VSCode also made some UI changes, like https://code.visualstudio.com/updates/v1_57#_updated-quick-pick-suggest-widget-colors |
I got same problem. Just downgraded to this:
and works fine right now. Also I'm getting
for while. Any updates? |
@kaganergovan |
Hi, I have fixed this problem in vscode-vibrancy 1.0.16-rc1. I will publish the version in the vscode extension marketplace when the test is complete. |
Perfect! Thank you! Edit: I installed 1.0.16-rc1 and it works on 1.57, there’s occasional flickering (it goes back to solid color and back to acrylic) but they are short. |
Hi, I have fixed this problem and make sure you have upgraded this extension to v1.0.16. If the problem is not resolved, please update this issue. |
Thank you dear
…On Tue, 15 Jun 2021, 8:12 pm EYHN, ***@***.***> wrote:
Hi, I have fixed this problem and make sure you have upgraded this
extension to v1.0.16.
If the problem is not resolved, please update this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#108 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARMUIX7KZIVT6775TBONZW3TS5NVLANCNFSM46RPVMXQ>
.
|
lor1x v1.0.16 extension is working. But it’s flickering very few time. However thanks a lot dear EYHAN and lor1x |
@sohancms The current solution does have flickering problems and I am looking for a better solution. |
when I do full-screen mode (F11) vibrancy won't work there too. and flickering lot |
Hi,
After updating to 1.57 yesterday Vibrancy stopped working, not entirely. When VS Code is starting up I can see it being rendered then overwritten once everything loads. The acrylic effect lasts only for the load time then it is solid color of the theme I’m using.
I tried this on macOS Big Sur 11.4 and Windows 10 21H1, even on clean installs of VS Code (with just Vibrancy on it), same thing. I have downgraded to 1.56.2 for now and blocked updates.
Anyone else having this issue as well?
The text was updated successfully, but these errors were encountered: