ozhawk

I have installed Cura 5 Beta with no issues, but after selecting Lightning Infill for a model, then switching to Spiral or Vase mode I noticed after slicing the Lightning Infill still shows in the Preview Mode. I have attempted to print a "vase" yet due to the preview. This appears to be a bug. Is this a known issue, or a new one? I have uploaded the Preview Mode view of the print.

Looks like Ultimaker has made a BIG mistake with version 4.10, 11 and 12. NONE of these versions work with the AMD processors. I have proven this by installing ver 4.11 on my old HP Intel notebook. But my AMD Ryzen 5 3600 crashes the newer versions when trying to load a file. This means anyone with AMD processers need to move to Prusa Slicers. Looks like these versions were not tested on the AMD processors.

This error keeps appearing each time I reload the program, even after running CCleaner to remove registry entries, there has to be a fault in the software.

I do not hav any drives higher the H mapped, but still have this issue. Also the program does not appear in Win 10 Start Menu or my desktop.

When starting Cura 4.9 I receive the Freezer Python error in main script (traceback unavailable). Ihave added the screen capture of the error, and the program will not load. Appreciate your advice on this.

I tried to install version 4.6.2, and when it was downloaded I noticed the file extension is AMD64, not Win64 as per previous versions. When you run the installer as administrator the attached error message appears, this seems to be possibly related to the file extension not being correctly recognized? Previous versions up to and including 4.6.1 installed successfully and work well, 4.6.1 was a big improvement in time calculation, just wondering why this is happening? Thanks for the help.

I have found since version 3.6, when you send the sliced file to your SD card etc, you cannot overwrite the file. At times I have realized that a part was not correct, and re-sliced the model and re-saved it to my SD card. The issue or bug is that the original file is not overwritten. This means when you start the print, changes made after the first "version" are not picked up by the file. I think it should be a simple code change similar to how MS Windows overwrites the file, with a warning message that your about to overwrite the file. I have used the 4.5.0 beta since its release, and found it to be an improvement over earlier versions, and this code change will save a lot of problems for new users as well. Appreciate any feedback if there is already a way to resolve this.

Thanks for that information, based on your comments, this sounds like its something that Cura generates during the slicing process. I wonder if it can be considered as a "bug". Its more of a nuisance than anything if you want to check a file after it has been sliced and saved.

This one of the GCode files that gives the invalid message, but I'm able to print it with no issues. GhostbatMid.gcode

I'm musing windows 10 Pro.

I have noticed that both version 4.0 and 4.3 give me an invalid file error if I try to load a GCode file previously created using either versions. Is this meant to work this way, or is it bug?