The error appeared today, does anyone know what to do with it? I can’t slice or export or print anything.
1 Like
Hmm. The errors it’s showing bottom right indicate it’s a very complex model with over a million triangles.
You might try to Right Click the model and choose Fix model. If that doesn’t handle it you may have no choice but to Simplify the model (same way).
That will reduce the number of triangles. It will also lose a bit of detail, but honestly I doubt you’ll see it unless you stick your eyeball half an inch away. It’s adjustable so you may have to play a little.
There are several 3rd party tools to help redefine the model with minimal loss like MeshMixer but they can be … tricky to use (insert Meme of man beating bloody head on desk) … 
Might try the tools you have handy, but do a Fix first.
3 Likes
I don’t mean to bump this month old thread but I have this exact same issue - no matter what model I use, I get a Serializing NaN error, even after right click > fix. Did you every find a fix?
Edit - I figured it out. I knew that NaN was a Javascript thing, so I went digging through the configuration folder. I backed up my slicer profiles, found in
{harddrive}/users/{user}/AppData/Roaming/BambuStudio/user/{random numbers}/process
Then I unistalled Bambu Studio, deleted the entire BambuStudio folder, then reinstalled. I noticed that when unistalling the latest stable version, there is no option for “delete user data”, but the public beta v1.06.00.65 does have a “delete user data” option when unistalling. Checking that box when unistalling is the same as deleting this folder manually in the stable version.
After Bambu Studio is reinstalled, File>Import>Import Configs is where you can import your backed up slicer profiles! And, fixed!!
3 Likes
Well done! Thanks so much for sharing this, I’m sure anyone on here will give you a pass on the necro thread thing, I sure do.
This is exactly what is needed on this board. Sometimes people will post a problem, get lots of answers & suggestions and not bother reporting back.
Hmmm. Kinda like the OP, eh? LOL
Cheers!
Hi All,
I too can generate this error. Following above procedure did not work, however when starting with a new model, no settings changed, Slices fine.
Then, back to my original project, I had a custom filament sequence order. Once I change this, bang, Sequence NaN error. 
2 Likes
In Bambu Studio Windows Version (1.9.3.50) I am also seeing the Serializing NaN error message when I attempt to slice my model.
I did notice it was only with models where I changed the filament sequence for either or both the First layer and Other layers in the plate setting the error would appear. If I left filament sequences to automatic it would slice without any errors.
If you notice the Layer is set to 2 to some very large number.
If you change this option to Layer 2 to End the 3D part will slice without the error.
[I tried to attach some pictures but bambu will not allow me.]
5 Likes
I can recreate this problem by customising the ‘other layers filament sequence’ option. bit annoying but for now i set it to Auto until this (clear) bug gets sorted.
1 Like
I had the same problem. For some reason it was changed from auto. As soon as i switched it back it sliced no problems.
1 Like
A year later, this bug is still there.
This was the solution to my nan issue, thankyou.
The problem i was trying to solve when i ran into this issue was different though. I was trying to get an embedded group of parts aka text to slice first so their walls were the same colour as the text and not of the parent part. The text and parent share the same walls but the parent walls prioritize over the text ruining the text. Sigh 
“other layers filament sequence” set to AUTO also worked for me
I drug the model off the plate and sliced plate then set model back in the center of plate and sliced all that worked for me
The error is something to do with the file code. Simple fix that worked for me.
Export the model as an STL. Then close Bambu or orca. Now open the slicer and start new project. Now simply import your STL that you exported, and it should be fixed.
alos was the solution for me! Thanks for sharing
This error still remains , and the same thing happens if i change Sequence order. dec. 2024