Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update docs and code to reflect logging support in Burst-compiled jobs #61

Closed
reeseschultz opened this issue Feb 3, 2021 · 2 comments
Closed
Assignees
Labels
enhancement New feature and/or improvement

Comments

@reeseschultz
Copy link
Owner

Adding UnityEngine as an import and calling WithoutBurst in jobs is wearing my patience thin, as I've done it a bazillion times now when troubleshooting. It's also accident-prone.

Thus, I propose a Burst-compatible logging package. I'll think more about the API. I definitely want proper log levels handled in a concise and straightforward manner.

@reeseschultz reeseschultz added the enhancement New feature and/or improvement label Feb 3, 2021
@reeseschultz reeseschultz self-assigned this Feb 3, 2021
@Dreaming381
Copy link

I just saw this in the forums and went here to check if this was just an issue with using 2019.3. But it seems you are no longer using 2019.3.
As of the Unity versions supported by latest DOTS, Debug.Log and friends are supported in Bursted jobs. However, you must use string interpolation or String.Format for this to work (concatenating strings using the + operator is not supported).

@reeseschultz
Copy link
Owner Author

@Dreaming381 that's great to know, thanks for the heads-up. I'll update my docs to reflect that.

@reeseschultz reeseschultz changed the title Add Burst-compatible logging package Update docs and code to reflect logging support in Burst-compiled jobs Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature and/or improvement
Projects
None yet
Development

No branches or pull requests

2 participants