menu
 

在 Audiokinetic 社区问答论坛上,用户可对 Wwise 和 Strata 相关问题进行提问和解答。如需从 Audiokinetic 技术支持团队获取答复,请务必使用技术支持申请单页面。

0 投票

Connecting the Wwise Profiler to a web application using Wwise

Connecting the Wwise Profiler requires running a proxy server in the background. This proxy server acts as a message broker; the Wwise runtime automatically connects to the proxy via WebSocket on startup, and the Wwise Profiler connects to the same proxy via TCP.

To run the proxy server, you will require node.js version 14 or later.

  1. Open a command-line interface, and navigate to the SDK\samples\SoundEngine\Emscripten\WwiseProfilerServer directory.
  2. Install dependencies by running the command npm install.
  3. Start the server by running the command node WwiseProfilerServer.js

This will bind local port 8095 to a WebSocket server. By default, the Wwise runtime connects to ws://localhost:8095/. This can be changed in AkCommSettings::szCommProxyServerUrl on the game side.

Once the server is up, start the web application integrating Wwise. Use your browser's devtools panel to make sure there are no connection errors in the web page's console log when the application starts. If there are no errors, you should see an active WebSocket connection in the devtools' Network tab, and Wwise Authoring should be able to detect the game instance on the local network, just as it would for a more typical desktop application.

Hi everyone,

I'm trying to connect IntegrationDemo WebGL (2024.1.1.8691 SDK/Emscripten_mt/Profile Version) to wwise profiler.

I ran the WwiseProfilerServer,and ran a local server to run IntegrationDemo in chrome.

IntegrationDemo html page worked well,WwiseProfilerServer console also printed ports correctly.

But wwise profiler remote can not see any instance of IntegrationDemo WebGL.

How to fix it?Thanks!

分类:General Discussion | 用户: Shuo L. (100 分)

Please sign-in or register to answer this question.

...