Welcome to the Burst discussion forum.
You can use this space to get the latest news about the Burst Compiler, ask for help, share feedback, and have discussions about the product.
What is the Burst Compiler?
Burst is a compiler that translates from IL/.NET bytecode to highly optimized native code using LLVM. It is released as a Unity package and integrated into Unity using the Unity Package Manager.
Resources
For more information, please have a look at these resources:
-
Videos and tutorials
-
Intrinsics: Low-level engine development with Burst - Unite Copenhagen 2019 (slides)
-
Behind the burst compiler, converting .NET IL to highly optimized native code - DotNext 2018
-
Blog posts
Requirements
The minimum required Unity version to install the Burst Compiler is Unity 2018.4
Getting started
Once you have downloaded the unity editor of your choice:
- Open any Unity Project
- Open the package manager window by going into the Window->Package Manager menu
- Select the Unity Registry
- Find the Burst package
- Press Install
Release Plan
We will be releasing a series of updates to Burst throughout the year.
The Burst Compiler is a verified release and our plan is to support at any point in time:
- one verified version
- one pre-release version
Please follow this forum to get all the updates about our releases and news.
Feedback
In terms of feedback, we’re especially looking for:
- Framework and Tools - Are there use cases that are not covered yet that you would like to do with the Burst Compiler?
- Usability Improvements - Are there any workflows that are unclear or missing?
- General Questions - Is there anything that is unclear or that you don’t understand?
- Developer API - Do you need specific features exposed or changed?
- Documentation and Tutorials - Do you have recommendations about our documentation or ideas for tutorials we should produce?
Please share your feedback in this forum.
How to report bugs
Ideally we’d like any bugs reported through the built-in bug reporter tool, as that will automatically provide us with some relevant context. We understand that it is often not possible to share the sensitive project data with us, so we will do our best to reproduce your findings on our end without a concrete repo case. But if you can, it is always helpful to get a stripped project.
Have a look at this page for more information and best practices around bug reporting.
Once you have submitted a bug report through the bug reporter, please feel free to start a discussion about it in this forum.
Thank you for your interest, we’re looking forward to your feedback!