-
Notifications
You must be signed in to change notification settings - Fork 233
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
[bug] Bambu Lab Studio 1.1.1.1 crashes while being launched on a secondary display #179
Comments
+1 am also having this issue. |
Mikerium give me you Windows version (build number), and used video card brand? Do you have the latest bios, hardware drivers, ect...? |
already fixed in the newest released version v1.2.0 |
This does still happen in the current v1.2.0.9 of Bambu Studio :/ Running:
and 3 Displays:
Whenever I close Bambu Studio on the Top or Left Display I can't open it up again. It will freeze while launching as described in the posts above. |
+1 this also happens on Mac's running |
Did all of this happen when Studio was moved from one screen to another? |
Hi. @richardhartless-wk |
if you're having this problemo, and its stuck on a side monitor, just set that monitor to your primary monitor, move it to your main, set that back to primary and enjoy |
Description
There is currently a bug preventing Bambu Lab Studio to start on a secondary Display. It happens when you move the Bambu Lab Studio Window to a secondary Display, close it while its still on your non-primary Monitor and then try to re-open it. It will just freeze until it gets the typical white-ish overlay for a non responding App and Windows reports that the App has crashed. Rendering the User to be unable to use the Slicer anymore.
Steps to reproduce:
Environment:
OS: Windows 11 Version 10.0.22000 Build 22000
Bambu Lab Studio: 1.1.1.1
Temporary Workaround
-> It will automatically launch on your primary Display working as intended (as all other Displays are disabled/powered off/unplugged while you start the Slicer)
The text was updated successfully, but these errors were encountered: