Update CEF to newer version

[getnamo]

At the time of opening this issue it appears latest stable is 112ish see https://bitbucket.org/chromiumembedded/cef/wiki/BranchesAndBuilding

Main repo for updating: https://github.com/getnamo/BluBrowser

Related older issues - #29, #60, #64, #72

[getnamo]

https://github.com/getnamo/BLUI-Unreal/releases/tag/v4.6.0 updates it to 90.0.4430.212 to sync version with the one in the engine.

use https://github.com/getnamo/BLUI-Unreal/releases/download/v4.6.0/BluBrowserCEF-90.0.4430.212-Win64.7z for just the blu_process and updated cef (no plugin)

[mangoplane]

https://github.com/getnamo/BLUI-Unreal/releases/tag/v4.6.0 updates it to 90.0.3340.212 to sync version with the one in the engine.

use https://github.com/getnamo/BLUI-Unreal/releases/download/v4.6.0/BluBrowserCEF-90.0.4430.212-Win64.7z for just the blu_process and updated cef (no plugin)

Does that mean the browser built into Unreal Engine is running CEF? In that case, what are the benefits to using this custom version of Chrome?

Kind regards.

[getnamo]

Not quite, it means whichever one runs first will load into memory for header include links, but the separate browser process is still run by blu_process.exe and you still have full control over the instance which you do not have with the built in plugin. That's said if the built in web browser plugin API satisfies your use case, I would recommend using it.

At some point in the future namespacing the headers should allow decoupled CEF versions without causing incompatibility.

[mangoplane]

Not quite, it means whichever one runs first will load into memory for header include links, but the separate browser process is still run by blu_process.exe and you still have full control over the instance which you do not have with the built in plugin. That's said if the built in web browser plugin API satisfies your use case, I would recommend using it.

At some point in the future namespacing the headers should allow decoupled CEF versions without causing incompatibility.

Interesting, thanks for the education. It's great to know they support CEF. I think I'll experiment with the native WebBrowser in Unreal, to see if I can replicate the above error I mentioned in the other issue. I believe it may be specific to this plugin, and if I identify the cause I will be sure to PR a fix or raise it as an issue.

Decoupling the CEF versions would be an amazing step forward, allowing us to update the versions independently to the latest and greatest Chromium regardless of the native browser.

Thanks.

[getnamo]

Sorry just realized I misread your earlier question. Yes the web browser plugin uses CEF underneath. This is then used in e.g. the popular Bridge plugin for e.g. browsing assets but can be used as a web browser view.

Difference between BLUI and web browser plugin at this point is smaller than it's been in the past and I generally recommend people to use the built in version if it suits their use case.

Some differences:

• BLUI renders 60fps, web browser plugin at 24 fps, need c++ access to change this for built in, but in theory supported.
• Developers have control over cef version used (can e.g. compile one in with custom codecs)
• More configurations are exposed in BLUI, especially in the context of inputs and e.g. handling downloads/etc.
• The way Js web page communication is handled is different.