The name of the executable will be set to 'CEF Ingame Browser' so that users can identify the audio source in their volume mixer, as seen below. That means it has its own, separate volume control and cannot be used to produce 3D audio. Instead, it is played on the separate browser process. It is not required, but can be used to test / debug the CEF Server away from your game.Īudio playback that occurs in the browser (for example, when playing a YouTube video) is not played in game / in engine. The test client project is also bundled in the solution. If you are looking for x86 support, this project is not for you.

The legacy / stable scripting engine will not work, as it does not support named pipes. NET 4.x scripting compatibility is required, you will need to enable the 'Expirimental' scripting engine for your unity project. Mono support is possible in the underlying libraries and APIs, so Linux and Mac support is possible with some additional work. RequirementsĬurrently only targets Windows. Unlike the Chromium project itself, which focuses mainly on Google Chrome application development, CEF focuses on facilitating embedded browser use cases in third-party applications. NET library for integration in Unity or other applications, which communicates with the server via named pipe.Ī test client is also available (see below). The project consists of two parts: First, the server, which manages a CEF (Chrome Embedded Framework) browser instance. Bi-directional messaging between your C# code and in-browser JavaScript code.Input support for key combinations, dragging, selecting and scrolling.Pass mouse and keyboard events from game to browser.Fast data exchange via named pipes, making high FPS possible.Use all the modern web features in Chromium.🚧 This is a work in progress, do not use this 🚧 Features 🚧 This is a work in progress, do not use this 🚧 Proxy server for an embedded Chromium browser in your Unity games.

Github chromium