sekisback

no big deal, but i am searching for a solution. I have a different behavior from cura if i start cura by double clicking the AppImage (everything is like expected) or if i start cura from command line by using /usr/bin/cura or /opt/cura/Ultimaker-Cura-5.1.0-linux.AppImage In the second case it seams for me, that the screenresolution is different or maybe the fonts are bigger I tried this also with cura 5.0, in cura 5.0 is no different in the display behavior, never mind which start version i choose. Did someone know this behavior. Using debian. Maybe there is something missing, if i use the cli to start cura 5.1.0 i got this output with cura 5.0 i got this output qt.qml.context: file:///tmp/.mount_UltimajP6F5L/share/cura/resources/qml/Settings/SettingView.qml:427:16 Parameter "index" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.

@ ahoeben, thx for you quick answer, damm you are right I dint checked that. I was the meaning that the file will be stored as gcode. Made my day

Morning is it possible to change the format from gcode to ufp by default? I have an Ender3 Profile in Cura 4.7.1 with octoprint connection and it works like a charm. Now I added the CuraThumbnails Plugin to Octoprint to see the thumbnail form the ufp file. I can slice and use save as *.ufp, than i have to transfer the file to octoprint manualy, so this works. I found under PrinterSettings that i can change the G-Code-Var. In my case by default "Marlin", I changed this to Ultimaker2 without effect. I dont know where to change the export format to ufp to send the file as ufp directly to the printer via cura octoprint plugin