| Description |
General configuration for test projects | Displays frame rate and latency information, virtual buttons, debug panel, and other tools. Provided to help developers conveniently test the cloud application. |
General configuration for mouse control applications | The Tencent Cloud logo and toolbar are hidden. Keyboard and mouse events are sent to the cloud application, and left/right virtual joysticks are enabled for users on mobile devices. This is suitable for applications that only natively support keyboard and mouse controls. For users on mobile devices, a virtual joystick mapped to the WASD and Space keys needs to be displayed to allow the user to move around and jump. |
General configuration for multi-touch applications | The Tencent Cloud logo and toolbar are hidden. Touch events are sent to the cloud application, and mobile devices do not use the CAR virtual joystick plugin. Note: This is only suitable for applications that natively support touch controls. The application must be capable of managing touch window messages in Windows, and it has been locally tested with a physical Windows touch screen device to ensure successful operation. It is NOT advisable to rely on mouse-to-touch conversion within UE or Unity engines for testing touch message handling, as touch behavior on touch screen devices may behave unpredictably. If the application only natively supports mouse and keyboard commands, this configuration will not work for implementing touch controls. You can integrate the SDK and use the onTouchEvent callback to obtain the corresponding touch point coordinates and send keyboard/mouse commands as touch commands. |
| Description |
Loading page logo | You can use a custom logo by entering the URL for the logo image, (for example, https://qcloudimg.tencent-cloud.cn/raw/5e1434b0dd32f26d9f064853aef02a33.png). The recommended logo dimensions are 90px (height) x 360px (width). |
Toolbar displayed on the main page | Mobile tools include frame rate and latency information, full screen switch (only supports Android; iOS does not support full screen due to system limitations), rotate, mic switch, virtual joystick switch, virtual keyboard switch, debug panel, application restart, and application close. PC tools include frame rate and latency information, full screen switch, debug panel, application restart, and application close. |
Application built-in control modes | Keyboard + mouse: Select if the application natively accepts keyboard and mouse commands to control the application. This typically requires the CAR virtual joystick plugin in order to accommodate users on mobile devices. Touch: Select if the application natively accepts touch commands for control and does not require the CAR virtual joystick plugin. The application must be capable of managing touch window messages in Windows, and it has been locally tested with a physical Windows touch screen device to ensure successful operation. It is NOT advisable to rely on mouse-to-touch conversion within UE or Unity engines for testing touch message handling, as touch behavior on touch screen devices may behave unpredictably. How to implement multi-touch if the application only supports mouse and keyboard commands?
You need to integrate the SDK and use the onTouchEvent callback to obtain the corresponding touch point coordinates and send keyboard/mouse commands as touch commands. |
Mobile virtual joystick | Left joystick: Sends keyboard WASD commands to the cloud application, usually used to control left/right/up/down movements. Right joystick: Sends keyboard Space key commands to the cloud application, usually used to jump. |
| Description |
Landscape mode (default for mobile devices) | When enabled, the cloud rendered image will be displayed in landscape mode by default on mobile devices. This is typically enabled for applications and games whose display width is greater than the display height. |
Mic enabled by default | When enabled, sound from the end user's microphone will be sent to the cloud application by default (requires end-user device support, such as Chrome requiring permission to use a microphone). This is typically enabled for applications and games that feature voice communication, such as group conferences and interactive live streaming applications. |
Was this page helpful?