PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Stops working on second monitor which is horizontal
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 5.4k
- Forks
- 2.4k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 26
Description
Check version
- I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
Screenshots of crash/graphical issue, version and options menu
There is no error prompt or any kind of message. It just stops working showing that the application is not responding
What are your system specifications and configuration?
Operating System: Windows 10
First Monitor: Acer XF240H, 144,000Hz, 8-Bit, vertical
Second Monitor: ASUS Vs248, 59,940Hz, 8-Bit, horizontal
Graphics Card: AMD Radeon RX 5700 XT
Processor: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
How to reproduce the issue
If I open the application on my first Monitor and attach it onto the top for full window mode it will load and work regardless of old builds or settings and closing and starting it up again. After I drag it onto the second Monitor into full window mode by attaching it on top the window and close it, it will stop working getting stuck on the actual window after the loading window. After that I can't move it back and it won't start working even if I delete builds and settings.
Character build code
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Windows 10 sequence using the two-monitor setup: open the application on the vertical monitor, move it to the horizontal monitor, maximize it, close it, and relaunch. Start by examining the loading-window and saved window/settings behavior; done means the application can relaunch and move between monitors without becoming unresponsive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100