#[SPZ2-6136] [1.0.2-rc1] Scenario selection screen doesn't adapt to custom scenarios

8 messages Β· Page 1 of 1 (latest)

pine herald
#

When loading a custom scenario (via a mod), its panel is partly offscreen in the selection screen, and any other custom scenarios are completely offscreen (there doesn't seem to be a way to scroll). Resolution is 1920x1080 since that seems to affect it.

unkempt parcelBOT
#

Thank you for reporting this bug! Our team will review your report soon.
Feel free to add more details in follow-up messages β€” we're also scanning for duplicate reports automatically now.
πŸ“¨ There are currently 21 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.

πŸ“‹ Log files help us investigate issues. You can find yours here:
β€’ Windows: %USERPROFILE%\AppData\LocalLow\tobspr Games\shapez 2\Player.log

πŸ’Ύ Savegame files (.spz2) are very helpful if relevant to the issue!
Export via Main Menu β†’ Play β†’ click the download icon on the relevant savegame.
You can also find them here:
β€’ Windows: %USERPROFILE%/AppData/LocalLow/tobspr Games/shapez 2/

#

Custom Scenarios are not present in game after making a custom scenario Json and starting a new game.
To Do β€’ Priority: Highest β€’ Fix: None β€’ Game: 1.0.0

Custom scenarios are not available in shapez 2 after creating a custom scenario JSON file and placing it in the custom-scenarios folder within the app data directory. To reproduce, create a custom scenario JSON per Wiki instructions, place it in the appropriate folder, launch the game, and start a new game under the relevant game mode. The custom scenarios do not appear anywhere in the new game flow. Expected behavior is that user-created scenarios should be displayed as selectable options wh...
πŸ’¬ Threads: [1.0.0-alpha5-rc2] Custom Scenarios aren

#

Scenario options challenges screen has overlapping text in several areas for Polish
To Do β€’ Priority: Medium β€’ Fix: 1.0.1 Release (1.0 Fix 1)

When the game language is set to Polish, the Challenge screen (accessed via New Game, Classic Mode, Regular scenario) displays overlapping text in several areas. Larger paragraphs extend beyond their intended borders, overlapping with adjacent Challenge categories. The expected behavior is that text stays within the borders of each Challenge category regardless of language.

#

[Steam Deck] multiple scaling issues in different resolutions of various Aspect ratios
To Do β€’ Priority: Medium β€’ Fix: Probably Never

When playing shapez 2 on Steam Deck at resolutions other than 1280x800 with aspect ratios different from 16:10, UI elements scale incorrectly. This makes it difficult to select options using the cursor or touch input. The issue occurs by launching the game on Steam Deck, changing to any non-default resolution, and starting or loading a savegame. UI elements should be correctly scaled and touch input should be accurately tracked. This fails a Steam Deck CQA checklist test case.

#

Pinned Tasks can exceed the Screen at the bottom
To Do β€’ Priority: Low β€’ Fix: None

When multiple jobs are pinned using the pin feature, the pinned items can exceed the bottom of the screen, causing the last pinned job to be not visible. This occurs on a Full HD screen at default interface scale. Reducing the interface scale below 100% makes the hidden job appear. Expected behavior would be scrollable pins, a limit on total pins, or automatic shrinking when more are added.
πŸ’¬ Threads: [0.1.1] Minor Pinned Task Scroll Bug/QoL

unkempt parcelBOT
#

[SPZ2-6136] [1.0.2-rc1] Scenario selection screen doesn't adapt to custom scenarios

#

πŸ” This bug report has been marked as a duplicate of SPZ2-6136: Custom Scenarios are not present in game after making a custom scenario Json and starting a new game.

Custom scenarios are not available in shapez 2 after creating a custom scenario JSON file and placing it in the custom-scenarios folder within the app data directory. To reproduce, create a custom sce…

Please refer to that ticket for updates.
If you believe this was incorrectly flagged, run /reopen-bug and we will have a look again!

Threads linked to this issue: