Wiki 13: Layer time variability + Minor Improvements (#10677)

* Layer time Variability

Co-Authored-By: dewi-ny-je <2866139+dewi-ny-je@users.noreply.github.com>

* Layer time Variability ++

Co-Authored-By: dewi-ny-je <2866139+dewi-ny-je@users.noreply.github.com>

* Infill gcode analysis tool

* Infill calculator project

* 2 Sigma

Co-Authored-By: dewi-ny-je <2866139+dewi-ny-je@users.noreply.github.com>

* Layer Time Variability improved calculation, grouping % and New names

Co-Authored-By: dewi-ny-je <2866139+dewi-ny-je@users.noreply.github.com>

* Fix Applies to lines

* Reorder, icons and descriptions

* #10687 comment

* Update phishing site reporting instructions in README

README now advises users to report malicious sites using both Google Safe Browsing and Microsoft Security Intelligence, improving community security guidance.

* Ziped analysis gcodes

* Klipper estimator + 3mf klipperized

* Klipper estimator Corrected

* Reformat MD generator

* extra-solid-infill.gif Size Optimized

* Analysis Refactor

* cleaned outliers

* imagefix

* Images with accurate values

* Project specific Machine, Material and Process

* Notes

* Update extra-solid-infill.gif

* Update profiles images and fix using same name

* Zipped analysis files

* Add note on Avoid Crossing Walls and Timelapse mode

Co-Authored-By: Rodrigo <162915171+RF47@users.noreply.github.com>

* Update VS build instructions

Co-Authored-By: Anson Liu <546458+ansonl@users.noreply.github.com>

* Added IPThreat report links in README

* DEFA[.]NG

Co-Authored-By: Nanashi <53353250+NanashiTheNameless@users.noreply.github.com>

---------

Co-authored-by: dewi-ny-je <2866139+dewi-ny-je@users.noreply.github.com>
Co-authored-by: Rodrigo <162915171+RF47@users.noreply.github.com>
Co-authored-by: Anson Liu <546458+ansonl@users.noreply.github.com>
Co-authored-by: Nanashi <53353250+NanashiTheNameless@users.noreply.github.com>
This commit is contained in:
Ian Bassi
2025-10-19 12:04:16 -03:00
committed by GitHub
parent c79e89d30b
commit a754387566
16 changed files with 312 additions and 192 deletions

View File

@@ -84,19 +84,34 @@ How to building with Visual Studio 2022 on Windows 64-bit.
```
> [!NOTE]
> The build process will take a long time depending on your system but even with high-end hardware it can take up to 40 minutes.
> [!TIP]
> If you encounter issues, you can try to uninstall ZLIB from your Vcpkg library.
3. If successful, you will find the VS 2022 solution file in:
3. If successful, you will find the Visual Studio solution file in:
```shell
build\OrcaSlicer.sln
```
4. Open the solution in Visual Studio, set the build configuration to `Release` and run the `Local Windows Debugger`.
![compile_vs2022_local_debugger](https://github.com/SoftFever/OrcaSlicer/blob/main/doc/images/develop/compile_vs2022_local_debugger.png?raw=true)
5. Your resulting executable will be located in:
```shell
\build\src\Release\orca-slicer.exe
```
> [!NOTE]
> The first time you build a branch, it will take a long time.
> Changes to .cpp files are quickly compiled.
> Changes to .hpp files take longer, depending on what you change.
> If you switch back and forth between branches, it also takes a long time to rebuild, even if you haven't made any changes.
> [!IMPORTANT]
> Make sure that CMake version 3.31.x is actually being used. Run `cmake --version` and verify it returns a **3.31.x** version.
> If you see an older version (e.g. 3.29), it's likely due to another copy in your system's PATH (e.g. from Strawberry Perl).
> You can run where cmake to check the active paths and rearrange your **System Environment Variables** > PATH, ensuring the correct CMake (e.g. C:\Program Files\CMake\bin) appears before others like C:\Strawberry\c\bin.
> [!NOTE]
> [!TIP]
> If the build fails, try deleting the `build/` and `deps/build/` directories to clear any cached build data. Rebuilding after a clean-up is usually sufficient to resolve most issues.
## MacOS 64-bit

View File

@@ -139,9 +139,9 @@ The following sample JSON file shows how to create a new generic filament profil
> When developing profiles, you may notice that changes aren't reflected in OrcaSlicer after editing profile files. This happens because OrcaSlicer caches profiles in the system folder.
> To force OrcaSlicer to load your updated profiles:
> 1. **Access the configuration folder**: Go to **Help** → **Show Configuration Folder**
> ![Help menu](https://github.com/SoftFever/OrcaSlicer/blob/main/doc/images/develop/go-to-configuration-folder.jpeg?raw=true)
> ![go-to-configuration-folder](https://github.com/SoftFever/OrcaSlicer/blob/main/doc/images/develop/go-to-configuration-folder.png?raw=true)
> 2. **Clear the cache**: Delete the `system` folder to remove cached profiles
> ![Delete system folder](https://github.com/SoftFever/OrcaSlicer/blob/main/doc/images/develop/profile-delete-system-folder.jpeg?raw=true)
> ![profile-delete-system-folder](https://github.com/SoftFever/OrcaSlicer/blob/main/doc/images/develop/profile-delete-system-folder.png?raw=true)
> 3. **Restart OrcaSlicer**: Launch the application to load your updated profiles
> This process forces OrcaSlicer to update its profile cache from the source files in the `resources/profiles/` directory.