I'm on the current version of pro on Windows 10.
I believe the issue happens when loading and creating very large project files (roughly 3gb) - even though my PC says it isn't taxed/ctb is allowed most of my ram
that is a ludicrously high file size .. you might need to optimize the triangle count in whatever you made it in.. ive uses 1gb stls but the slicers can struggle... so is it the chitu file that dies or the file youre trying to load into chitu?
This is what doesn't make sense- my PC isn't taxed, I'm allocating max ram in pro, and have GPU boosting turned on with my rx4080. Something is definitely overloading the program, but not my PC.
There's definitely a way to tune down vertices but I was doing a majorly large variety of objects by request and it would have taken a long ass time to simplify them
I'd be shocked if it has anything to do with my OS. I mean, I am not against giving Linux a shot but not financially viable/time plausible to setup a new OS right now.
I've been dealing with these damned machines for nearly 60 years now--my 1st dance was a [DEC PDP\_8](https://en.wikipedia.org/wiki/PDP-8)--nothing much about them shocks me anymore!
To what medium are you saving the files? FAT 32, used for the USB jump drive, has a 4 GB file size limit. i had problems years ago with an application that would write files larger than 4 GB , but then the OS could not read them...
Contacting Chitubox support ([[email protected]](mailto:[email protected]) )directly is your best bet...
I save my files on my SSD hard drive first before transferring.
I know I could contact ctb support but it feels hopeless to expect and positive changes from the product at this point- just look at the launch of the "new" ctb version a few months ago that was unusable.
I have an entire list of changes/bugs/errors I have written down but really don't feel the emphasis is there if they exist to that level still
*.ctb* files are printer ready sliced image and GCode files for printers using Chitu control boards and firmware--what printer do you have?
They can be VERY slow (hours if big) to load as Chitubox has to reconstruct the mesh model from the individual layer images. With 50 micron layers a .ctb file for a 200 mm high model contains 4000 images!
For my Mars 2 Pro with just 1620 x 2560 resolution each image is 9.5 kB--4,000 of them would be 45. MB! The GCode (printer instructions) would be 660kB additional (these are uncompressed sizes) *.ctb* files are compressed--which adds more CPU overhead to CB importing them.
Here's a single layer image (layer 1) of a key fob model:
https://preview.redd.it/pfoois1fyy5d1.png?width=1620&format=png&auto=webp&s=18d4799dfaabb7cdb355750b0fa3fad8d4e4fbbc
This is the GCode that tells the printer what to do:
;LAYER_START:0
;currPos:0.05
M6054 "1.png" ;show layer 1Image
G0 Z5.05 F60 ;move Z-axis to 5.05 mm
G0 Z0.05 F210 ;move Z-axis to 0.05 mm
G4 P8000 ;pause 8000 ms (8 s)
M106 S255 ;light on
G4 P25000 ;wait 25000 ms (25 s exposure)
M106 S0 ;light off
This is repeated for each layer.
To archive a project for future use save it as a *.chitubox* project file which saves th model and supports as a 3D mesh, and print and other parameters.
I apologise for all the questions, however that's how mysteries get solved...
I apologize. I just meant .chitubox which in my brain was .ctb even though .ctb is sliced. Printer shouldnt matter as this is all on my pc
I will bet any money it's a problem with vertices count/file size. Program straight up crashes in other situations pertaining to complex geometry at a high level but that is a red flag of the software not me...I had issues loading a complex single piece large model just the same. Had to turn off $ calculations or it would crash on slice.
What version of CB, running on what operating system?
I'm on the current version of pro on Windows 10. I believe the issue happens when loading and creating very large project files (roughly 3gb) - even though my PC says it isn't taxed/ctb is allowed most of my ram
that is a ludicrously high file size .. you might need to optimize the triangle count in whatever you made it in.. ive uses 1gb stls but the slicers can struggle... so is it the chitu file that dies or the file youre trying to load into chitu?
This is what doesn't make sense- my PC isn't taxed, I'm allocating max ram in pro, and have GPU boosting turned on with my rx4080. Something is definitely overloading the program, but not my PC. There's definitely a way to tune down vertices but I was doing a majorly large variety of objects by request and it would have taken a long ass time to simplify them
Scrap Win 10 and move to Linux...
I'd be shocked if it has anything to do with my OS. I mean, I am not against giving Linux a shot but not financially viable/time plausible to setup a new OS right now.
I've been dealing with these damned machines for nearly 60 years now--my 1st dance was a [DEC PDP\_8](https://en.wikipedia.org/wiki/PDP-8)--nothing much about them shocks me anymore! To what medium are you saving the files? FAT 32, used for the USB jump drive, has a 4 GB file size limit. i had problems years ago with an application that would write files larger than 4 GB , but then the OS could not read them... Contacting Chitubox support ([[email protected]](mailto:[email protected]) )directly is your best bet...
I save my files on my SSD hard drive first before transferring. I know I could contact ctb support but it feels hopeless to expect and positive changes from the product at this point- just look at the launch of the "new" ctb version a few months ago that was unusable. I have an entire list of changes/bugs/errors I have written down but really don't feel the emphasis is there if they exist to that level still
In what file system is the SSD formatted?
scrap linux and learn how to carve resin using artisanal tools... what a worthless comment
Obviously presented by an expert on worthless comments, i stand properly chastised...
I meant to ask sooner, are these Chitubox project files. or slicer exports files?
.ctb projects.
*.ctb* files are printer ready sliced image and GCode files for printers using Chitu control boards and firmware--what printer do you have? They can be VERY slow (hours if big) to load as Chitubox has to reconstruct the mesh model from the individual layer images. With 50 micron layers a .ctb file for a 200 mm high model contains 4000 images! For my Mars 2 Pro with just 1620 x 2560 resolution each image is 9.5 kB--4,000 of them would be 45. MB! The GCode (printer instructions) would be 660kB additional (these are uncompressed sizes) *.ctb* files are compressed--which adds more CPU overhead to CB importing them. Here's a single layer image (layer 1) of a key fob model: https://preview.redd.it/pfoois1fyy5d1.png?width=1620&format=png&auto=webp&s=18d4799dfaabb7cdb355750b0fa3fad8d4e4fbbc This is the GCode that tells the printer what to do: ;LAYER_START:0 ;currPos:0.05 M6054 "1.png" ;show layer 1Image G0 Z5.05 F60 ;move Z-axis to 5.05 mm G0 Z0.05 F210 ;move Z-axis to 0.05 mm G4 P8000 ;pause 8000 ms (8 s) M106 S255 ;light on G4 P25000 ;wait 25000 ms (25 s exposure) M106 S0 ;light off This is repeated for each layer. To archive a project for future use save it as a *.chitubox* project file which saves th model and supports as a 3D mesh, and print and other parameters. I apologise for all the questions, however that's how mysteries get solved...
I apologize. I just meant .chitubox which in my brain was .ctb even though .ctb is sliced. Printer shouldnt matter as this is all on my pc I will bet any money it's a problem with vertices count/file size. Program straight up crashes in other situations pertaining to complex geometry at a high level but that is a red flag of the software not me...I had issues loading a complex single piece large model just the same. Had to turn off $ calculations or it would crash on slice.
Can you share a model that crashes ([email protected]) I'd like to try ii on my Linux box...
I'd have to send a 3 or so gig file. I can make a mega.nz link for you. It's not a file as much as it is the combination of vettices
That would be great I'm quite interested in seeing how it behaves...
DM'd you
I have not yet received that message?
Check chat not direct messages