Unity WebGL构建在BrightSign XT1144播放器加载至90%卡住的技术求助

Hey there, I’ve dealt with similar head-scratchers when deploying WebGL content to BrightSign players, so let me share some actionable steps that might get you past that 90% loading hang.

First, let’s recap what you’ve already tried (great moves by the way): enabling Development Build, disabling compression/data caching, turning off engine code stripping, and updating BrightSign OS to 8.2.72. Let’s add some targeted checks tailored to BrightSign’s specific environment:

1. Force WebGL 1.0 Compatibility #

BrightSign’s Chromium-based engine in OS 8.x doesn’t always play nice with WebGL 2.0 features. Try forcing Unity to build for WebGL 1.0 instead:

• Open your Unity project
• Navigate to Edit > Project Settings > Player > WebGL Settings
• Under the Rendering Path dropdown, select WebGL 1.0
• Rebuild your project and re-deploy the HTML5 widget to the player

2. Validate Widget File Structure & Paths #

BrightAuthor:connected can be finicky about how WebGL assets are packaged. Double-check these details:

• Ensure you’re including all Unity WebGL output files: the Build folder, TemplateData folder, and the main .html file in your widget
• Avoid spaces or special characters in file/folder names—BrightSign’s file system struggles with these
• Confirm the widget’s "Local Files" path points directly to your main Unity HTML file, not a parent subfolder

3. Check the Player’s Debug Console for Errors #

Since you have Development Build enabled, you can dig into what’s failing mid-load:

• Connect your BrightSign player to your local network
• Open a browser and navigate to the player’s IP address (find this in BrightAuthor:connected or the player’s on-screen settings)
• Go to the Debug tab and open the JavaScript console. Look for errors like missing asset requests, unsupported JS APIs, or memory allocation failures—this will usually pinpoint the exact blockage.

4. Reduce Memory Footprint #

Embedded devices like the XT1144 have tighter memory limits than desktop browsers. Try trimming your build’s memory usage:

• In Unity’s WebGL Settings, lower the Default Memory Size (start with 256MB or 512MB instead of the default 1GB)
• Compress textures to device-friendly formats (ASTC, ETC1) in Unity’s Texture Import Settings to cut down on load data
• Remove any unused assets or shaders from your project—even small, unused files can add up

5. Test with an Ultra-Minimal Build #

Strip your project down to the absolute basics: create a new Unity project with just a single plane and a low-res texture, build it for WebGL, and deploy that to the player. If this loads successfully, the issue is likely tied to specific assets or settings in your original project (like a shader that’s incompatible with BrightSign’s engine).

If none of these steps resolve the issue, it’s worth verifying that your build’s resource demands don’t exceed the XT1144’s hardware specs. Also, try re-transferring your files to the player—USB transfers sometimes corrupt assets, so network deployment via BrightAuthor:connected might be more reliable.

内容的提问来源于stack exchange，提问作者asj