I know there’s multiple cases of this but I can’t get it work no matter what I try!
Laptop has AMD Ryzen 7 and 8gb Ram. Radeon graphics card.
Any large file I slice (not necessarily complex I me a physically large) will not Slice.
I’ve tried to simplify models to silly low numbers. No change. I’ve set affinity on laptop to a couple cores, no change. Updated everything. Repaired models in Bambu and mesh mixer. Exported as different files, obj, 3mf stl etc. No change.
The only thing that works is making it physically smaller! Ie scale to 80% and it will slice!
If that doesn’t work, then, and only then, uninstall Bambu Studio, roll back to a previous release that you know worked for you, and start upgrading forward. Just like using DDU to uninstall a driver, Revo Uninstaller is my go-to uninstaller of choice. There are others, but I find that this utility (the free version) does the best and most thorough job of purging registry entries and files. Download Revo Uninstaller Free - Remove unwanted programs easily - you’ll want to uninstall it after because it will sit in your system tray nagging you to purchase the full product. You only need it once.
What sucks about uninstalling Bambu Studio is that you’ll lose all your settings if you perform a pristine install. However, with all the bug reports on Bambu Studio, it’s clear the product is gradually degrading with each release, especially for legacy hardware and software. That’s a long way of saying Bambu is clearly not doing a thorough job of app testing before releasing new versions.
Alternatively, if you’re on older firmware, you can simply try Orca Slicer. But if you’ve upgraded beyond 1.08 for the P1 and X1, or 1.03 for the A series, then you can’t use Orca because you’re in Bambu-Connect jail where Bambu Labs started blocking 3rd party app functionality.
That’s not something I have tried yet the ddu. Main problem being I’m on a laptop and it’s integrated graphics I’m not sure how I’d locate the exact driver. Or can I do an automatic update from Windows or Lenovo?
Video driver installations can be very fickle. I have both AMD and Nvidia cards in various machines and laptops, and as a system builder, I can tell you I waste more time fixing driver issues than any other problems with my systems.
Microsoft would have us believe that all one has to do is click on Windows Update, but that only works well if you have bug-free software. When you have poorly tested software such as open-source platforms like slicers, there is often a lot of vestigial code left over from previous iterations of features. These rarely get fully tested because the development community assumes they are stable and require minimal testing. Most of the time, that’s true, unless there’s a problem like the one you’re experiencing.
I suggest first identifying the video card and driver currently in your setup. For that, the best tool is the free version of TechPowerUp’s GPU-Z. It’s the big daddy of GPU utilities and tells you everything you need to know.
There are two sites dedicated to graphics cards that host nearly every driver from the last several years, so if the current driver is causing issues, download one that’s a full revision older.
Thanks for all your help in this. Appreciate your time.
So I was hunting around the AMD site and tried thier auto update tool only to download it and be told it doesn’t support my driver please manually download. That led me to the how to find your video card name. I followed and I think I ended up with AMD RADEON Lucienne GPU. Does that sound right or do I need to drill down further.
It’s not exactly my idea of fun hunting all this down and doing all this work for my supposedly supported laptop to try and slice a file! Takes long enough for me to slice models as it is haha!
Appreciate your help. If I use your link and find the driver name, I can then use ddu uninstall and reinstall and try it again?
My fear is what happens when bambu studio updates again? Saying that I also tried Orca and had exactly the same crash
Pull the specific driver you want, not whatever Windows Update or AMD’s Adrenalin utility hands you.
AMD official drivers. Be aware they’ll try to steer you into using the Adrenalin app and auto-detect, which is exactly what you’re trying to avoid: Drivers and Support for Processors and Graphics
Avoid auto-installers if you’re chasing a version-specific fix.
AMD Auto-Detect and Adrenalin are convenient, but they take away version control. If auto-detect gives you the same broken behavior, go back to manual installs.
Keep utilities that hijack workflow off your system if you want fewer interrupts.
I skip AMD Adrenalin and NVIDIA GeForce Experience for exactly that reason and stick to driver-only packages.
Bottom line: decide between convenience and control. When you’re debugging, control wins.
I mean, it’s a lot of work. I didn’t plan on becoming a GPU enthusiast and go this deep into things lol. I just want to slice a flipping model to print.
How would I know what driver I need? I have no idea and would just let auto update do its thing. Obviously if someone said use abc123 it will work. Then that’s fine. But it won’t be that easy will it!
Bambu have actually replied asking for dump files and will look into so interesting to see what they say
If you sent them the 3mf that crashes your slicer, post it here too. I’m curious. What you said about it crashing at $x scale, but slicing at ${x*0.80} scale could be a LOT of things.
All I can suggest is to temper your expectations. 3D printing, especially Chinese-made 3D printing is far from the experience we get from our desktop printers. For those who don’t remember early inkjet printers, those sucked equally as much as ink would routinely dry out in the well and become unusable with no diagnostics. Same was true of early laser printers that embedded Adobe Postscript, they worked about as well as today’s slicers, when they worked, they worked well and when they didn’t…? Well…
Unfortunately, the answer usually comes down to trial and error.
There is another way to diagnose the problem but if you don’t like the driver experimental route, you’ll like that even less. But if you want, I can post a LONG tutorial on how to use the event viewer in Windows specific to diagnosing the slicer crashing. While it won’t tell you exactly what is wrong, it “could” help to identify where the failure point is. After that, you can focus on restoring that and only that component.
I can’t upload the 3mf it’s 70mb? There’s a helmet I’ve found on makerworld it also crashes on. Again it’s anything physically big in size. But that one was 2million triangle.
I won’t make you go deep into explanation of a possible fault find yet but appreciate your offer. Let’s see what bambu say
That is a significant data point and it has really piqued my curiosity.
How big is the model itself? I ask because of two things.
Have you tried to export it as GCODE to a file and manually load it onto an SD Card? Note the size of the file. That would tell us how big the GCODE file is for that particular object.
If it crashes on upload, you may be overtasking the MPU. 64MB is a magical number in computer science in that is is on a numeric boundary if memory serves. It could be that we’ve, or you, have discovered an upper limit not previously known in the slicer. Or more likely, the MPU being used in the printer is the limitation.
One experiment is to right-click and use simplify model to reduce the number of vertices. Did you attempt that just to see if the model will load?
So interestingly that was a spiderman helmet! So a full size head size item! It was however over 2m triangles. When I simplified that it did indeed slice fine.
The other item is a large model printed in multiple pieces and the head, similar size to the helmet is what keeps crashing. That is only 400k and I’ve simplified right down to about 100k and it still won’t have it. These are 2 examples but I’ve had more and it’s all big items. Not complex some, just big.
How would I export as gcode if the file won’t slice? Don’t I need to slice first?
