Why Test Exported Builds?
Your game might work perfectly in the Summer Engine editor but have issues when exported. Always test exported builds before releasing to players! This guide shows you how to properly test your game after export but before release.Quick Testing Workflow
Export Your Game
Test on Your Development Machine
Test on a Clean Machine
Fix Issues and Re-export
macOS Local Testing
First Run: Ad-Hoc Signing
Summer Engine creates ad-hoc signed builds by default. These work on your Mac but have security dialogs.Export Your Game
- Bundle Identifier:
com.yourgame.test(any reverse-domain format) - Codesign → Codesign: Disabled or Built-in (ad-hoc only)
- Notarization → Notarization: Disabled
~/Desktop/YourGame.appLaunch the Exported Game
YourGame.appHandle Security Dialog
- Right-click (don’t double-click!)
YourGame.app - Click Open from menu
- Click Open in the dialog
Grant Permissions
Why the Security Warning Appears
Ad-hoc signed apps (for testing):- Run on your Mac
- Request permissions properly
- Good for development testing
- Other people’s Macs warn about them (Gatekeeper) when they are downloaded
- Run on anyone’s Mac
- No security warnings
- Need an Apple Developer account
- Usually not needed for Steam; optional for itch.io
Testing Features That Only Work in Exports
Microphone/Audio Input
Why it matters: Voice chat, voice commands, audio recording In editor: May not request permissions properly (macOS security limitation) In export: the macOS permission dialog appears on first use Set up the export preset first. On macOS a game can only use the microphone when its preset says so:- Privacy → Microphone Usage Description: one sentence that tells players why the game needs the microphone
- Codesign → Entitlements → Audio Input: On
Export and Launch
Trigger Mic Usage
Grant Permission
Verify It Works
- Speak into mic
- Check audio input is captured
- Test your voice features work properly
- After granting permission, verify in System Settings → Privacy & Security → Microphone
- Your game should appear in the list
Camera Access
Similar process to microphone - permission dialog appears on first use in exported build.File System Access
Save games and user data (user://):
- In the editor and in the export:
~/Library/Application Support/Godot/app_userdata/YourGame/on macOS, unless your project sets a custom user folder res://is read-only in an exported game: never save there
- Save game in exported build
- Quit game
- Launch again - verify save loaded
Windows Local Testing
No Security Warnings on Your PC
Windows trusts your own builds by default. But test what other users will see:Export for Windows
MyGame.exeTest Launch
MyGame.exe - should run immediatelyTest on Friend's PC
MyGame.exe to another Windows PCThey’ll see: Windows Defender SmartScreen warningWhat Users See (Unsigned Windows Build)
First launch on clean PC:- Double-click
MyGame.exe - Windows Defender SmartScreen appears:
“Windows protected your PC. Microsoft Defender SmartScreen prevented an unrecognized app from starting.”
- Click More info
- Click Run anyway
- Game launches
Performance Testing
Test Debug vs Release
Debug Export (For Testing)
Debug Export (For Testing)
- Shows debug messages in the console
- Runs slower than release
- Larger file size
Release Export (For Distribution)
Release Export (For Distribution)
- Full optimization enabled
- Smaller file size
- No console output
- Maximum performance
- In the export file dialog, Export With Debug on makes a debug build; off makes a release build
- On Windows, Debug → Export Console Wrapper set to Debug Only adds a console
.exeto debug builds, so you can read their output
Framerate Testing
Check FPS in exported build:- Enable FPS display in your game (or use external tools)
- Run through demanding scenes
- Verify maintains target FPS (30 or 60)
- Profile in editor first (Debug → Profiler)
- Optimize before exporting
- Lower graphics settings in Project Settings
Testing on Clean Machines
Why This Matters
Your dev machine has:- Summer Engine installed
- All dependencies
- Your project files
- Visual C++ runtimes
- Ideal testing environment
- Nothing except the OS
- Might be missing runtimes
- Different GPU/drivers
- Real-world conditions
- Missing DLL files (Windows)
- Graphics driver incompatibilities
- Audio device issues
- Save file path problems
How to Test on Clean Machine
- Use a Friend's Computer
- Virtual Machine
- Different User Account
- Export your game
- Copy to USB drive or upload to Google Drive/Dropbox
- Friend downloads and runs it
- Watch them play (screen share if remote)
- Note any errors or issues
Testing Checklist
Before releasing your game, verify:Launch and Stability
- Game launches without errors
- No crashes during 30+ minutes of gameplay
- Game can be quit properly (doesn’t hang)
- Multiple launch/quit cycles work (no state corruption)
Graphics
- All textures load correctly
- Shaders work (no pink/magenta materials)
- UI scales properly at different resolutions
- Fullscreen and windowed modes work
- Game looks correct on different monitors
Audio
- Music plays without crackling
- Sound effects trigger correctly
- Volume controls work
- Audio doesn’t cut out or distort
- Works with both speakers and headphones
Input
- Keyboard controls work (if applicable)
- Mouse controls work (if applicable)
- Gamepad controls work (if applicable)
- Input remapping works (if your game has it)
Game Features
- Save/load works
- Saved data persists after quitting
- All levels/content accessible
- Achievements unlock (if implemented)
- Multiplayer connects (if applicable)
Platform-Specific (macOS)
- Microphone permission requested (if using voice)
- Camera permission requested (if using camera)
- Game works on both Intel and Apple Silicon (if using universal)
Platform-Specific (Windows)
- No DLL missing errors
- Works on Windows 10 and 11
- Runs on a clean PC with no extra installs
Voice Feature Testing (Special Case)
If your game uses microphone input (voice chat, voice commands):The Editor Problem
Issue: When the editor runs your game, macOS asks for microphone access for the editor, not for your game. If the editor never got access, voice features look broken. Result: Voice features may appear broken in the editor but work fine in exported builds.The Solution: Test Via Export
Export Your Game
Launch Exported .app
Trigger Voice Feature
Permission Dialog Appears
Grant and Test
Fixing Issues Found During Testing
Game Crashes on Launch
Debug process:Export in Debug Mode
Launch from Terminal
Read Error Messages
- Missing file errors
- Script errors
- Resource loading failures
Fix in Summer Engine
Graphics Issues (Missing Textures, Pink Materials)
Possible causes:- Texture compression not enabled for platform
- Shaders not exported properly
- Resources not included in export
- Verify texture compression enabled (ETC2 ASTC for Mac, S3TC BPTC for Windows)
- Check Export → Resources → Export Mode is “Export all resources in project”
- Re-export and test
Audio Not Playing
Check:- Audio files are Ogg Vorbis, WAV or MP3
- AudioStreamPlayer nodes properly configured
- Audio bus not muted
- Test with headphones (not just speakers)
Testing Different Architectures (macOS)
macOS has three architecture options - each needs testing if you support it:Universal (Recommended)
What it is: Single app that runs on both Intel and Apple Silicon Macs How to test:- Test on an Apple Silicon Mac
- Test on Intel Mac (if you have access)
arm64 Only
What it is: Apple Silicon only (smaller file size) How to test: Runs on Apple Silicon Macs only Will NOT run on: Intel Macs (shows error)x86_64 Only (Legacy)
What it is: Intel Macs only How to test: Runs on Intel Macs On Apple Silicon: Runs via Rosetta 2 (translation layer) - slower performanceTesting Save Data
Where Saves Go
user:// is the same folder in the editor and in the exported game, unless your project sets a custom user folder:
- macOS:
~/Library/Application Support/Godot/app_userdata/YourGameName/ - Windows:
%APPDATA%\Godot\app_userdata\YourGameName\ - Linux:
~/.local/share/godot/app_userdata/YourGameName/
Test Save Persistence
Create Save Data
Quit Completely
Relaunch
Verify Save Loaded
- Using wrong directory (hardcoded paths instead of
user://) - Not closing the
FileAccess(callclose()or let it go out of scope) - File permissions issues on different OS
Performance Testing
Compare Editor vs Export
Expected: Exported game runs faster than editor (especially Release builds) If exported game is slower:- Check you exported a release build (Export With Debug off)
- Profile in editor first (Debug → Profiler) - find bottlenecks before exporting
- Test on same machine for fair comparison
Minimum Spec Testing
Test on lower-end hardware:- An older Intel Mac
- Budget Windows PC
- Integrated graphics (Intel/AMD iGPU, not dedicated GPU)
- Maintains target FPS (30 or 60)
- No stuttering during gameplay
- Memory usage stays reasonable (< 4 GB for most indie games)
Platform-Specific Testing
macOS Specific
Test these features:- Retina display rendering (high DPI)
- Fullscreen vs windowed mode
- Menu bar integration (if using native menus)
- Dock icon appears correctly
- Microphone permissions (if using voice)
- Trackpad gestures (if supported)
- The newest macOS
- The version before it
Windows Specific
Test these features:- Rendering on the player’s GPU (Vulkan or Direct3D 12 for Forward+ and Mobile, OpenGL for Compatibility)
- Fullscreen exclusive mode
- Alt+Tab works properly
- Multiple monitor support
- Windows 10 AND Windows 11
- Path separators (
/vs\) in paths you build yourself - File name case: the exported pack is case-sensitive, so
res://Player.pngloaded asres://player.pngworks in the editor and fails in the export - Missing Visual C++ Runtime on a clean PC
Multiplayer Testing
Summer multiplayer games run on Summer’s hosted servers. Test them in two steps:- On your machine, with Local Play. Run two clients against a local server. See Testing it on your machine.
- Online, with the version you release. Join online with the exact build players get, from two devices. See Join online with the version you release.
What to Look For During Testing
Red Flags (Fix Before Release)
- Crashes within the first 5 minutes - major stability issue
- Missing textures or audio - resource export problem
- Stuttering or freezing - performance issue
- Save doesn’t persist - save system broken
- Controls don’t work - input mapping issue
Minor Issues (Fix If Time Permits)
- Occasional visual glitch - note it and fix it if easy
- One sound effect too loud - balance issue
- Typo in UI text - polish issue
- Minor FPS dip in one area - optimize if possible
What’s OK to Ship
- Security warnings on macOS or Windows - normal for unsigned games on itch.io
- Not perfect graphics - indie games are judged on gameplay
- Small bugs you know about - patch them after release
Iteration Speed
Fast Testing Loop
Make Changes
Quick Test in Editor
Export
Test Export
Repeat
Preparing for Release
Once testing is complete:Final Export Checklist
- Export a release build (Export With Debug off)
- Test on clean machine(s)
- All critical bugs fixed
- Save/load verified working
- Performance acceptable on minimum spec
- File size reasonable (< 500 MB ideal for indie games)
- Game can be quit properly
- README/instructions included (if distributing manually)
For Steam
- Exported for all target platforms (Windows, Mac, Linux)
- Tested each platform build
- Build size under Steam depot limits (usually fine for indie games)
- Steam Input configured (if using controllers)
For itch.io
- Game zipped if needed (macOS .app must be zipped)
- File named clearly (
MyGame-Mac.zip,MyGame-Windows.exe) - README explains how to bypass security warnings
- File size under itch.io’s upload limit, or upload with
butler
Common Testing Mistakes
Only Testing on the Development Machine
Problem: Works for you, crashes for users Solution: Test on at least one other computerOnly Testing Debug Builds
Problem: Debug is slow, users get Release build Solution: Always test final Release build before publishingSkipping Platform-Specific Testing
Problem: Works on Mac, crashes on Windows (or vice versa) Solution: Test every platform you’re releasing onNot Testing Permissions
Problem: Microphone/camera don’t work for users Solution: Test exported build specifically for permission dialogsAssuming Editor = Export
Problem: Different behaviors in editor vs export Solution: Always export and test before considering game “done”Getting Help
Discord Community
#game-dev for quick help
