ahoeben

The " M117 Tail_1.0 layer: 0 " line that you quote is put there by a postprocessing script ("Display filename and layer on LCD"). This script has a setting called "text to display". If you enter anything at all there, that will be used instead of the filename.

What is wrong with using the search&replace functionality?

Thanks. That's not exactly what I said. What I said was that I think this needs to be fixed in the firmware. Ultimaker unilaterally decided to break support for perfectly valid gcode. Your approach, while it works, is a lot more post-processing intensive. Saving gcode files is likely going to take noticably longer, for all printers (also those not affected by the bug introduced with the S5 firmware and now backported to the UM3). I will consider adding your alternative approach only for "Griffin" flavor printers. But I would still much prefer if the actual bug is fixed.

The “plugins” you are looking for are called “postprocessing scripts” in newer versions of Cura. See the Extensions menu, Post Processing.

It never worked with the S5, now that firmware bug has been copied to the UM3 as well.

You are welcome, but I did not contribute much to Cura 4 other than the mentioned plugins.

You would not be getting the most out of your 2+ machines, but that should work.

Especially for PLA and models that aren’t too complex, the gcode is fairly interchangeable. The 2+ has a better feeder, so Cura may produce gcode that has extrusion and retraction speeds that could cause some skipping on the extruder when printing with the UM2.

That would be @ctbeke

The fix has been tested internally at Ultimaker, and will be part of Cura 4.1. Thanks for testing!

If you start with a Custom FFF Printer, all settings will be at their defaults.

With the architecture of Cura, supporting displaying and entering every metric unit in imperial units would be a lot of work, and the chance of screwing things up for all users (not just those wanting this feature) would be high. As a contributor to the project I don't foresee it happening "any time soon" (or at all, really, unless a very big client needs it).

@phaedrux, thanks for testing. The fix I made is specifically for Macs where everything is excruciatingly slow, because everything ends up being drawn by the processor instead of by the GPU. For them, the workaround with the "Force compatibility mode" checkbox in the general preferences only improved things a tiny bit. My fix forces "compatibility mode" on those computers, not just for layer view but for everything. Your case is why the compatibility mode checkbox is there; apparently your GPU supports the required functionality, but it is just slow when doing it. So you can manually opt for either slow or limited. Fixing that is outside the scope of this particular fix.

Sorry, this is getting confusing. Is the performance of my build any different for you than the performance of the official 4.0 build?

Is everything slow, or just the layer view? Is there any way you can force Cura to use the NVidia GPU instead of the Intel GPU? You have an interesting corner case. The Intel Iris Pro gpu in your Macbook PRO seems to not support OpenGL 4.1 (4.0 is the maximum it will do), but the NVidia GPU does.

Question: what nozzle diameter does your printer have? If I were to guess, I would say 0,015748". Is that a nice number to have all widths depend on? What is the wall width if use 3 extrusion thicknesses? 0,0472441". Do you really want to think in those numbers? 0.4mm and 1.2mm respectively sound like much more workable numbers. I have never seen a 3d printer that is based on imperial units. 3d printers are intrinsically based on metric units. This may be different from CNC machines, I don't know. But Cura is designed for 3d printers.

With an MKS board and display, I would suggest you just start with a recent Marlin firmware and configure it from there instead of a precompiled-for-Ultimaker version.

I replaced the build. Could you test again?

Yes, sorry, apparently something went wrong “signing” the app bundle. I’ll post a new version today.

Ok, thanks for testing. Something must have gone wrong while signing the patched application. I’ll create a new build tomorrow.

That looks like a clone, not an Ultimaker-produced model. As a result, it is hard to know what firmware would work on that printer.

@wildjokers, you could still do me a favor and test if my build works correctly on your new computer. Specifically, I would like to know if it correctly shows the advanced Layer View (with the horizontal "play" slider as well as the vertical layer slider)

See this thread with a link to a test-version that hopefully fixes the slow performance in Cura 4.0

I have created a repackaged build of Cura 4.0 with my fix for the slow rendering on Macs that don't support the newer OpenGL features that Cura uses for the advanced layer view: http://files.fieldofview.com/cura/Ultimaker Cura-4.0.0.dmg Other than the change in the OpenGL context, it should be axactly the same as the original build, and work with your existing configuration. Please let me know if the build works, and if it is indeed faster.

Because I can make a plugin that fixes some of your issues, but I have no say about the UI of Ultimaker Cura? Would you rather I don't make an alternative GUI? I don't understand responses like this. Note that what the plugin does would not have been possible with a plugin in previous versions of Cura. Ultimaker have made the Cura UI more plugin-friendly. Now you have a choice, even if you don't like the default option.