#Adaptive Layer Height Not Working?
1 messages · Page 1 of 1 (latest)
you need to click on the blue line on the right and drag you mouswe on it
yeah that makes them change, but when I click "Adaptive" there it resets it to pure white like it is in the picture
it's supposed to become red and green automatically, I haven't ever had to manually do it
which version of orca
when you click on the adaptive button it works
are you clicking on this button
yeah that's how you do it automatically
it just resets it to white like the reset button do
I wish mine were too
did you move the slider to a new value?
you can do the buttons or the right hand slider not both
I know, I only did that to illustrate that the "Adaptive" button resets everything to white instead of working as intended
post your 3mf file
ok I made a new project and it worked for a cylinder, I had closed the program and made a new project already and it didn't fix it. Let me see if it is just working now
for no reason that I am aware of >.>.>.>.> computers are fun
nope okay this is weird
I added a cynlinder primitive and it was able to do the adaptive layer height, but once I loaded in my STLs it reset and now doesn't work again
post the 3mf file ill have a look
you can't open the adaptive layer height menu unless you have an object selected, and you have to do them individually
wait lms what that does
yeah I selected each object individually through thta menu and the same thing happened
as soon as I selected the cylinder and clicked "Adaptive" it turned from red to all white
ok added one model individually and it did it
but once I add the second one and click Adaptive nothing happens, and when I go back to the original added model that successfully was adaptive layer height sliced, it now resets it back to white
when I click the "Adaptive" button
I guess I will just have to make a separate project file for each object lol
i can use your file ok,, BBS
all 3 with varible layer height , have you sliced the plate to see if its ok
how can I tell if it is sliced in adaptive layer height based on the sliced plate?
changes the sliver view to layer height
only the initial object is adaptive, and only remains so as long as I do not try to "Adaptive" button it again, because that would make it reset to white and refuse to be adaptive'd again
are you using windows linux etc?
Windows 11
it's weird because I haven't had trouble with it before. I just finished doing a calilantern thing so maybe that messed it up somehow but idk how
its very odd just tried it on my other pc works on that 2 but they are both win 10
yeah I bugged my stuff out bad this time I guess
its doing it to me now but dont know why
if you open the project and do variable layer height it works o, but then if you click on one of the parts again it stops working correctly
@faint comet can you replicate this undisclosed software feature
down load the project above set varibal e layer height for each object , "slice " then go back and try to edit the height
Well I can tell you that it is working fine when I load primitives into the latest nightly. Let me check the project...
Same for the project, works good in v2.3.1-alpha/nightly
so if you go back and click on one of the parts does it not go white ? and can you still add the variable height
@faint comet hit the adaptive button, then it all fails
I'm sorry it is happening to you too, but it is good to know that it's not just me being stupid
Yep, did exactly that and it worked good. Let me see if I can get a screen capture video.
by the way what did you use to capture the video
It's a system utility built-in to Linux Ubuntu 25.04, don't think it even has a name.
im on windows
anyone have any idea what I can do to fix this?
did you watch the video above?
yes and I just watched it again, and here's why it doesn't help; He's on Linux, and his program is functioning fine. This almost definitely means that the bug is restricted to Windows, the bug which you were able to confirm exists on your Windows machine. I am likewise (and have always been) able to manually adjust the layer lines using the bar thing on the right of the screen, but that isn't related to my problem in any way. When I click "Adaptive" it resets the whole object to default instead of applying adaptive layer height
This bug affects every project that has more than one object
including brand new projects
and, like, that video doesn't offer any solutions, even if he were on a Windows machine himself 🙁
I hate it when I mess things up and I have no idea what I did or how I did it
well, I take that back, sometimes in certain situations that can be a lot of fun, but not this time lol
threw science at the wall to see what stuck, un/reinstalled Orca, the bug was nice and gone until I copied my backed-up profiles and then the problem happens again. Grasping for straws here, but are my acceleration settings being messed up to blame for this?
the error it gives is weird considering the limits I have in place
I humbly offer my entire profile folder lol
im on a windows pc running the alpa version
so far so good
i can also go back in and modify the layers
It's true, I don't have a solution to this (I never use adaptive layer heights), which is why I really didn't get involved from the start. I was just confirming for Moth that it was working good for me. Let me see if it works on my Windows 10 PC as well, so then we can at least narrow that down further.
im on win 10 with Alpha night build at the moment
That shouldn't have anythig to do with the layer heights, but I can tell you that error is misleading because of the feature label. The setting Max acceleration for extruding does not refer to the accel of the extrud_er_, but rather to the accel of the X/Y axes during moves that including extrud_ing_. It's really very poor wording, but the devil is in the details. You will need to set that at or higher than the accels in your Process profile, or reduce those to be less than this one.
thank you for the help again ya'll, I'm still on 2.3.0 if that matters
It might. I would try 2.3.1-Alpha latest nightly and see what happens.
i can try the 2.3.0 later when im on that PC
You can certainly do that, just have to install them in different directories.
I think at one point I had 5 different versions of Orca all installed simultaneously.
I experience the same thing with 2.3.1 nightly
I saw there was a profile validator in the download page, maybe that is worth a check
ahh that is only more error messages
all's well until the profiles are loaded
you mean your profiles?
yeah the ones I zipped and uploaded
I am not sure of the procedure but I copied that from %appdata%/Orcaslicer/ (C:\Users\rabro\AppData\Roaming\OrcaSlicer)
i then had to copy the folders inside 893671622 over/into the default profiles in order to get it to load them
send me a 3mf file might be easier
You are using a Bambu Lab account to sink your profiles, huh?
that doesnt bring in your printer so it could be your profile is corrupt
That would make sense why the original issue isn't appearing until the profile is imported.
how can I Noah's ark my profile to get the proper settings out? My brain is corrupt 🫨
I was trying to figure out the account thing, I must have set that up immediately after installing Orca because I don't remember doing it through Bambu but clearly I did so
just swap your printer for one out of orca
like I should delete my current printer and get the default printer profile that OpenNept4une gives and reset my settings to that? I would like to transfer as much as I can if possible in the process
this is the default ON4 has provided
Did I mess up a setting somewhere, or is this just a product of entropy and it just corrupted because that's how computers are?
its possible the file got messed up between versions we have seen the odd file go a bit strange
with your elegoo file above
that is good to see that it works right on yours. Is there any way to copy the printer profile settings over? I can do it manually no problem, just want to see if there are other options first lol
i would do it manually as you may end up corrupting the file again
okay it is something to do with my acceleration values because it was working until I messed with them
i doubt it , but stranger things have happened
just found the "fix." If the "Adaptive" button acts like the "Reset" button, all one has to do is switch to a different printer in that dropdown box and then switch back to the desired profile. Then, the "Adaptive" button works as expected
thats why MxBrnr did the video to show you the proceedure
can we call this fixed now?
It is clear to me that we are not seeing the same thing when we watch that video. His video showed him manually adjusting the layer height using the right-most weird adaptive bar graph slider, slicing it, and then checking to see that the manually adjusted adaptive layers he set were slicing correctly. My "fix" has nothing to do with that, and it is in airquotes because at best it is a bandage. I just watched his video again, and he does not experience the "Adaptive" button acting like the "Reset" button, which completely invalidates the video anyways
So, do with it what you like? I've been trying to get the problem figured out while being told how to fix or do something completely different
I am just glad that I figured out a way to get around this glaring bug that should be addressed
i do the adjustment the same way as Mxbrnr, but i just tried it how you discribed and that works too
I was *always able to manually adjust the layer height using the thing that I feel unnecessarily needs to be pointed out by these big red arrows. That was never a problem
and they would always make it through the final slice
my problem is that the adaptive button would reset that meter on the right to pure white instead of doing adaptive layer heights
now that I figured out how to work it, this is what that cone should look like when I click the Adaptive button
without the fix, clicking the Adaptive button turns it back to default like so
so I am forced to toggle printers in order to get around this bug
i can only get it back to white if i hit the reset button
hitting the "adative " button gives me this
hitting "smooth" once gives me this
if i hit "adaptive "again
"reset" this
yeah it's really weird, I am totally clueless as to why mine is different. It's a fresh install minus the profiles, I deleted its folder in Roaming before installing the nightly
sorry about being gruff, I've been having a lot of issues with that lately but I am actively working on it
just tried multiple parts just incase that made a difference, but was ok
In my video, the only reason I adjusted layers with the slider was to show that changes were made, so you could see that when I hit the adaptive button it reverted those changes back to what the slicer automatically chooses. At no point in my testing - in or out of the video - did hitting the adapt button ever turn everything all white (or any other solid color).
I'VE GOT IT!!! Ladies and gentlemen, we have a bug!
After clicking Adaptive the first time, changing any setting in the Machine, Filament, or Process profiles instantly breaks the Adaptive button (even if the changed setting was immediately changed back before clicking on Adaptive for the second time). Here is a video from Windows 10 using the OrcaSlicer v2.3.1-alpha release:
I DO get this issue with the latest Nightly version on my Linux system, but on both systems ONLY with the project 3MF provided by Goobtacular. If I load a new project with my own models into my own machine, everything works as intended. Seems there is either something corrupted, or one of the model files or a setting is forcing the bug. More testing is needed to narrow it down further, and I will try to work on that later today.
@remote schooner I used OBS Studio for the capture (set output FPS to 10 and format to MP4). Think I will switch to using this on my Linux system too since it works really well and keeps file sizes small (bonus: it's free and open-source).
I totally missed the update here, sorry about that! I'm still just dealing with the problem by changing printers and making adaptive layers be the first thing I do after changing
So are you still getting the issue even with other models?
Yes, it's universal