...
Build Configurations refer to the different settings and options used when building a project.
1. Development Configuration
It is used during the development phase of a project.
...
| Note |
|---|
It has less performance optimizations to speed up the compilation process. Not suitable for final, optimized builds meant for distribution and the game may run more slowly than in a shipping build. |
2. Debug Configuration
It has additional information and debug symbols for easier debugging.
...
| Note |
|---|
Debug builds are slower and larger than their Release counterparts. They include additional checks and information that can impact performance. Debug builds are not suitable for final game releases due to their reduced performance. |
3. Shipping Configuration
This is the final version of your game that is intended for distribution to end-users.
...
| Note |
|---|
While optimized for performance and size, it lacks detailed debugging information, making it challenging to diagnose issues. It is not suitable for development or testing phases but is crucial for creating the final game build. |
4. Test Configuration
Similar to the Shipping configuration, but has additional checks and safeguards to catch potential issues during testing.
...
| Note |
|---|
It is slower than the Shipping configuration due to the added checks and may have a larger exe file size. It is primarily used for internal testing before the final release. |
5. DebugGame Configuration
This configuration strikes a balance between the Development and Debug configurations.
...
| Info |
|---|
Note that Blueprint-only projects will not have the option to create a DebugGame build. |
Need help? Contact Support
If you still need help, contact support to get your issue resolved quickly.
...