Jump to content

stevepos

Member
  • Posts

    8
  • Joined

  • Last visited

Personal Information

  • 3D printer
    Other 3D printer

stevepos's Achievements

0

Reputation

  1. Hi, Top object in the screenshot below has lines that are not straight on one particular layer and looks messy in the actual print. It's the first layer above support structure. Am using standard High Profile and i added another object to the print to see if that has the same problem. It doesn't. The top object was actually derived from the bottom object, elongated and windows added. I tried setting Top/Bottom Line direction to 90 for this layer but it had no effect. Is there another setting that might correct this. Am using Cura-mb-master-armhf-20210629.AppImage. Gcode attached. Thanks, Steve Walls.gcode
  2. Thanks burtoogle, adding that package has resolved the problem, Cura starts with MESA enabled and I can now see the additional functionallity. Great, many thanks for your help.
  3. thanks, that helped, could be shared library version mismatch?: libGL: MESA-LOADER: failed to open /opt/mesa-20.1/lib/arm-linux-gnueabihf/dri/vc4_dri.so: libLLVM-7.so.1: cannot open shared object file: No such file or directory sudo find / -name 'libLLVM*' -print /usr/lib/arm-linux-gnueabihf/libLLVM-9.so /usr/lib/arm-linux-gnueabihf/libLLVM-9.so.1
  4. couldn't find a way of passing env vars into the appimage. maybe its designed that way. dropping this now as i can live w/o the extra functionallity, but may try again in future, cheers.
  5. Hi burtoogle, Checked permissions and all was 755. Tried 777 on the Dirs and chown -R pi:pi /opt/mesa-20.1, and ran appimage as root. Alas, still got same error with each of these changes. thanks
  6. Hi, Sorry, orrection to previous post. This attached image shows the error. Thanks
  7. Hi, Am trying out the Cura appimage (20200714) on RPI4 8Gb with Raspian OS (32-bit) build 4.19. For me it works fine w/o /opt/mesa-20.1 (20200709) but with mesa am getting the openGL error shown in attached image. Reproduced the error on another RPI4 4Gb with fresh 4.19 OS image. Any ideas what is causing this? Thanks
×
×
  • Create New...