#Game stopped responding to input in build mode (destroy mode)

1 messages · Page 1 of 1 (latest)

proud seal
#

While in "destroy" mode of the building menu to delete a roof for upgrades, the game stopped responding to any keyboard input besides WASD and mouse input other than camera movement.

I was unable to destroy built objects, unable to exit destroy mode, unable to exit build mode, and unable to exit the game. Had to force-close via taskbar.

The issue was unrelated to my PC, as pressing the windows key brought up the start menu and taskbar and allowed me to force-close the game, and all inputs worked normally everywhere besides in-game (even while Windrose was still running).

Edit: In case this info matters I'm accessing the game through a hosted dedicated server, but the server console did not display any errors in the log, or at least none I was able to interpret as an error.

proud seal
deft sleet
#

Thanks for the detailed report! We'll look into it.
Does this happen often?

proud seal
# deft sleet Thanks for the detailed report! We'll look into it. Does this happen often?

Thank you!

So far, this has happened twice now. The second time was several hours after posting this.

It was the same as described except that I was not deleting a large number of build items (I was building though, but not specifically using destroy mode).

I was able to get inputs to respond again the second time by opening the inventory I believe, but it may have been the journal. I don't remember which exactly, but one of the hotkeys for a menu worked and forced me out of build mode.

I spend a much larger amount of time than "average" building in games, so if this is just an occasional error with building, there may not be too many others who experience it with that kind of frequency. It did happen twice in about 6 hours, but I had literally been building for all six of those hours haha

I can come back and update if it continues to occur.

Thanks for all the hard work, that was one massive (and impressive!) patch notes you guys released for the hotfix tonight!!

deft sleet
#

Thank you for kind words! We have this issue tracked, but might take some time before we can properly investigate this and figure out what goes wrong. Im keeping this thread open with "Unsolved" status, so we'll definitely get to it. Sorry for the inconvenience!