LarkSR3.3
3.3 Environment
Hardware Environment
CPU
Memory
GPU
sound card
Software Environment
Operating System
Chrome Browser
VC Runtime Library
DX Runtime
Text Editor
Virtual Sound Card Driver
Virtual Camera Driver
Virtual Handle Controller Driver
System Settings
Turn Off Antivirus and Firewall
Turn Off Application Running Notification
Setup Automatic Login
Set Never Sleep-Never Turn Off the Display
Using dongle settings
3D Program Adaptation
Program Adaptation Requirements
Installation and Deployment
System Components
Stand-Alone Version
Simple Cluster Version (Windows)
Deployment in Detail
Stand-Alone Intranet
Stand-Alone External Network
Cluster intranet(Windows)
Cluster external network(Windows)
Cluster intranet(Linux Docker)
Cluster external network(Linux Docker)
Deployment Case Study
Edge cluster deployment
LarkXR NAT
LarkXR Turn
Nginx reverse proxy
Server Port Mapping
Advanced Cluster Deployment
GPU dedicated server
Server Deployment Guide
Operating System Precautions
Using
Browser support
Browser support
Front usage instructions
Language support
Application Overview
Enter the application
Video interaction
Voice interaction
Live streaming
Text input
Regional detection
Allocation strategy
Remote pole setting
Gesture instructions
Function menu
PC
Mobile
Exit the application
Backend usage instructions
Login
Data center
Monitor
Usage Statistics
clientErrLog
Applications
Package Management
Package Overview
Add Package
Update package
Delete Package
Application Management
Applications
Add Applications
Share
Mouse Mapping
Reserve Applications
Noun interpretation
Run Applications
RunApplications
Synchronization management
Index
Client List
SR Client Management
Group Mgt
Group management
System Setting
Access Auth List
Workspace
Param Setting
LicenceType
No Operation Timeout
Store
Safe
Region Setting
Custom Logo
Short Note
Port Mapping
Dispatch Policy
Current Limiting
Theme
Users
Change Password
change PWD
Port Forward
guides
Custom
App Index
EnterAppli
Server-side
Application Storage
Standalone
Local Storage
OSS Storage
AWS S3
Cluster
Local storage
OSS Storage
AWS S3
General Features
Disk Space
Sync
Set Max Sync Cnt
Feature Components
DataChannel
Additional Parameters
Smart Voice
video input
voice input
external physical controller
Interactive Mode
How to use
Use Front end
Interactive Mode Interface Integration
Security Settings
Feature Components
Redis
MySQL8
Database Monitoring(druid)
Change userName and PWD
Disable
HTTPS access
Windows
Linux Docker
App Auth
Workplace Access Encryption
SDK ID for encrypted secondary development
security setting
Use AppliList Page
IP Blacklist-Whitelist
Allow Cross-Origin
CORS
Cors For Upload
Frequently Asked Questions (FAQ)
list of common issues
Update Log
product updates
-
+
首页
Program Adaptation Requirements
LarkSR supports the following 4 types: 1. **SR (3D Shared Mode - Parallel Cloud Solution)**: This type restricts applications to pure 3D simulation programs, and a server can run multiple such applications simultaneously. 2. **SR (2D Shared Mode - Parallel Cloud Solution)**: This mode is suitable for applications with both 2D and 3D elements, mainly addressing the multi-instance requirements of applications with 2D elements. Compared to 3D shared mode, the concurrency is lower, but it can replace exclusive mode in many scenarios. This mode supports pre-launch functionality, audio output, data channels, interactive mode, but does not support client adjustment of resolution, microphone, camera, and other device pass-through. Important notes include: 1) The system will automatically create users, and there may be remnants of user directories in user directories; 2) Normal usernames should not start with \_LARKXR\_; 3) RDP services are required, and it is recommended to modify the default RDP port; 4) In strict security reviews, 2D application sharing mode can be disabled in the configuration file (modify the management node configuration file: pxy.render-server.remote-desktop.enable=false); 5) Each 2D application shared connection will consume a certain amount of local bandwidth, but the impact is not significant; 6) Entry into applications is slightly slower than 3D shared mode; 7) Resource scheduling for single-machine multi-card is based on the operating system's polling allocation of multiple GPU resources. 3. **SR (Exclusive Mode)**: For some locally installed applications with user directories, applications that may have cross-user access permission issues, and multi-screen scenarios, it is recommended to use exclusive mode. In this mode, a server can only run one simulation application.**In version V3.3.3.0,this type is removed by default.If you need to enable it,please add the following configuration item in`larkxr-center/application.properties`** ``` pxy.dispatch-policy.enable-exclude-mode=true ``` ## Requirements for Applications in 3D Shared Mode 1. Supported engines include: Unreal, Unity3D, DirectX9, DirectX10, DirectX11, DirectX12, OpenGL, Enscape, etc. 2. It is recommended to start the application with the resolution expected for actual use as the benchmark, and it should be started in maximized window mode, not in full-screen exclusive mode. - Full-screen exclusive mode will cause the server to run only one application, and when the application resolution does not match the server's resolution, the server's resolution will be changed. - Taking a Unity application as an example, **do not** choose the option in the red box:  3. The application must be pure 3D and single-process, paying attention to the following points: - Only applications with single-process windows are supported, such as those developed using Unreal, Unity3D. - Windows pop-ups are not supported; pop-ups need to use graphic rendering selection. - If developing OpenGL programs using QT, replace QT controls with OpenGL/Widget to render together in the scene; otherwise, QT controls will not be captured. - Applications should not open external documents like Word, PDF, Excel through APIs. 4. For applications developed using the Unreal Engine, when specifying the path during application upload, do not fill in the exe program at the root directory. The correct directory should be at the same level -> project name directory -> Binaries -> Win64 -> xxx.exe. If there are startup parameters, add them to the background startup parameter text box. Reference link: [Reference Link](https://www.pingxingyun.com/contribute/detail?topicId=10107&categoryId=3).
admin
2025年4月17日 10:08
转发文档
收藏文档
上一篇
下一篇
手机扫码
复制链接
手机扫一扫转发分享
复制链接
Markdown文件
Word文件
PDF文档
PDF文档(打印)
分享
链接
类型
密码
更新密码
有效期