F3D is an open source 3D viewer, fast and minimalist
f3d.app
f3d.app
It would also be cool if it offered conversions between formats (as it clearly demonstrates the ability to take some file and render it, it should be able to reverse that operation in most cases too).
I never knew about the bindings, it may be cool to experiment with some procedurally generated models, or using some form of network model to produce 3D models. I remember from quite some time ago that would procedurally generate star ships [1].
[1] https://blendermarket.com/products/procedural-starship-space...
Large file can take some time but should be loaded at some point, but indeed, no more feedback but the progress bar.
Conversions are hard because you need not only a reader, but a writer too, and they should all be implemented. That being said, I think it would be cool to have another project based on the libf3d trying to go in this direction. It will not be in F3D though.
"It's like <img> or <video> tag for 3D models"
Most of the time I can't control what light my models are shown in, so it was great to have some control of how it was presented.
Install with `pip install f3d` or download our binary release: https://f3d.app/doc/user/INSTALLATION.html
After clicking: When should I use this, when I'm developing 3d printer software and want to preview files or so? Who is this for?
Windows as well supports gltf in many areas.
iOS natively supports USDZ for the last 5-ish years.
The only challenge has been with thumbnails, and it looks like we should explore this: https://github.com/f3d-app/f3d/issues/969#issuecomment-17032...
Because we generate so many assets, our preferred solution would be a "3DAM/3DCMS", which there seem to be a few of now. However, a 3D file manager where we can open multiple viewers / objects from a higher level directory ("open folder as project") would help with our open source collaborations :)
Do not hesitate to reach out on discord or GitHub for help.
EDIT
Trying it from the command line and I see the problem: a message is posted to stderr complaining that the file does not exist, probably because this is an smb path and it (f3d) is doing some weird thing trying to open the path itself instead of going through the default filesystem apis.
Copying the file to the local fs and then opening it with f3d works, so as far as I'm concerned, this is at the very least a bug in that f3d doesn't forward fatal errors to the UI and only posts them to stderr, which is hidden/swallowed by default when opening f3d via the desktop environment or by double-clicking on the .stl file (as no terminal is shown), if not to also mention a bug opening files from smb or network shares or more generally through the gvfs extensions.
Regarding the error, you are correct, we have not implemented a log dialog. We plan to improve that in the future but its not a small work: https://github.com/f3d-app/f3d/issues/29
In my previous (work) life it would've been incredibly useful to have an editor that could open the yearly, not-backward-neither-forward-compatible iterations of 3D Studio Max, AutoCAD and Maya file formats. Especially when custom renders were involved. I still have somewhere a 3DSMax 9/Vray file that could be opened correctly only on the very same machine that wrote it.
We did not focus on legacy proprietary format though, but many modern formats are supported.
BSD 3-Clause "New" or "Revised" License
https://github.com/f3d-app/f3d/blob/master/LICENSE.md
(I had trouble finding the git repository.)
Could I use F3D as the rendering engine for a game?
Hard to say since I never used UE static mesh viewer, but if you test it I would apreciate a feedback!
> Could I use F3D as the rendering engine for a game?
Not really. F3D rely on VTK for rendering, which is definitely not a game rendering engine.
That being said, you can easily render 2D sprite for your games by scripting F3D.
after downloading from the web page: the macos arm download is corrupted I think, x86 works fine, currently watching the orc "thing" angrily stand in place.
You could just download the binary we distribute instead: https://f3d.app/doc/user/INSTALLATION.html