Skip to content

Clarity on intention/implementation #2

Description

@tobyclh

Hi,

Great work on open sourcing this, really appreciate it.

Similar to #1, I want to have some more clarity in terms of what is the intention of the open source library, and more importantly what can and can I not do with the library.

  1. For example, the dna provided via FAB doesn't have a render-able geometry, so I am assuming that the actual metahuman topology etc are still under UE standard licensing and is not part of the deal? It is rather difficult to handle since it would be hard for me to even run a unit test if I were to release something open source (which I intend to). And even for that DNA I cannot include in a public repo I assume? The same goes for the faceboard?

  2. If I am understanding it correctly all the shaders are obviously still under standard UE license. To accurately render a dna with their texture maps I will basically have to create the shader system compatible with the one in UE, which is completely fair. But I can roll up my own Cook-Torrance / GGX-style shader stack, but am I going to get into trouble if I were to release it if it looks close to the one from UE? Or is that one of the intended use?

  3. What exactly do you guys want to see coming out of this release? I am asking so I don't get on your bad side.

Cheers!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions