-
Notifications
You must be signed in to change notification settings - Fork 1.9k
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PrusaSlicer not responding when launched on second screen #8400
Comments
Can you please check if this is the issue/solution? #5573 |
I have the same behavior on my home HP laptop and my office Fujitsu desktop. Both setups uses double monitors of the same resolution. Neither use Nahimic or any weird software. All the hardware (mouse/keyboard+drivers) are different. |
Thanks for the report. Can you please try the following build, where we tried to fix the problem? You may need to enter following credentials to download the build: |
This build seam to be forcefully launching PS on main screen, no matter where it was closed. |
Thanks, @ElfyShort. And can you please try one more build? As above, you may need to enter following credentials to download the build: |
I see no difference between this and the previous build I tested, so exactly the same feedback. |
Description of the bug
When PrusaSlicer starts on a second screen, it does not load all the way, and freezes in a "not respond" state.
I have been catching this issue since I started using the slicer (I believe it was version 2.3.1 or 2.3.2).
The bug was preserved till current version 2.4.2.
The way I used to make it running again involved turning off the 2nd screen, and launching the Slicer, making it load normally on the main screen.
Project file & How to reproduce
Launch slicer.
Drag on second screen.
Close slicer.
Launch slicer (to make sure it is starting on second screen).
Slicer does not load.
Version of PrusaSlicer
2.3.2 - 2.4.2
Operating system
win 10
Printer model
Custom model
The text was updated successfully, but these errors were encountered: