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

Preview not working #4896

Open
surdu opened this issue Dec 1, 2019 · 7 comments
Open

Preview not working #4896

surdu opened this issue Dec 1, 2019 · 7 comments

Comments

@surdu
Copy link

surdu commented Dec 1, 2019

Describe the bug
Preview doesn't work on MacOs for the latest build from master, or any available dev build from the download page.

To Reproduce
Steps to reproduce the behavior:

  1. Download the latest dev MacOS build, currently 66af505
  2. Load any stl
  3. Go to the Preview tab
  4. See nothing
  5. Same for Layers tab
  6. Also 'Send to printer' doesn't seem to send anything, though the save gcode works

Desktop (please complete the following information):

  • OS: MacOS 10.14.6 (18G1012)
  • Version: 1.3.1-dev master (66af505)
@lordofhyphens
Copy link
Member

Try: https://dl.slic3r.org/dev/mac/jenkins/

There's something going on with the Mojave builds that I have not been able to sort out.

@lordofhyphens
Copy link
Member

@surdu re: send to printer, are the permissions set correctly for the serial device for your printer (if it's a usb connection)?

@surdu
Copy link
Author

surdu commented Dec 5, 2019

@lordofhyphens It's an OctoPrint server, and it works on the release build and Jenkins build. I'll test it again after the preview issue is fixed. I feel that they are related. If it's still an issue afterwards, I'll create a separate ticket.

@lordofhyphens
Copy link
Member

Weird.

@lordofhyphens
Copy link
Member

lordofhyphens commented Dec 6, 2019

@surdu
Copy link
Author

surdu commented Dec 6, 2019

@lordofhyphens Both preview and send to printer works 😉

@lordofhyphens
Copy link
Member

... well that is weird as someone else with a related problem is still having issues, but you aren't?

So that tells me at least part of it is building on Travis at all, and not how we are building on Travis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants