X-Frame FPS Accelerator · Troubleshooting & FAQ
This page covers the most common issues users encounter with X-Frame FPS Accelerator and how to resolve them.
| Symptom | FPS does not change after adding X-Frame to the camera. |
|---|---|
| Cause | Current FPS already meets the target, or the method is set to Disabled. |
| Solution |
|
| Symptom | The rendered image appears excessively blurry or pixelated. |
|---|---|
| Cause | Minimum Quality is set too low, or Filtering is set to Nearest Neighbor. |
| Solution |
|
| Symptom | Previous frames leave ghost traces on screen. |
|---|---|
| Cause | The X-Frame camera's clear flags are set to Nothing while the scene has transparency or moving objects. |
| Solution |
|
| Symptom | Canvas buttons or interactive elements do not respond to clicks/taps. |
|---|---|
| Cause | Screen coordinates are offset due to downsampling, or runtime Canvas objects are not registered. |
| Solution |
|
| Symptom | You selected Horizontal or Quad Downsampling but the behavior is always Adaptive. |
|---|---|
| Cause | When URP is detected, X-Frame internally uses Adaptive Downsampling regardless of the selected method. |
| Solution |
|
Visit the Kronnect Support to post your question. Our team will get back to you shortly.
Help us improve this documentation page.