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

Object sprites randomly glitching when Object Selection is frequently changed. #14011

Open
2 tasks
Xtreme97-RCT opened this issue Feb 7, 2021 · 1 comment
Open
2 tasks
Labels
bug Something went wrong.

Comments

@Xtreme97-RCT
Copy link

OS: Windows 10
Version: 0.3.2
Commit/Build: latest develop, but also affects previous develop and release builds.

This has been happening for some time so I don't think it's specific to any new develop changes. When a user changes the object selection, either by the Object Selection menu or just by loading a park with a different object selection to the currently loaded one, some objects can glitch at random. The way this manifests is that the sprite image for an object is replaced by a random sprite, either from another object or from somewhere else in the game (for example a few times I've had the image replaced by part of the glass ride entrance hut). This affects both vanilla and custom scenery.

Currently the only fix is saving the game, quitting OpenRCT2 and restarting, which resets everything to normal. The changes aren't permanent so this is more of a persistent bug than anything game-breaking.

  • Reproducible in RCT2 (vanilla)?
  • Specific to multiplayer?

Steps to reproduce:

  1. Load a park and frequently change the object selection or load multiple parks with distinct object selection. Most notable when using custom scenery but affects vanilla objects too.

Screenshots / Video:
Github_issue_object_glitch
Github_issue_object_glitch_2

@Gymnasiast
Copy link
Member

I have noticed this too. It runs out of image slots -- apparently they are not all freed when objects get unloaded.

@Gymnasiast Gymnasiast added the bug Something went wrong. label Feb 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something went wrong.
Projects
None yet
Development

No branches or pull requests

2 participants