News for hackers. Stuff that matters.
Re:Filament: Physically-based rendering engine by andybak on Saturday August 04, 2018 @10:24AM (#17686957)
1. What's the likelihood of seeing a Unity wrapper for this in my lifetime? I imagine the takeup of it if it plugged into Unity or Unreal would be massively increased.

2. How does it compare with what OTOY are working on for realtime? I imagine they are focused on quality over performance and aren't even considering mobile.

Re:Filament: Physically-based rendering engine by lebek on Saturday August 04, 2018 @08:59PM (#17689156)
Unity and Unreal both support Android and PBR so I don't see an obvious benefit to being able to use this alternative renderer. Because of the license and the fact that it's a newish codebase written in simple C++ I can see it being popular as a starting point for in-house engines.
Re:Filament: Physically-based rendering engine by kowdermeister on Saturday August 04, 2018 @03:43PM (#17688176)
PBR is already enabled in most game engines, it's even supported out of the box by Three.js
Re:Filament: Physically-based rendering engine by andybak on Saturday August 04, 2018 @05:20PM (#17688475)
I'm asking about this specific engine - not PBR in general.
Re:Filament: Physically-based rendering engine by Asgardr on Monday August 06, 2018 @05:54AM (#17696301)
Why would Unity use Filament? They have a PBR solution that works for them and is in active development. OTOY's OctaneRenderer is an unbiased path tracer. It's not comparable to Filament, two different use cases.