That’s it, at once I thought this would be a great product to brag, promote and show off. Now it’s nothing but a HEADACHE. App constantly crashing (MORE THAT 10 TIMES IN A ROW). DA** filament changing to colors not chosen or selected. I thought this would be a good product but now I am seriously thinking of buy a product that I should not even mention on this forum. But what could I do? I’m at my wit end with this 
I paid for the 3D printer to work, not to wait for it to work. And some other 3D printers are starting to look alot better right now 
I don’t think you will see much tech support in the forums. I’ve had success (all-be-it rather slow success) by e-mailing tech support.
If it is any consolation (and I doubt it is) I’ve only had the app crash once when I ran out of memory (lots of apps running simultaneously) What platform are you running the app on?
I can’t help with the CFS. When I researched my purchase, the CFS is the only thing anyone complained about, so I skipped that option.
Does your printer still crash if you do not use the CFS (i.e. use the single filament side feeder).
I have literally never had a Crash on Creality Print 6. Something on your machine is interfearing.
I have never had the wrong color print. You might be neglecting to match up the colors in the final step when sending the print.
Tip: Communicating in a more polite manner, will get your more responses from the community.
2 Likes
I am running the program on a windows 10, with geforce rtx 32g of ram graphics card with 900GB of memory. So I am running the app and it has crashed here and there, then I would go back in and slice or print. And I could get through it. However this one file keep constantly crashing & I mean CONSTANTLY. I keep the programs up to date, so I am just at a loss because if these problem persist. My plan (business plan) will have to be revised and not with the printer that I WANT to use
Nah no neglecting the match ups because I LITERALLY write them down machines number, slot and color. And it still switches them. At 1st I was running mostly petg & pla, but now I run straight petg and it still switches colors where I don’t want them. After I have written down everything where they are, for example. I use beige as a color for my 4 characters which will be used across them all. But for whatever reason the system change it to grey & keep doing it by the way. How do I know b/c you know the part or prompt before you send it to the printer shows you another look and the assigned colors and it switches the color mint for a skin tone to a grey color. Even after I choose to switch it back it still prints grey. So I have to literally put the actual color in that slot when it was not assign the to begin with 
900GB RAM?!? so you’re not running out of memory 
I have had an occasional model that would cause crashes. Most of the time the app flags the error, but not always. If the app doesn’t flag the error, the crash usually happens mid-print (OUCH!). I have had success re-processing the STL for errors. I use mesh mixer’s “make solid” feature. It is hideous overkill, but it’s free and it works.
Can’t help with the color change thing. It might be helpful to open up the gcode and see if the code is written correctly At least then you’ll know if it is the app or the CFS.
1 Like
I think I am going to pawn this printer and get a bamboo or something else. Another print crash after 2 days & not the app wont even get pass the slicer, it’s just stuck for 30+ minutes now. This is no reliable product
Sorry to hear that. When the K2 works it works well. not getting past the slicer really points to a model issue. Have you tried an alternate slicer? An easy quick check would be to use creaility’s cloud slice. I’m really curious about the model that won’t slice. Did you find anything in the gcode? If you can think of a way to get it to me I’ll give it a try.
Separately, here’s another person with CFS issues similar to yours. You are not alone on CFS issues. K2 plus CFS always prints with first spool no matter how sliced or chosen
There are thousands of people here to help.
But we can’t help if you are incoherent, rude and low on detail.
First thing to consider is “if this is a problem why am I the only one experiencing it?”
Consider that.
Next, grab a nice cup of tea and take 5 minutes to READ THIS → LinuxSilo.net: How To Ask Questions The Smart Way
NOBODY will help you if you continue acting like an over-emotional 3 year old. They’d rather you just go away…
So, read the article, be considerate of our valuable time, and you’ll find a highly skilled group of people who are willing to help.
5 Likes
I could not agree more !!!
2 Likes
Do you know someone with a similar printer that could test run the print for you on a different printer?
I offered, but got no response. Even hunted him down on instagram for a DM, still no reply.
Sorry for the late reply I was pouting like a 3 year old according to some ignorant people here. Thanks for actually asking Gozmon & Jim99Bass instead of assuming my age. I was temporary suspended from replying so that is why it took so long and I don’t often check my Instagram rn. I don’t know anyone that has my same setup. I’m beginning to think I may have to break it down into more parts. But I don’t know why it(the file) would slice before, but now after attempting to slice it just crashes over and over and over and over and over and over and over and over and over and over again. I now figured out how to get pass the filament issue. But the app just constantly crashes.
Right back to being Toxic and Insulting people. Best of luck to you.
2 Likes
My offer to look at the problematic model still stands.
I may have stumbled across something. Does you model have a high polygon count? I just loaded a model with a lot going on. It took 10+ minutes to slice then I could no longer select the object. Is this how yours is crashing? When I restarted I was prompted to install v6.2. I did. This time when I sliced the problem model The software offered me a “Slicing Preview Lite” to avoid lock-up’s. I chose that mode. It still took a long time to slice, but this time it worked and is printing as I type this. Here’s the message I received and accepted:
Grab Print 6.2 There are definitely some bug fixes and improvements in there.
Addendum: I loaded the problem model again This time I tried doing a model fix and simplification when I loaded the model. The slice went much faster.
@gozmon yeah the model has a high polycount, I appreciate the offer to look at the model. The thing is though these things are I.P. (Intellectual Properties) so I’m a bit hesitant to share it. Why? because this will be one of our giveaways that we will be running in a few weeks. Really I do appreciate it b/c you’ve come on here & asked questions to help solve the issues. And not come in on a high horse & lay false swallow claims of perception at my feet. So thanks for that also, what I am going to try are 2 things. One break the model down into more parts, which will low the polycount. 2 download the new update the 6.2 although the 6.1.2 absolutely did not work on my systems. I mean it wouldn’t even get pass the slicer at all on any of the 4 prints. I do have one question can you explain your grey paragraph a bit more?