Update to last orca version #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
) * Added SBS to filament_info.json * Added SBS to Print.cpp * added SBS to PrintConfig.cpp * Added SBS to BBL * Added SBS Template and also specified SBS as type in fdm_filament_sbs.json * Updated settings for SBS in filament_sbs_template.json * Applied SBS settings to fdm_filament_sbs.json * added settings to Generic SBS @base.json --------- Co-authored-by: Duan Gauche <[email protected]> Co-authored-by: SoftFever <[email protected]>
This reverts commit b83e16d. Found regressions like auto orientation didn't work anymore after this change, revert it
* Improvements in Inner Outer Inner wall ordering logic * Updated to BFS algorithm, made ordering more robust and corrected edge cases * Doc updates * Refinements in perimeter sorting * Removal of touch threshold and code debugging to improve sequencing * Code cleanup * Code refinements on perimeter distance thresholds * Extend perimeter re-ordering to more than inset index 2, to reduce travel moves when printing neighbouring features * Refinements to IOI perimeter re-ordering algorithm to improve travel scenarios where multiple external perimeters are contained in the same island. * Documentation updates * Removed unnecessary code * Removed bespoke to_points function and replaced with ExtrusionLine member already present. Removed squaredDistance and replaced with Eigen library call. * Refactor code to move distancing functions to the multipoint class. Renamed for more clarity on their purpose.
The prime logic is mainly bollowed from Prusa XL 5T
* Update Wiki * Wiki updates
* Fix linux deps debug build * Use the same DL_CACHE for release build when building debug version of deps on Linux. This prevents downloading the same source packages twice, and avoid downloading again after deleting the build dir. * Fix debug build * Fix warnings "loop variable creates a copy from type" and "loop variable binds to a temporary constructed from type"
* Fix build with CGAL 5.6 Surface_mesh iterators no longer return references, so it's necessary to use const references or copies when iterating. This was previously merged in #3045 but isn't references in the current main branch anymore. No idea where why it is gone, but the issue still persists thus the patch should still be added.
* Artillery proflies update
…ity (#6468) * Gap fill tool tip clarification * Gap fill text and parameter visibility update
* Fix crash due to the wrong window get returned in `PointCtrl` (#6261). `getWindow()` must return the control itself, not its child control; otherwise the child control will be destroyed twice when the tab container is destroyed. * Fix another crash on Linux caused by unused undo button
Fix "Open Containing Folder" on Linux (#6449)
* Overhang tooltips updates
* Wiki home page fix links and readme update to link to wiki * Update README.md * Fixed developer reference links * Update linkage from slicer settings to Wiki for layer height, line width and seam settings * adaptive PA documentation * Update adaptive-pressure-advance.md * updated screenshots * formatting * Update adaptive-pressure-advance.md * Update adaptive-pressure-advance.md * Update adaptive-pressure-advance.md * Include adaptive PA link
* update flow rate calibration tests * more tweaks * add YOLO linear flow rate calibration * update name * revert line_width changes * Make it 2mm thick and change some text * Update YOLO test: Normal YOLO for 0.01 step Perfectionist YOLO for 0.005 step * add space
Removed unused variables
Incorrect mmu flush sentences corrected. Still might not be 100% accurate, but better this way
* Update FlyingBear S1 0.4 nozzle.json * Update 0.16mm Optimal @FlyingBear Reborn3.json * Update 0.16mm Optimal @FlyingBear S1.json * Update fdm_process_common.json * Update fdm_klipper_common.json * Update fdm_machine_common.json * Update fdm_klipper_common.json * Update fdm_machine_common.json * Update fdm_process_common.json * Update fdm_process_common_S1.json fix some parameters * Update fdm_process_common.json * Update FlyingBear S1 0.4 nozzle.json * Update 0.08mm Extra Fine @FlyingBear S1.json * Update 0.12mm Fine @FlyingBear S1.json * Update 0.16mm Optimal @FlyingBear S1.json * Update 0.20mm Standard @FlyingBear S1.json * Update 0.24mm Draft @FlyingBear S1.json * Update 0.08mm Extra Fine @FlyingBear Reborn3.json * Update 0.12mm Fine @FlyingBear Reborn3.json * Update 0.16mm Optimal @FlyingBear Reborn3.json * Update 0.20mm Standard @FlyingBear Reborn3.json * Update 0.24mm Draft @FlyingBear Reborn3.json * Update FlyingBear S1 0.4 nozzle.json
… be changed after parsing get_last_z_from_gcode
…th wipe tower extrusions. (#6980) … # Description This update, along with #6934, resolves the remaining issues with the wipe tower. The GCode class will no longer maintain its own Z height information (m_nominal_z). Instead, it will utilize the Z height from GCodeWriter's m_pos. This approach is less error-prone. This PR also fixes #6755. It also enforce "Enable Filament ramming" option @igiannakas It should fix the wipe tower crashing issue # Screenshots/Recordings/Graphs <!-- > Please attach relevant screenshots to showcase the UI changes. > Please attach images that can help explain the changes. --> ## Tests <!-- > Please describe the tests that you have conducted to verify the changes made in this PR. -->
Makes situations like #6098 less confusing. Old:  New: 
# Description This PR aims to solve an exception when using OrcaSlicer in CLI which caused the --scale option to not work. All credits to @lanewei120 from BambuStudio for pushing it on BS repo. Related commit on BS: bambulab/BambuStudio@2d4655e#diff-2fa194122e892282ec589e51d5f7da65da83ec0488ced4b63930345d1273a353R3797 Related issue on BS: bambulab/BambuStudio#4628 Related issue on Orca: #6454 fixes #6454 ## Tests ``` ./orca-slicer.exe --scale 2 --slice 1 --allow-newer-file test_model.stl --debug 5 ``` The command above works again and scale the model then slice the scaled model. Before, the scale would not complete.
# Simple visual change Currently, the grid has 3 round corners and 1 sharp corner. It seems like bambu lab hard coded this specifically to fit their bed model. As a non-bambu user, I dont like how the corners look.   Another point I'd like to bring up is that rounded corners do not match the boundary detection box. ## Tests Tested locally on windows and macos.
Porting from Prusa exporting negative parts. Before:  After: 
Resolves #5932 **The following changes made are made to all V-Core 4 versions** - Improved cover's quality  - Added RatRig's PunkFil ABS, PETG, and PETG CF filaments - Added PETG-CF10 filament type & RatRig to filament vendors - Increased max z speed to 200 from 50 and max acceleration travel to 10,000 from 9,000 - Enabled wipe and z hop, as well as, increased retract before wipe to 70% from 0% - Improved layer change G-Code - Fixed pause G-Code - Added extruder clearance parameters *Almost all of these changes come from @nameisCruzCruz in #5932
- add filament Breakaway - add preheat configs - fix `prime_volume`
This PR moves the code around without any functional changes, so that all code related to supports now placed at the same location & structure as BambuStudio. This makes merging updates from BambuStudio much easier in the future.
# Description The idea behind this PR is to make it easier for the users to tweak filament setting overrides i.e. reduce number of times users have to switch between the printer and filament settings to compare the values. # Screenshots/Recordings/Graphs     ## Tests I've done some manual testing to confirm: * Override setting with the same value as extruder is still shown as a change. * Resetting unsaved override setting back to original value still works as expected. * Override settings are shown correctly on the next load after a save. * Extruder settings changes are reflected on Settings Overrides page. ## Other I have discovered a strange behaviour between `Filament Settings` and `Printer Settings` windows. On a fresh load of application opening `Filament Settings` window, navigating to `Settings Overrides` tab and then closing the window results in `Filament` tab being opened the next time `Filament Settings` window is opened. But if you open `Printer settings` window, navigate to `Extruder` or `Motion ability` tabs then the application changes the behaviour to open the last visited tab by the user for both of the windows. I'm mentioning this because when this happens the flow of events in the application changes and causes my change to break until the user changes a tab. As far as I can tell for some reason ConfigOptionsGroup's `reload_config` method is starting to get called (second time?) after TabFilament's `update_filament_overrides_page` method which wipes out the values set by me. I'm not sure which is the correct behaviour, so I left that for a discussion here. If last visited tab is the correct behaviour, then I would need help to figure out how to fix this problem.
…a_dir was not used (#7049) # Description fixed #6987 # Screenshots/Recordings/Graphs <!-- > Please attach relevant screenshots to showcase the UI changes. > Please attach images that can help explain the changes. --> ## Tests <!-- > Please describe the tests that you have conducted to verify the changes made in this PR. -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.