filament

While this one seems like an official Google project, some other projects are not, even if it is on github.com/google A random example E.g https://github.com/google/filament#disclaimer This is not an officially supported Google product.

There's also https://github.com/google/filament

It does look like Filament has a web target: https://github.com/google/filament but if they're targeting embedded systems, maybe they haven't prioritized a public web demo yet. If the bulk of the project is actually in C++, making a web demo probably involves a whole WASM side-quest. I suspect there's a different amount of friction between "I wanna open source this cool project we're doing" and "I wanna build a rendering target we won't use to make the README look better."

I'd like to share Thermion, an open source 3D rendering toolkit I made for Flutter and/or Dart. This came about when I needed a 3D renderer for a Flutter app[0] I was building. At the time, the only off-the-shelf option was to embed Unity, which wasn't ideal for a few reasons - unstable build process, compositing and transparency issues, and licensing uncertainty, just to name a few. In any event, frankensteining Unity (C#) together with Flutter (Dart) didn't seem like a great solution. After browsing for alternative renderers, I discovered Filament[1], an open-source, cross-platform Physically Based Rendering engine from Google. I initially only wrote some simple bindings to embed Filament inside a Flutter Android/iOS app, but have since added more functionality, and have expanded this to cover Windows, MacOS and Web (there was Linux sup

How does this compare to Google's filament? [0] [0]: https://github.com/google/filament

Anyone know much about how this compares to Filament by Google? https://github.com/google/filament

Just getting back into Android dev myself. Rapid workflow stack: Jetpack Compose / Kotlin, Material Design UI kits and Stripe / Firebase Cloud Functions. The emphasis on being able to go from idea to release in the shortest time frame. Target being Fast Mobile Commerce https://github.com/android/compose-samples https://material.io/resources https://firebase.google.com/docs/use-cases/payments Other than that I'm excited about next-gen low latency audio library Oboe and real-time physically based renderer Filament https://github.com/google/oboe/tree/master/samples https://github.com/google/filament/tree/main/samples Best of Luck ;)

Does Google use Filament [1] for this AR stuff or do they have something completely different? I mean using something else would be a huge waste from my little point of view ¯\_(ツ)_/¯ [1] Filament is a real-time physically based rendering engine for Android, iOS, Windows, Linux, macOS, and WebGL2 - https://github.com/google/filament

Wait, Filament is on life support? There is activity there: https://github.com/google/filament/graphs/contributors https://github.com/google/filament/releases

https://github.com/google/filament and ThreeJS are probably the closest

For a multi-platform C++ project, these are quite reasonable prerequisites, as bad as it looks at first glance. Also AFAIK, to dabble with the web version, just download filament-*web.tgz file here: https://github.com/google/filament/releases, this contains a .wasm and .js file you can copy into your project (and soon this will most likely be on npm). Expecting a JS user to compile an emscripten project would be a bit much to ask ;)

Some samples from repo: https://github.com/google/filament

If you missed the earlier post about Filament and it's gorgeous documentation, here are a few links for you :) https://news.ycombinator.com/item?id=17684286 https://github.com/google/filament https://google.github.io/filament/Filament.md.html https://google.github.io/filament/Materials.md.html

If you missed the earlier post about Filament and it's gorgeous documentation, here are a few links for you :) https://news.ycombinator.com/item?id=17684286 https://github.com/google/filament https://google.github.io/filament/Filament.md.html https://google.github.io/filament/Materials.md.html

Yes it is using it wrong, because while some issues are indeed Swing interop bugs with the host GUI, others are lack of skills by not reading canonical books like "Filthy Rich Clients", written by Chet Haase and Romain Guy, the guys that drove most of Android rendering stack. Romain Guy's team recently released Filament, https://github.com/google/filament Back in the Sun days, Romain had a blog about writing nice looking Java UIs, which eventually lead to the "Filthy Rich Clients" book publication.