Skip to content
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

Cura 5 Beta doesn't support main display on second monitor #12102

Open
2 tasks
theryanmc opened this issue May 5, 2022 · 26 comments
Open
2 tasks

Cura 5 Beta doesn't support main display on second monitor #12102

theryanmc opened this issue May 5, 2022 · 26 comments
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: Bug The code does not produce the intended behavior.

Comments

@theryanmc
Copy link

Application Version

5.0.0-beta

Platform

Windows 10

Printer

Creality Ender 3 S1 Pro

Reproduction steps

Set your second monitor as main display
Open cura (you will see the launch window on the not main monitor)
Any pop up windows will also show up on that monitor

Actual results

Cura won't respect the main monitor preference in windows 10.

Expected results

Cura would load popups on the main monitor, or at least on the monitor where Cura is open.

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

nothing need.

@theryanmc theryanmc added the Type: Bug The code does not produce the intended behavior. label May 5, 2022
@hawkeyexp
Copy link

Same effect on windows 11

@MariMakes
Copy link
Contributor

Hi @theryanmc thanks for reporting this.
I will bring this up with the team, and keep you posted.

@MariMakes MariMakes added the Status: Triage This ticket requires input from someone of the Cura team label May 23, 2022
@MariMakes
Copy link
Contributor

Hey @theryanmc and @hawkeyexp
It has been discussed with the team and we recognize the behavior you are describing.
Unfortunately, it has no priority for us to fix or implement this, therefore we decided to defer this.
I hope you understand.

@MariMakes MariMakes added Status: Deferred We don't have time to work on this for now but intend to in the future. and removed Status: Triage This ticket requires input from someone of the Cura team labels May 24, 2022
This was referenced May 24, 2022
@ScottFerg56
Copy link

Clipboard Image
This bug may be more serious than you know! I've attached a screenshot of the upper-left portion of my primary monitor which shows what I saw when I first ran v5.0. If I close it on my secondary monitor, it reopens with the updated size and position on the 2nd monitor. BUT, anytime I close Cura on my primary monitor it reopens this way! Just a sliver that requires some resizing to expose enough of the titlebar to move it to a usable position. (See my other comments on #12140 which was closed and deferred to this bug.)

@hawkeyexp
Copy link

:-( I can understand it's a "cosmetic" issue and functional bugs has to be fixed first but it sucks every day :-)

@RonenGru
Copy link

This is not a cosmetic issue. On my dual display I have the same behavior. However, in my system it goes further than just being cosmetic because whenever I open a secondary windows (for example Marketplace) it just opens a blank window on the second monitor and freezes Cura. I need to shutdown the Cura service to get out of it. This makes the program completely unusable with two monitors. In order to make it work I need to disable the secondary monitor. When I do this the program behaves as it should. Again, this is not a minor issue! Have not experienced this problem with any other version of Cura or with any other application.

@fieldOfView
Copy link
Collaborator

Is this deferred or closed? Normally a deferred issue is left open.

@fieldOfView
Copy link
Collaborator

This phenomenon is especially problematic on systems where opening a window on the second display results in an unresponsive window (ie: those systems that previously required unchecking the "Restore window position on start" option in the general preferences).

@MariMakes
Copy link
Contributor

Oh! My mistake, I'll open it back up again and bring it up with the team.

@MariMakes MariMakes reopened this May 30, 2022
@Vandresc Vandresc added the Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. label May 30, 2022
@Vandresc
Copy link
Contributor

Devs see CURA-9344 for our internal reference.

Thank you all for your feedback!

@Vandresc Vandresc added Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. and removed Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. labels May 31, 2022
@nallath nallath removed the Status: Deferred We don't have time to work on this for now but intend to in the future. label Jun 10, 2022
@RonenGru
Copy link

RonenGru commented Jun 16, 2022

I think I found the source of this problem. It's the Nahimic service in Windows...interestingly this was a problem with PrusaSlicer as well. The Nahimic service is an audio enhancement software that works alongside the system audio driver. The solution with a dual monitor setup is to disable (or better still stop) the Nahimic service completely. Unless you have a specific need for it, you probably won't experience any issues disabling it. The way to disable it is by typing in "services" in the Windows search field (bottom left corner) and opening the services window:

Ultimaker_5_Nahimic_Service_Bug

Right click on the Nahimic service >Properties>Startup type...set to either Manual or Disabled...

Now you'll be able to run Ultimaker Cura 5 on a dual monitor system without freezing or crashing. RG

@ScottFerg56
Copy link

I think I found the source of this problem. It's the Nahimic service in Windows...

My system does not have a 'Nahimic' service and is not suffering crashing/freezing problems, so I suspect we have a second issue being conflated with the original one here.

@RonenGru
Copy link

You're right, there are two issues that are apparently unrelated but which seemed to be related originally. The Cura splash screen still opens on the second monitor and so do any secondary windows (For example, Post Processing Scripts) but with the Nahimic service disabled Cura doesn't crash any more. With the Nahimic service turned on Cura would inevitably crash. I'll post the Nahmic solution in the appropriate thread. Thanks. RG

@nallath
Copy link
Member

nallath commented Jun 17, 2022

I think that the crashing issue is related to Nahimic. It using the "wrong" screen is a different issue.

@hawkeyexp
Copy link

Should be addressed and fixed - cura guys please solve it :-)

@MariMakes
Copy link
Contributor

Quick update on our side for those who are still stuck.

We might have a fix for some of the issues reported here. 🎉
It's a bit hard for us to test, but we have a nightly build available.
Can you please try it out and let us know if it resolves your issue?

You can find the download links and the discussions here.

@tdwilli1
Copy link

tdwilli1 commented Mar 31, 2023 via email

@tdwilli1
Copy link

tdwilli1 commented Mar 31, 2023 via email

@hawkeyexp
Copy link

I can confirm it is working, too.

Startup splash is always shown on primary display defined by windows and dialog windows from plugins etc. and upload dialog (moonraker plugin) is shown on same display where cura is placed - also if cura is moved after opening from one screen to another!
Great work - seems the bug is fully solved!

@RonenGru
Copy link

RonenGru commented Mar 31, 2023 via email

@rburema
Copy link
Member

rburema commented Apr 4, 2023

Thanks for testing everyone! That's a relief :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: On Backlog The issue / feature has been reproduced and is deemed important enough to be fixed. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests