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 Drops LSD On Preview Render in MacOS #13417

Closed
2 tasks
EasyG0ing1 opened this issue Sep 30, 2022 · 7 comments
Closed
2 tasks

Cura Drops LSD On Preview Render in MacOS #13417

EasyG0ing1 opened this issue Sep 30, 2022 · 7 comments
Labels
Status: Duplicate Duplicate of another issue. Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Bug The code does not produce the intended behavior.

Comments

@EasyG0ing1
Copy link
Contributor

Application Version

5.1.0

Platform

MacOS 12.5.1

Printer

Anycubic Mega X

Reproduction steps

Second time this has happened to me and the only way I can fix it is by completely wiping the app and related folders then re-install Cura, but for some reason, when it renders previews, it looks like it's on acid ...

see screen shot

Actual results

see screen shot

Expected results

Not that

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

Screen Shot 2022-09-30 at 8 51 24 AM

@EasyG0ing1 EasyG0ing1 added Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Sep 30, 2022
@GregValiant GregValiant added Status: Duplicate Duplicate of another issue. Status: Needs Info Needs more information before action can be taken. Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. and removed Status: Triage This ticket requires input from someone of the Cura team labels Oct 2, 2022
@GregValiant
Copy link
Collaborator

Thanks for the report.
This is one of the cockroach bugs of Cura. It's hard to duplicate and consequently has been impossible to get rid of.
After saving the gcode, open the gcode file in Cura. I believe you will find that all that peripheral stuff is not present in the gcode.

Is this happening with all your models? If so, then please zip a project file ("File | Save Project") and the Cura.log file ("Help | Show Configuration Folder") and post the zip file here. If you could also post some information about your video sub-system that could be helpful. Someone from the Cura team will take a look.

On a less serious note, it's possible you have installed the Timothy Leary version of Cura. It uses Peter Maxx rendering. You can see the effect in this slice of three older model benchies.
PeterMaxx

@github-actions
Copy link
Contributor

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.

@EasyG0ing1
Copy link
Contributor Author

EasyG0ing1 commented Nov 9, 2022

@GregValiant It will take some time before I can provide the additional information requested, since I reset my install after creating this issue. It can take sometimes months before the problem shows up again, so the best I can do is get you what you're asking for the next time it happens.

Timothy Leary version of Cura

Moody Blues ... "Legend Of A Mind" ;-)

@github-actions github-actions bot removed the Status: Needs Info Needs more information before action can be taken. label Nov 9, 2022
@github-actions github-actions bot reopened this Nov 9, 2022
@GregValiant
Copy link
Collaborator

That's fine. Like I said, the bug has been around a while and it's tough to duplicate. It could be related to your specific hardware, or a glitch in the Cura code, or your video system driver doesn't play well with Cura's OpenGL requirements. Nobody knows for sure.
When it happens again try to get good documentation. The more information the better for debugging.

I'm going to close this report as there just isn't much we can do at this point. If it happens again you can open another report.

@EasyG0ing1
Copy link
Contributor Author

EasyG0ing1 commented Nov 17, 2022

@GregValiant - If it matters, I'm running on a 2019 MacBook Pro ... On my last MBP I recall being able to choose which graphics card was the active card but I can't seem to find that option on this one ... it would be an interesting test to see if it has any effect on the problem.

Screenshot

@EasyG0ing1
Copy link
Contributor Author

@GregValiant - The other interesting factor about this issue, is that it takes time (usage of the software) before it happens, and wiping out the install and re-installing from scratch fixes it... which begs the question, what could possibly be changing in the softwares files themselves that would have any impact at all on the rendering of preview images?

@GregValiant
Copy link
Collaborator

I found another reference to this bug #10387

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Duplicate Duplicate of another issue. Status: Under Investigation The issue has been confirmed or is assumed to be likely to be a real issue. It's pending discussion. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

2 participants