BUG: File size issue (gcode > around 250Mb)

[MlvPerry]

Hello, I have an issue with gcode files (for 3d printing) larger than approximately 250Mb.
They do not finish transfering to the Snapmaker 2.0 A350, or they crash the display software before starting the print.
I tried with different slicers and different files. For some prints is not possible to further reduce the file size via resolution decrease or print settings optimization...
I see other users have the same or very similar problems, for example here and here.

[scotthsl]

Hi MlvPerry,
Thanks for your feedback!

My colleagues sad this is known Luban issue, they will fix it.

[ITmaze]

If this is the case it's customary to link to the issue in the other tree that you can find what's going on in relation to it being fixed.

…

-- finger painting on glass is an inexact art - apologies for any errors in this scra^Hibble ()/)/)() ..ASCII for Onno..

On Mon., 25 Jan. 2021, 16:36 scotthsl, ***@***.***> wrote: Closed Snapmaker/Snapmaker2-Controller#58 <https://github.com/Snapmaker/Snapmaker2-Controller/issues/58>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/Snapmaker/Snapmaker2-Controller/issues/58#event-4244288653>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF4P4JBTUBG6R5Z6CTM6MOTS3UUQLANCNFSM4WARPMNQ> .

[MlvPerry]

If this is the case it's customary to link to the issue in the other tree that you can find what's going on in relation to it being fixed.

@ITmaze Yes, that sounds like good practice... Sorry, but I have very little experience with GitHub and related protocols, should I just link the issue in the Luban repository? (as a new issue) Or the correct way is a different one? Or, yet, it's better if a collaborator does something about it?
I couldn't find much info online about it, but maybe I'm just using the wrong search terms... (?? https://github.com/marketplace/actions/add-an-issue-link ??)

This problem is currently preventing me from using the Snapmaker 2.0 as a printer alltogether.
Thank you for your help!

[ITmaze]

My comment was directed at the person who closed the issue. The way to create a link is just to paste the URL into a comment. Given that the issue was closed by scotthsl, it would be their responsibility to create the link, not yours, MlvPerry.

…

-- finger painting on glass is an inexact art - apologies for any errors in this scra^Hibble ()/)/)() ..ASCII for Onno..

On Tue., 26 Jan. 2021, 16:41 MlvPerry, ***@***.***> wrote: If this is the case it's customary to link to the issue in the other tree that you can find what's going on in relation to it being fixed. @ITmaze <https://github.com/ITmaze> Yes, that sounds like good practice... Sorry, but I have very little experience with GitHub and related protocols, should I just link the issue in the Luban repository? (as a new issue) Or the correct way is a different one? Or, yet, it's better if a collaborator does something about it? I couldn't find much info online about it, but maybe I'm just using the wrong search terms... (?? https://github.com/marketplace/actions/add-an-issue-link <http://url> ??) This problem is currently preventing me from using the Snapmaker 2.0 as a printer alltogether. Thank you for your help! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/Snapmaker/Snapmaker2-Controller/issues/58#issuecomment-767391510>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF4P4JCN3DVFH3W5OY3ZL4DS3Z53NANCNFSM4WARPMNQ> .

[scotthsl]

@ITmaze Yes, you are right, I am sorry for closing this issue directly before.
I asked my colleague to help to transfer it to luban here.

[MlvPerry]

Please note that the issue is not caused by the slicing software (or, to be precise, all of the slicing softwares I tried cause this same issue). So there is a problem with the Snapmaker software (firmware).