Cura 4.11 update

[Tneptunus 1]

So, I use the cr-10 profile for my anycubic chiron as that is the way I've had the best prints, with a few small adjustments.

When updating from 4.10 to 4.11 it kept all my settings for the profile and I sliced an object saved it to an SD card and put it to print. Normally what happens is it wipes a small line then begins on the brim, what is happening is it will begin to pump filament through as fast as possible, travel on the Y axis, reach the travel limit, then begin travel on the X axis, hit the limit and I do mean HIT the limit and attempt to continue going all the while feeding filament through. I had assumed this was a faulty file so I resliced, saved and tried again. Same thing. Tried a different file, same thing. Closed and reloaded cura, same thing. I then tried a custom chiron profile I had made but wasn't getting quite as good of results as from the cr10 profile and it worked with no issues but the print still wasn't as good as what I'd been getting with the cr10 profile so I ended up rolling back to 4.10. If anyone might know what's going on I'd love to have the update version as I do like the UI more.

[GregValiant 1,489]

Printer definition files contain some setup information about your printer.  Cura uses most of the information to tell itself the minimum and maximum speeds and acceleration, the build plate size, the StartUp G-Code and End G-Code, how many extruders, and most importantly, the firmware flavor.  The CR-10 uses Marlin and the Chiron uses RepRap.

• If you use the CR-10 definition then your firmware flavor might be wrong.  It should be "RepRap (Marlin Sprinter)".
• If things got scrambled (somehow) in the StartUp G-Code the printer could react as you describe.
• If your SD card is corrupt then the printer may not be reading the first part of the G-Code file correctly and will react as you describe.

If you post a screenshot of the "Manage Printers | Machine Settings" window and a "bad" gcode file someone will take a look.

If you format the SD card (FAT32) then that might solve the problem.