Skip to main content

Common Export Errors

”No export template found at the expected path”

What it means: Summer Engine can’t find the runtime files it needs to build a standalone game for that platform. What you already have: the Mac app of Summer Engine comes with the Mac template, and the Windows app with the Windows templates. Web, Linux, Android and iOS builds need templates from Summer’s download server. Solution:
  1. Ask your agent to run summer_export_templates with action: "list", then action: "install" and the missing platforms.
  2. Do not use the editor’s own template download: it fetches stock templates, not Summer’s.
  3. Templates are on the download server from Summer Engine 0.7.1. On 0.7.0, update Summer Engine.
Where templates go and how to check them: Export templates. Still missing? Email support@summerengine.com.

”Cannot export for universal or arm64 if ETC2 ASTC texture format is disabled”

What it means: You’re trying to export for Apple Silicon Macs without the required texture compression format. Solution:
1

Open Project Settings

Project → Project Settings
2

Enable Texture Compression

Rendering → Textures → VRAM Compression → Import ETC2 ASTCToggle to On
3

Wait for Reimport

Summer will reimport all textures (1-5 minutes)Status bar shows progress
4

Try Export Again

Return to Project → Export and try exporting
Why this happens: Apple Silicon Macs use different texture compression than Intel Macs/PCs.

”Cannot export for universal or x86_64 if S3TC BPTC texture format is disabled”

What it means: You’re trying to export for Windows/Intel Macs without the required texture format. Solution: Same as above, but enable Import S3TC BPTC instead of (or in addition to) ETC2 ASTC. Pro tip: Enable both formats at once if you’re releasing on both Mac and Windows. Avoids reimporting twice.

”Invalid Bundle Identifier”

Platform: macOS only What it means: You’re using the default placeholder (com.example.game) which isn’t valid for distribution. Solution:
1

Open Export Preset

Project → Export → Select your macOS preset
2

Find Bundle Identifier

Scroll to Application → Bundle Identifier
3

Replace with Unique ID

Use reverse-domain format:
  • com.yourstudio.yourgame
  • io.itch.username.gamename
  • com.yourname.projectname
Must be lowercase, use dots to separate, no spaces
4

Save

Preset is now valid for export!
Why it matters: macOS uses bundle identifiers to track apps. Without a unique one, your game might conflict with other apps or not install properly.

Export Process Issues

Export Takes Forever

Normal times:
  • Small game (100 MB): 30-60 seconds
  • Medium game (500 MB): 1-3 minutes
  • Large game (2 GB): 5-10 minutes
If taking longer:
  • Check disk space (need 2-3x game size free)
  • Close other resource-heavy apps
  • The first export is slower (it imports every asset); later exports are faster

Export Crashes Summer Engine

Possible causes:
  • Out of memory (exporting huge game)
  • Corrupted asset in project
  • Disk full
Solution:
  1. Save your project
  2. Restart Summer Engine
  3. Check Output tab for error messages before exporting
  4. Try exporting to a different location (different drive)

Exported Build Is Missing Files

Cause: Files not properly added to export or excluded by filters Solution:
  • Check Resources tab in export preset
  • Ensure Export Mode is Export all resources (not “selected resources”)
  • Verify Filters to export doesn’t exclude needed files

Runtime Issues (Exported Game Problems)

Game Won’t Launch After Export

Cause: Missing Visual C++ RuntimeSolution: Most PCs have it. If not, the player installs the latest supported Visual C++ Redistributable from Microsoft.If it happens on many PCs, tell us on Discord.
Cause: Unsigned app downloaded from internetSolution for players: Right-click app → Open → Click Open in dialogSolution for developers: Code sign your app (requires Apple Developer account)
Cause: Executable not marked as executableSolution:
Debugging steps:
  1. Run from terminal/command line to see error messages
  2. Check if it works on your dev machine
  3. Verify export architecture matches OS (arm64 for Apple Silicon, x86_64 for Intel/AMD)
  4. Test with minimal project - does export work with empty project?

Graphics Issues in Exported Game

Black screen or missing textures:
  • Check texture compression is enabled for the target platform
  • Verify shaders work in the editor before exporting
  • Test on a GPU different from your dev machine
  • Check the minimum macOS/Windows version in export settings
Low FPS after export:
  • Export a release build: turn off Export With Debug in the export dialog
  • Check Project Settings → Rendering → Quality - lower settings if needed
  • Profile in editor first (Debug → Profiler) to find bottlenecks

Audio Issues in Exported Game

No sound or crackling:
  • Test that audio works in the editor first
  • Check the audio format (Ogg Vorbis is smaller than WAV for music)
  • Verify the player’s PC has working audio drivers
  • Test with both speakers and headphones

Platform-Specific Warnings

macOS: “Unidentified Developer” Warning

This is normal for unsigned apps! What players see:
“MyGame.app cannot be opened because it is from an unidentified developer”
How players bypass it:
  1. Right-click the app (don’t double-click)
  2. Click Open from menu
  3. Dialog appears with Open button
  4. Click Open - app launches
Permanent fix: Code sign and notarize your app (requires an Apple Developer account) Alternative: Publish on Steam: games Steam installs do not get this warning

Windows: SmartScreen Warning

What players see:
“Windows protected your PC. Microsoft Defender SmartScreen prevented an unrecognized app from starting.”
How players bypass it:
  1. Click More info
  2. Click Run anyway
Permanent fix: Code sign your .exe. See Windows export: code signing. Alternative: Publish on Steam, where games do not show this warning, or on itch.io, where players can click through it
Don’t worry about these warnings for itch.io releases! Indie game players are used to clicking through them. Steam removes them automatically.

File Size Issues

Exported Game Is Huge

Check these:
  • Using WAV audio instead of Ogg Vorbis? (WAV is 10x larger)
  • Uncompressed textures? (Enable S3TC/ETC2 compression)
  • Debug build? (Turn off Export With Debug)
  • Unused assets in project? (Clean up before export)
Compression comparison:
  • WAV audio (1 minute): ~10 MB
  • Ogg Vorbis (1 minute): ~1 MB
  • Uncompressed texture (1024x1024): ~4 MB
  • Compressed texture (1024x1024): ~200 KB

Exported Game Is Too Small (Missing Assets)

Possible causes:
  • Export filters excluding your files
  • Resources not saved in project
  • Embed PCK disabled + you only distributed .exe (need both .exe and .pck)
Solution: Check Export preset → Resources tab → Export mode is Export all resources

Performance Problems After Export

Game Runs Slowly in Exported Build

Check:
  1. Did you export a debug build? (It is slower)
    • Solution: Turn off Export With Debug in the export dialog
  2. Is V-Sync enabled? (Limits to 60 FPS)
    • Project Settings → Rendering → V-Sync
  3. Profile in editor first
    • Debug → Profiler → Find bottlenecks before exporting
Debug vs release:
  • Debug build: extra checks and debug output, so it runs slower
  • Release build: full speed

Game Crashes After Running for a While

Possible causes:
  • Memory leak (check if RAM usage grows over time)
  • Unhandled errors in game code
  • Resource loading issues
Debugging:
  1. Export a debug build with console output (Windows: Export Console Wrapper = Debug Only, and run the .console.exe)
  2. Run exported game and watch for error messages
  3. Fix the issues in your project, then export again

Steam-Specific Issues

Build Uploaded But Players Can’t Download

Cause: Build not set live on default branch Solution:
  • Steamworks dashboard → Builds tab
  • Select your build → Set build live on default branch

Wrong Version Downloading

Cause: Multiple builds on different branches Solution: Check which branch is set as default in Steamworks

macOS Build Won’t Run Through Steam

Cause: Incorrect launch executable path Solution: Set launch executable to:
Not just MyGame.app - must point to binary inside the bundle!

itch.io-Specific Issues

Upload Fails

File size limits: itch.io limits the size of each uploaded file. Large games upload with itch.io’s butler tool. Solution: Compress your build, or upload it with butler.

Web Game Doesn’t Load

For HTML5 exports:
  • Ensure you zipped the entire export folder, not just index.html
  • Set correct index file (index.html)
  • Check browser console (F12) for errors
  • Some browser features require HTTPS (SharedArrayBuffer) - itch.io provides this

Getting More Help

Discord Community

Ask in #game-dev channel - community helps fast!

Email Support

Persistent export issues or bugs

Export for Summer Games

Store bundles, web builds and export templates

Back to Export Guides

Platform-specific export instructions
Before asking for help: Include this info:
  • Platform you’re exporting to (macOS/Windows/Linux)
  • Export settings you’re using (architecture, embed PCK, etc.)
  • Error message (full text or screenshot)
  • Does it work on your dev machine but not others?
This helps us solve your issue faster!
Contact us: