The sliding menu bug

Avatar
  • Views 7,707
  • updated
  • Completed - Resolved

Operating System

    Windows 10 Home 64-bit
CPU
    Intel Core i7 6700HQ @ 2.60GHz    43 °C
    Skylake 14nm Technology
RAM
    32.0GB Dual-Channel Unknown @ 1198MHz (17-17-17-39)
Motherboard
    Alienware 0FG0DK (U3E1)
Graphics
    Generic PnP Monitor (1920x1080@60Hz)
    Intel HD Graphics 530 (Dell)
    NVIDIA GeForce GTX 1070 (Dell)    48 °C
    ForceWare version: 378.66
    SLI Disabled
Storage
    931GB Hitachi HGST HTS721010A9E630 (SATA)    36 °C
Optical Drives
    No optical disk drives detected
Audio
    Realtek Audio

Bugs of this kind have been reported before. In short, the bug is this:

Image 3501


It appears to occur under different circumstances. However, I have found one cause of the bug which is very easy to replicate.


Step 1: Open the map editor.

Step 2: Under the map description, begin typing.

Step 3: Whilst typing, press page up.


This recreates the bug. In short, the entire screen is shifted to the left. It is always shifted to the same degree. Once performed, it is, as far as I am aware, irreversible.


It Must be done with the map editor description. Neither the map editor title nor the multiplayer hosting titles work.


If my understanding is correct, page up zooms the camera. I would theorise that the game is attempting to 'zoom out' of the current position and, for some reason, zooming right is deemed to be the correct position. It may be because some of the UI is deemed not to be 'central'. This is because the main menu buttons seem largely in the same position but everything else seems to have moved. I am likely incorrect though. The fact that I am using 1,920 x 1,080 resolution may be important, I am not sure.

The bug is easy to replicate but I attached my output log anyway.

output_log.txt

Game Version:
Steam Public
Platform:
Windows
Avatar
anonymous
  • Completed - Resolved
Avatar
anonymous
  • Completed - Next Patch
Avatar
Stefan Furcht
  • Started
Avatar
anonymous
  • Accepted

God damn it. It's likely due to the UI being rendered as a webpage. We'll look to sort this