ahoeben

Not without logs. See https://github.com/Ultimaker/Cura/#logging-issues It looks like you are having a different issue than the topic starter, because that issue was specific to Cura 4.9.

@hwa The "Print with OctoPrint" option in the caret menu should only be there if an OctoPrint instance is connected to the printer in Cura. Can you check on the DuetRRF printer in Cura (for which I guess you don't have an OctoPrint instance configured) you don't have a "Print with OctoPrint" option?

That is going to be really hard to do generally; how would you perfectly align the existing shape perfectly with the buildplate? It needs to be extremely perfectly aligned because any misalignment will result in the print not sticking on some parts and the nozzle crashing into the existing shape in other parts. Also unless the model is perfectly flat you are going to have areas where the nozzle simply cannot reach without colliding with/scraping over the existing shape.

I would have preferred both files as attachments instead of pasted in a long, unwieldy message. Funny, you have almost the exact same computer as I have, only I have double the RAM and an i7 instead of your i5. Unfortunately, looking over they logs has not given me any new insights or ideas for things to try.

I'm sort of out of ideas then. Perhaps the logs and dxdiag can give us a hint: The log as produced by dxdiag (start -> run -> dxdiag -> save output) The Cura GUI log file, located at %APPDATA%\cura\<Cura version>\cura.log, usually C:\Users\<your username>\AppData\Roaming\cura\<Cura version>\cura.log

I have updated the release with new packages. https://github.com/fieldOfView/Cura-StartOptimiser/releases/tag/v3.6.0-DEV

Thanks for testing. I'll fix the packaging mishap for the Start Optimiser (sorry for the inconvenience).

Due to major changes in Cura 5, all plugins have to be updated by their maintainers and resubmitted to the Marketplace, where they are tested by Ultimaker devs before they are made available to the Marketplace. This process takes some time as you might imagine. In the mean time, you can already help test some of the new versions of my plugins that will eventually end up in the Marketplace here:

Do you know the "Line type" color scheme? There's also an overview of printing time percentages (though no weight percentages per type). Here's a screenshot: (my Cura looks a bit different than yours probably, since I am running the Sidebar GUI plugin)

Now? https://github.com/fieldOfView/Cura-ArcWelderPlugin/releases/tag/v3.6.0-DEV

Did this work in Cura 4.13 with the version of the plugin that is currently in the Marketplace? Can you test this prerelease of the plugin with Cura 4.13? Be sure to download the appropriate .curapackage for Cura 4.13 (from the same page). The monitor page just shows the state of OctoPrint and has little to no effect on the print starting after uploading.

Soon?

I have pushed a new prerelease of the OctoPrint Connection plugin to github: https://github.com/fieldOfView/Cura-OctoPrintPlugin/releases/tag/v3.7.0-DEV Should be less prone to crashing, but the print monitor does not seem to work just yet.

No change at all? What version of the driver do you use now? My current laptop has the same GPU as yours, and I am not seeing this issue. I use driver version 21.20.16-4664. You could try the Cura 5.0 beta, which uses a newer version of the Qt framework which may not have this issue.

There was a time when I knew the issue-number by heart, because it was such a prevalent thing. Good to know you got it worked out.

Yes, certain intel drivers have been known to cause this offset in the past. Please check if intel has a newer driver version. It has been 5 years since I last saw this issue though: https://github.com/Ultimaker/Cura/issues/2068

Thanks, I am on it. The OctoPrint Connection plugin linked above has some issues to work out still.

That's going to be easier with a link to your source code (github?) Try using UM.Label instead of Label. Don't specify a color or a font, that is taken care of by UM.Label. Alternatively use UM.Theme.getColor() from the theme, instead of hardcoding colors. That way your QML will work with both light and dark themes.

Fixed that for you here: https://github.com/Ultimaker/Uranium/pull/811

I have made available an initial set of prerelease versions of some of my plugins here: Once these have undergone some more testing, I will push them to the Marketplace so they can be reviewed and be included in the new Marketplace for Cura 5.0.

With the release of the Cura 5.0 beta, a lot has changed in the core of Cura. So much so, that in order to be compatible with Cura 5.0, all plugin need to be updated and resubmitted to the Marketplace. I maintain a number of plugins, and you can imagine that it takes a while for me to update the plugins but also for the Ultimaker dev team to review them. I will use this post to share with you a growing set of pre-release versions of my plugins so you can test them with Cura 5.0 beta. Edit: All plugins are now in the Marketplace, and the prereleases for these plugins below should no longer be used (but will remain available on github) OctoPrint Connection: https://github.com/fieldOfView/Cura-OctoPrintPlugin/releases/tag/v3.7.0-DEV Mesh Tools: https://github.com/fieldOfView/Cura-MeshTools/releases/tag/v3.7.0-DEV Sidebar GUI: https://github.com/fieldOfView/Cura-SidebarGUIPlugin/releases/tag/v4.3.0-DEV Measure Tool: https://github.com/fieldOfView/Cura-MeasureTool/releases/tag/v1.1.0-DEV Z Offset: https://github.com/fieldOfView/Cura-ZOffsetPlugin/releases/tag/v3.7.0-DEV Linear Advance: https://github.com/fieldOfView/Cura-LinearAdvanceSettingPlugin/releases/tag/v3.6.0-DEV Edit 4/23: OctoPrint Connection: https://github.com/fieldOfView/Cura-OctoPrintPlugin/releases/tag/v3.7.0-DEV (updated) Arc Welder: https://github.com/fieldOfView/Cura-ArcWelderPlugin/releases/tag/v3.6.0-DEV Start Optimiser: https://github.com/fieldOfView/Cura-StartOptimiser/releases/tag/v3.6.0-DEV Titlebar Info: https://github.com/fieldOfView/Cura-VersionInTitlebarPlugin/releases/tag/v3.6.0-DEV Automatic Slicing Toggle: https://github.com/fieldOfView/Cura-PauseBackendPlugin/releases/tag/v3.6.0-DEV Edit 4/25: Printjob Naming: https://github.com/fieldOfView/Cura-CustomJobPrefix/releases/tag/v3.7.0-DEV Material Cost Tools: https://github.com/fieldOfView/Cura-MaterialCostTools/releases/tag/v3.6.0-DEV Setting Visibility Set Creator: https://github.com/fieldOfView/Cura-SettingVisibilityProfileCreator/releases/tag/v3.6.0-DEV Printer Settings: https://github.com/fieldOfView/Cura-PrinterSettingsPlugin/releases/tag/v3.6.0-DEV Edit 5/6: Material Settings: https://github.com/fieldOfView/Cura-MaterialSettingsPlugin/releases/tag/v3.6.0-DEV I will update this list with prereleases of other plugins, or when a new prerelease is necessary to fix a bug. To download these prerelease versions, go to the linked page and scroll down to the 'Assets' section. There you will see curapackages compatible with different versions of Cura. For Cura 5.0 you will need to download the file ending with `Cura5.0.curapackage`. After downloading that file, drop it onto the 3d viewport in Cura 5.0 as if you were opening a 3d model. You will then be prompted to restart Cura. You can drop multiple curapackages one after the other without restarting each time if you want to install multiple plugins. If you want to test these updated release in an older version of Cura, please download the curapackage labeled for that version. It is quite early days, and some of the plugins required extensive work to make them compatible with Cura 5.0. Feedback is welcome, either here or in the issue queue for the respective plugins.

Unfortunately that means users of Cura 5 will not get to use your plugins. Believe me, I know how much work it is to keep plugins up to date and compatible with different versions of Cura; I have been doing that for years. It is a necessary evil; plugins that expect certain code to be available that had to be changed/updated in Cura can crash Cura, and that is not desirable for Ultimaker. I agree that this could be handled better than the current message which suggests removing the plugin entirely; an option to install an update from the Marketplace (if available) would be nice. Another improvement would be a single message about all plugins instead of one message per plugin.

A lot has changed in the version. One major change is that the GUI framework Qt was updated from version 5 to version 6, to support newer operating systems (and fix multiple bugs with the previous version of Qt, which was no longer updated). Unfortunately this means that most of the UI of Cura and its plugins has to be made compatible with this newer version of Qt. Because of that all plugins need to be updated and resubmitted to the Marketplace. Existing profiles should be upgrade by Cura automatically (if they were installed in the correct location).

In the General preferences inside Cura, there's an option "Restore window position on start", which is checked by default. If you uncheck that option, Cura should always open on the primary display.

We can't tell from your .gcode file how you modded your Cura, so it is hard to tell what is going on. A project file would be much more helpful. Create one using File -> Save project...