OpenRCT2 / OpenRCT2/OpenRCT2

Selecting too many scenery groups causes objects to go into miscellaneous objects category

Open
#16,226 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
16.2k
Forks
1.9k
Avg merge
1d 20h
Merged PRs (30d)
80

Description

Operating System

Windows 10 Pro 20H2 64 bit

OpenRCT2 build

OpenRCT2, v0.3.5.1 (cb6d741 on develop) provided by GitHub (x64 windows installer)

Describe the issue

When adding too many different scenery groups to a scenario, the ones that (presumably) get loaded in last will be put in the Miscellaneous Objects category. This can happen to footpath items and trees, causing the terrain generation to put something else there. If you select under 31 groups and go to landscape editor, any groups added after those will be put in the Misc category allowing you to "preserve" some categories.

Area(s) with issue?

New Save Format (NSF)

Steps to reproduce
  1. Open Scenario Editor
  2. Enable more than 31 scenery groups
  3. Press forward to Landscape Editor
Attachments

category bug

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the Scenario Editor by enabling more than 31 scenery groups and entering the Landscape Editor. Trace the scenery-group loading and category assignment behavior, then verify that all enabled groups remain correctly categorized and terrain generation uses the intended items.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.