Nope!: I think I found a Bambu Slicer issue with when using small layer height.
Apparently it’ll take 68 years to print this really cool bunny…
BBS Beta Issue StarryRabbit.3mf (9.9 MB)
I had no problem printing one with the creator’s defaults, but it clearly didn’t like it when I lowered the layer height to 0.08. .4mm HF Nozzles.
Need to get to work… but… if anyone has any ideas.
It’s your Polymaker HT-PLA filament profile, specifically for the HF type nozzle. The Flow Ratio and Max volumetric speed settings are both “N/A” instead of numbers. Copy those two settings over from the standard nozzle type and the primary issue is fixed.
Doesn’t appear to be directly related to the beta version, unless that’s what messed up the filament profile in the first place. I tested on an older 2.5.x version.
This could still probably be more efficient if the colors didn’t go through all the way like that and mess up the infill… not sure why it is doing that, offhand, and didn’t play with it. Also… that’s a lot of filaments… 
HTH,
-Max
PS. How the heck was this painted with that pattern originally? No trace of the surface design is left if painting is removed. Interesting! (That does “fix” the infill.)
I suspect that if you right click and split to parts, it will show each individual pieces - it makes it much easier to assign colours, but the internal geometry does get weird, as each part will have its own walls
Nerp, tried that… it’s just one mesh, no parts. At least the model that’s in the project. Maybe copy/pasted or some other way it lost the parts along the way somewhere. 
-M
Thank you folks! I’ll update the profile and get back to you. (At work, so this will later in the day…)
I didn’t consider the HT-PLA as the one thing I changed… duh.
24855 days, 3 hours, 14 minutes is 100010001000100010001000100010 in Binary.
That looks like a code bug number to me…
It’s likely the time value is actually calculated to maximum positive 32-bit signed integer value, which is 7FFF FFFF or 2,147,483,647 seconds, which is 24855:03:14:07 (DD:HH:MM:SS).
The core issue is that parsing “N/A” into a numeric value didn’t cause any error or warning. Instead defaulting to something invalid, like zero or negative or NaN/Inf.
-Max
Ah. Take my number, multiply by 60 and add 7. I did Minutes.
I meant to add that you’re right about that being a “code bug number,” of course. Not sure I’ve seen that exact term used before… but it works! 
-M
I just invented the term - Code Bug Number: A unexpected number who’s value is suspiciously repetitious when converted to binary.
