View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0031721 | Runner | Layers | Public | 2020-05-26 18:03 | 2020-05-27 09:35 |
| Reporter | Dan | Assigned To | Fritz | ||
| Priority | Medium | Severity | C - General | Reproducibility | 100% |
| Status | Assigned | Resolution | Open | ||
| Platform | - | OS | Windows 10 | OS Version | Pro x64 |
| Product Version | 2.2.5 | ||||
| Target Version | Fixed in Version | ||||
| Summary | 0031721: Layers: Reuse of a layer many times doesn't quite clean up each time, causing a consistent FPS drop | ||||
| Description | Reuse of a layer in a room doesn't quite clean up the layer each time, eventually causing a consistent FPS drop if you reuse the layer enough times. You can see this in the sample attached. The original reporter suggests that the use of random seeds and instance positions is also required, but there are mixed thoughts about this on the GMC thread: https://forum.yoyogames.com/index.php?threads/bizarre-performance-decreasing-random-number-related-issue.75174/ | ||||
| Steps To Reproduce | 1. Run the project for Windows VM. 2. Press and release the spacebar. This will cause one "loop" of tiles using a random seed, then a second loop using seed of 0. 3. When the second loop has happened, wait a couple of seconds for your avg fps value to stabilise. 4. Press and release Ctrl. This will cause 999 loops using a random seed each time, then a final loop using seed of 0 again. (It will also remember the old FPS value for you....) 5. Come back to your PC after a few minutes and see that the game is now consistently running at a considerably lower avg FPS than the value which was recorded at the time you pressed Ctrl. Repro: 100% | ||||
| Additional Information | https://yoyogames.zendesk.com/agent/tickets/171284 | ||||
| Tags | No tags attached. | ||||
| 1.4 Found In | |||||
| 2.x Runtime Found In | 2.2.5.378 | ||||
| 2.x Runtime Verified In | |||||