We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.2.0
Windows
Win11
No response
SV07+
Observe dramatic difference in sliced wall speed on the color map
Sparse infill is set to 20mm: The outer wall speed is 200mm/s according to the colormap
Sparse infill set to 30 mm/s: The outer wall speed is about 70mm/s, except a layer that has a bridge!
Wall speed should not be influenced by infill speed settings.
XYZ.zip
The text was updated successfully, but these errors were encountered:
This should be related to the min layer time.
There are issue closed by timeout #4191 which points to the non-obviousness of that setting.
There another PR #5148 which addresses the same issue.
Sorry, something went wrong.
Correct answer. I tentatively suspected something like this, but it didn't occur to me (never printed that fast before).
Layer time can be seen here:
The setting is in filament options:
The settings is perfectly justified and below there are options to control its behavior.
No branches or pull requests
Is there an existing issue for this problem?
OrcaSlicer Version
2.2.0
Operating System (OS)
Windows
OS Version
Win11
Additional system information
No response
Printer
SV07+
How to reproduce
Observe dramatic difference in sliced wall speed on the color map
Actual results
Sparse infill is set to 20mm:
The outer wall speed is 200mm/s according to the colormap
Sparse infill set to 30 mm/s:
The outer wall speed is about 70mm/s, except a layer that has a bridge!
Expected results
Wall speed should not be influenced by infill speed settings.
Project file & Debug log uploads
XYZ.zip
Checklist of files to include
Anything else?
No response
The text was updated successfully, but these errors were encountered: