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

Print head display #8487

Closed
viper0078 opened this issue Oct 3, 2020 · 3 comments
Closed

Print head display #8487

viper0078 opened this issue Oct 3, 2020 · 3 comments
Labels
Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes Type: Bug The code does not produce the intended behavior.

Comments

@viper0078
Copy link

Application version
Ver.4.6.2

Platform
Win10

Printer
custom

Hi.
There seems to be something wrong with the print head display that appears when you move the slider bar in the preview.
When the slider bar is increased, the print head in the current position is lighter in color than the print head in the previous position.
無題

I think the colors are reversed.
If you move the screen even slightly, the print head in the current position becomes darker in color.
無題

Also, when the slider bar is reduced, the print head seems to be in the wrong position.
無題

My preference would be for the print head to be displayed in the current position only. Or I would like to be able to optionally specify whether or not to display one previous position.

Best regards.

@viper0078 viper0078 added the Type: Bug The code does not produce the intended behavior. label Oct 3, 2020
@Ghostkeeper
Copy link
Collaborator

Yeah, this issue was known to us already. It's a rendering update bug. If you rotate the camera the rendering updates and it shows the more opaque nozzle in the correct position.

It's been like this since 4.4 or so. I'll see if the team thinks it's worth investigating since I don't think that was ever discussed.

@Ultimaker Ultimaker deleted a comment from zyddst Oct 12, 2020
@GregValiant GregValiant added Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes labels Nov 20, 2024
@GregValiant
Copy link
Collaborator

Is this still an issue in current versions of Cura (5.8.0 and up)? Can this be closed?

Copy link
Contributor

github-actions bot commented Dec 8, 2024

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@github-actions github-actions bot closed this as completed Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

4 participants