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
bugfix-2.0.x
Yes, and the problem still exists.
Attempting to compile latest Bugfix ( July-13-2021) w/current config, identical settings to Bugfix from July-06-2021.
Configuration.zip
New Bugfix 2.0.9.x (July 13-2021)
Expected to compile as normal
Error during compile.
Copy settings from working config files using current config files. Compile
Marlin Bugfix 2.0.X
Flsun QQS Pro
MKS Nano V3 w/TS35 V2 and TMC2209 Uart
No response
Prusa Slicer
OctoPrint
The text was updated successfully, but these errors were encountered:
This is fixed by #22354 (pending merge)
Sorry, something went wrong.
This is fixed by #22354
Merged.
Please download bugfix-2.0.x to test with the latest code and let us know if you're still having this issue.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
No branches or pull requests
Did you test the latest
bugfix-2.0.x
code?Yes, and the problem still exists.
Bug Description
Attempting to compile latest Bugfix ( July-13-2021) w/current config, identical settings to Bugfix from July-06-2021.
Configuration.zip
Bug Timeline
New Bugfix 2.0.9.x (July 13-2021)
Expected behavior
Expected to compile as normal
Actual behavior
Error during compile.
Steps to Reproduce
Copy settings from working config files using current config files.
Compile
Version of Marlin Firmware
Marlin Bugfix 2.0.X
Printer model
Flsun QQS Pro
Electronics
MKS Nano V3 w/TS35 V2 and TMC2209 Uart
Add-ons
No response
Your Slicer
Prusa Slicer
Host Software
OctoPrint
Additional information & file uploads
No response
The text was updated successfully, but these errors were encountered: