Jump to content

Machine bed not shown


Recommended Posts

Posted · Machine bed not shown
  • Do they show up properly in Prepare mode?
  • Try going to Preferences > Configure Cura..., turn on Force layer view compatibility mode and restart Cura (just because it shouldn't be a problem doesn't mean it isn't).
  • If you could go to Help > Show Configuration Folder and attach the cura.log file in there to a post then we can spelunk through that to see if there's anything interesting.
  • That looks like Linux (and by that I mean it doesn't look like Windows or Mac). Are you running under X or Wayland? I've heard Cura can have problems running under Wayland (but haven't tested it myself because Nvidia still can't be bothered releasing drivers with decent Wayland support).
  • Link to post
    Share on other sites

    Posted · Machine bed not shown

    1. Both, Prepare and Preview shows nothing.

    2. Force layer... turned on. Nothing happens.

    3. No cura.log generated. See the attached capture with the content of the folderlog.png.13d51d7da91af8c98080581bcb94ab8a.png

    4. Yes, I'm using Arch Linux. Sorry for the lack of information. And yes, I'm running under Wayland. But this is the first time getting this issue.

     

    5. Many thanks for your fast and extensive response.

  • Link to post
    Share on other sites

    Posted · Machine bed not shown

    Try looking in ~/.local/share/cura (I still don't know why it creates folders in both locations) for a file called stderr.log and then in the 5.8 directory in there for the cura.log file.

     

    Also: what graphics card do you have and what driver are you using?

  • Link to post
    Share on other sites

    Posted · Machine bed not shown

    FWIW, I get a whole lot more information in nvidia-settings when running under X:

    image.thumb.png.c3eb841f8c5a174b1e94949cdcbb6f2f.png

     

    The log file suggests that it can only detect OpenGL 3.2 capable drivers available:

    2024-08-30 00:15:06,483 - DEBUG - [MainThread] UM.View.GL.OpenGLContext.detectBestOpenGLVersion [124]: Trying OpenGL context 4.1...
    2024-08-30 00:15:06,483 - ERROR - [MainThread] UM.View.GL.OpenGLContext.setContext [40]: Failed creating OpenGL context (4, 1, core=True)
    2024-08-30 00:15:06,483 - DEBUG - [MainThread] UM.View.GL.OpenGLContext.detectBestOpenGLVersion [188]: Failed to create OpenGL context 4.1.
    2024-08-30 00:15:06,483 - DEBUG - [MainThread] UM.View.GL.OpenGLContext.detectBestOpenGLVersion [191]: Trying OpenGL context 2.0...
    2024-08-30 00:15:06,483 - DEBUG - [MainThread] UM.View.GL.OpenGLContext.detectBestOpenGLVersion [198]: We got at least OpenGL context 2.0: 3.2 No profile
    2024-08-30 00:15:06,483 - DEBUG - [MainThread] UM.Qt.QtApplication.initialize [192]: Detected most suitable OpenGL context version: 2.0 No profile

    Although since Cura won't use that it just drops back to 2.0 (which is compatibility mode).

    But then when it tries to create an OpenGL view it craps its pants:

    2024-08-30 00:15:18,389 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [66]: An uncaught error has occurred!
    2024-08-30 00:15:18,389 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: Traceback (most recent call last):
    2024-08-30 00:15:18,389 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]:   File "UM/Qt/Bindings/MainWindow.py", line 289, in _render
    2024-08-30 00:15:18,390 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]:     OpenGL()
    2024-08-30 00:15:18,390 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]:   File "UM/View/GL/OpenGL.py", line 51, in __init__
    2024-08-30 00:15:18,390 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]:     raise RuntimeError("Try to create singleton '%s' more than once" % self.__class__.__name__)
    2024-08-30 00:15:18,390 - CRITICAL - [MainThread] cura.CrashHandler.__init__ [69]: RuntimeError: Try to create singleton 'OpenGL' more than once

    (repeat a bazillion times)

     

    First thing which has probably already been done in the background: make sure you have xorg-xwayland installed (you probably have something which depends on it installed already, but can't hurt to make sure). Not sure if that'll help, but it (probably) can't hurt.

     

    You should probably submit a bug report and see if they can help (or at the very least... get it reported as a bug so they can add it to the list of bugs to fix). Make sure to include your system info, the log files, and you should mention that you're running it under Wayland.

     

    Also, if you can, try running it under X, and if that works probably mention it in your bug report, although then they might just tell you that it's the Nvidia drivers at fault - and they wouldn't necessarily be wrong. Wayland support in the Nvidia proprietary drivers is still pretty immature (I'm usually a pretty early adopter - why do you think I'm running Tumbleweed?) but even I'm sticking back on X for the foreseeable future.

  • Link to post
    Share on other sites

    Posted · Machine bed not shown
    $ glxinfo | grep "version"
    server glx version string: 1.4
    client glx version string: 1.4
    GLX version: 1.4
    OpenGL core profile version string: 4.6.0 NVIDIA 560.35.03
    OpenGL core profile shading language version string: 4.60 NVIDIA
    OpenGL version string: 4.6.0 NVIDIA 560.35.03
    OpenGL shading language version string: 4.60 NVIDIA
    OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 560.35.03
    OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
        GL_EXT_shader_group_vote, GL_EXT_shader_implicit_conversions,

     

    I have ran Unigine Heaven benchmark and seems to work right but seems it only detects OpenGL 3.2.0

    ---- Render ----
    GLRender::GLRender(): Unknown NVidia GPU
    OpenGL vendor:   NVIDIA Corporation
    OpenGL renderer: NVIDIA GeForce GTX 960M/PCIe/SSE2
    OpenGL version:  3.2.0 NVIDIA 560.35.03
    OpenGL flags:    Core Profile

     

    I'll keep searching.

     

    Thanks

     

  • Link to post
    Share on other sites

    Posted · Machine bed not shown

    xorg-xwayland was not installed but installing it doesn't make a difference.

  • Link to post
    Share on other sites

    Posted · Machine bed not shown

    So looks like your system supports OpenGL 4.6 and OpenGL ES (OpenGL for Embedded Systems, a subset of OpenGL aimed at things like phones) 3.2 (which is the last version of it). Not sure why Unigine would (presumably) resort to OpenGL ES (maybe something to do with the "GLRender::GLRender(): Unknown NVidia GPU"?). If Cura is also trying to use OpenGL ES that could be your problem. Unfortunately I can't really help you here as the newest device I have with a mobile Nvidia chip has a GT555M - which is to say "not very new".

     

    I could take a complete stab in the dark and say "make sure everything is set to maximum performance mode" to try and get it to favour regular OpenGL but the answer probably isn't that simple.

  • Link to post
    Share on other sites

    Posted · Machine bed not shown
    Link to post
    Share on other sites

    Posted · Machine bed not shown
    59 minutes ago, theprocrastinator said:

    Good news: it's not just you.

    Bad news: it's not just you and they haven't fixed it for other people yet.

    Definitely worth adding a comment saying you have the same problem.

     

    If your laptop has switchable graphics between the GPU and integrated on the CPU - and most do - you could try using one of the options in this page on the Arch wiki to try and force it to use the integrated graphics and see if that makes a difference.

  • Link to post
    Share on other sites

    Posted · Machine bed not shown
    $ QT_QPA_PLATFORM=xcb ./pathto/UltiMaker-Cura-5.8.1-linux-X64.AppImage

    Seems to solve the problem.

     

    Models take a lot to load.

  • Link to post
    Share on other sites

    Posted · Machine bed not shown
    4 hours ago, theprocrastinator said:

    Models take a lot to load.

    Try opening the Marketplace (at the top right), click the gear icon at the top right of that, scroll down to "USB Printing" and disable that. No idea why it works but for many people it fixes that problem.

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.8 Stable released 🎉
        In the Cura 5.8 stable release, everyone can now tune their Z seams to look better than ever. Method series users get access to new material profiles, and the base Method model now has a printer profile, meaning the whole Method series is now supported in Cura!
        • 3 replies
      • Introducing the UltiMaker Factor 4
        We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
          • Thanks
          • Like
        • 3 replies
    ×
    ×
    • Create New...