added trouble shooting for screenshots

Author: bitsandfoxes

docs/platforms/unity/troubleshooting/index.mdx

@@ -69,6 +69,10 @@ This is a [known limitation](https://github.com/getsentry/sentry-unity/issues/88
 
 ### Sentry didn't capture Unity's test/helper function ForceCrash
 
-Unity provides a function to test crashes called `UnityEngine.Diagnostics.Utils.ForceCrash()`. The Sentry SDK subscribes to the signal handlers and captures **all signals** received by it. 
+Unity provides a function to test crashes called `UnityEngine.Diagnostics.Utils.ForceCrash()`. The Sentry SDK subscribes to the signal handlers and captures **all signals** received by it.
 But the result of that function doesn't get invoke our callback.
-Outside of this helper funciton, Sentry is unaware of any **real world** crash type that isn't invoking our signal handlers. 
+Outside of this helper funciton, Sentry is unaware of any **real world** crash type that isn't invoking our signal handlers.
+
+### Screenshot contain artifacts
+
+The screenshot capture relies on Unity's `ScreenCapture.CaptureScreenshotIntoRenderTexture` function. When capturing errors in the Editor, this might lead to artifacts or scaling issues in the captured screenshot.