
disable backgrounding occluded windows in chrome 99+ reg file and run it: Windows Registry Editor Version 5.00 you can set it to false manually if you know how, but if you don't, just copy the below codeblock into a Notepad, save it as a. "C:\Program Files\Google\Chrome\Application\chrome.exe" -profile-directory="granblue" -disable-features=CalculateNativeWinOcclusionĪs such, when 99 hits standard Chrome the only way to disable occlusion will be via this group policy. The workarounds are to either always launch Granblue first or setup a second profile for Granblue, which you can do by setting the shortcut to use a different profile Below is an example launch line where the launch order of Chrome won't matter, since we tell it to use a profile called granblue: If you launch Chrome normally (say through start menu) then the Granblue shortcut second on the same profile it will ignore the launch line

If you use Chrome for Granblue and regular browsing at the same time, and only use one profile, you must launch the Granblue shortcut with this flag first. In chrome 99+ (which is the Beta branch at time of writing) chrome will remove the flags currently needed to disable occlusion so you can play full auto and alt-tab:Įdit - you can follow this method instead of registry too, but there are some issues (especially if you only have 1 Chrome profile and also use chrome as your main browser):
