-
-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
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
3.0.0 Release #1868
Comments
3.0.0 ReleaseSHOWCASE TODO 🗣 Join our community:F3D Community is welcoming to users and developers alike! ❤️ Sponsor F3D:F3D is looking for sponsors! 🤸 Armature Display SupportYou can now display armature from glTF files in F3D! 📂 Open file dialog🖥️ Interactive ConsoleTOWRITE 📝 Complete changelogFor F3D users:
For libf3d users:
For F3D packagers:
For F3D plugin developpers:
|
F3D 3.0.0 Migration GuideDeprecation removalFirst make sure any deprecated CLI options, API or options are not used when using F3D 2.5.1. For F3D usersCLI Options changes
Add a
The short option
It is not supported to load only the geometry using
The way files are loaded in F3D has been completely reworked and is now way more flexible. Multiple rendering backends are available,
Other changes
Pressing
The If needed you can add a interaction bind for these commands in your configuration file.
There is no headless binary anymore, just use the standard binary with the For libf3d usersAPI changes
The Code using v2.5.1 should be able to rely on the variant API however we recommend using the struct API for better integration in IDE or the string API for flexibility. eg:
Should now be either: opt.render.show_edges = true; or opt.setAsString("render.show_edges", "true");
Engine creation has been completely reworked and now requires the usage of dedicated static creation method, eg:
Should now be:
The
Should now be:
Loading multiple files is supported by the
Should be:
C++17 is now required to use the libf3d and If your compiler does not support C++17, please use F3D 2.5.1 until it does. Options renaming
Many options are now |
3.0.0-RC1 testing: MacOS arm tested and some issues found. TODO MacOS x86_64 Issues: MacOS default window size is small with retina display -> not an issue |
Release notes update:
|
3.0.0-RC2 testing: MacOS silicon tested and no issues found. Issues: Commands from console issues: #1899
Windows installer still not fixed: f3d-app/f3d-superbuild#228 |
Before release:
git fetch origin --tags --force
Release Split :
master
branch intorelease
: release...masterRelease Candidates :
v3.0.0-RC4
version change in https://github.com/f3d-app/f3dCMakeLists.txt
andpyproject.toml
in therelease
branchgit tag v3.0.0-RC4 -m v3.0.0-RC4
v3.0.0-RC4
F3D version, superbuildmain
branch and prerelease publishtrue
release
branch, copy this paragraph and incrementN
Release :
v3.0.0
version change in https://github.com/f3d-app/f3dCMakeLists.txt
,pyproject.toml
and the multipledoxygen\conf.py
in therelease
branchv3.0.0
and push it to https://github.com/f3d-app/f3d:git tag v3.0.0 -m v3.0.0
3.0.0
in https://github.com/f3d-app/f3d-superbuildversions.cmake
in themain
branchv3.0.0
and push it to https://github.com/f3d-app/f3d-superbuild:git tag v3.0.0 -m v3.0.0
v3.0.0
F3D version,v3.0.0
sb version and prerelease publish truedoc
doc/dev/ROADMAPS_AND_RELEASES.md
for next release.github/ISSUE_TEMPLATE/new_release.md
in https://github.com/f3d-app/f3d if neededLinux testing protocol:
f3d testing/data/cow.vtp
-> check render, orientation, press R and check raytracingf3d testing/data/f3d.stp
-> check render, orientationf3d /path/to/any/new/file.format
-> check renderrm -rf ~/.cache/thumbnails
pcmanfm
(or another supported file manager)cd examples/libf3d && mkdir build && cd build && cmake ../ && make
./cpp/check-engine/check-engine
./cpp/render-interact/render-interact ../../../testing/data/cow.vtp
macOS testing protocol:
Windows testing protocol:
cd examples\libf3d && mkdir build && cd build && cmake ../ && cmake --build . --config Release
.\cpp\check-engine\Release\check-engine
.\cpp\render-interact\Release\render-interact ..\..\..\testing\data\cow.vtp
Python testing protocol:
The text was updated successfully, but these errors were encountered: