microsoft / microsoft/TRELLIS.2
Clarification on commercial usage regarding NVIDIA library dependencies (nvdiffrast/nvdiffrec)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.3k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Thank you for releasing TRELLIS.2. The performance and quality are truly impressive.
I have a question regarding the licensing and commercial use of this project. While the TRELLIS.2 repository itself is licensed under the MIT License, nvdiffrast and nvdiffrec as dependencies.
As far as I understand, those NVIDIA libraries are under the "Nvidia Source Code License (1-Way Commercial)," which restricts usage to non-commercial research and evaluation purposes only.
Could you clarify the following points?
Commercial status of the current implementation: Does the dependency on these NVIDIA libraries effectively mean that the current version of TRELLIS.2 cannot be used for commercial purposes (e.g., in a commercial service or for generating commercial assets)?
Potential for commercial-friendly alternatives: Are there any plans to provide an implementation that uses commercial-friendly alternatives (such as PyTorch3D or other MIT/Apache-licensed rasterizers) to replace the NVIDIA-specific dependencies?
I would appreciate your guidance on this, as many developers are interested in using this technology in practical, commercial applications.
Best regards,
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's licensing information and the nvdiffrast and nvdiffrec dependency terms mentioned in the issue. Compare those constraints with the proposed PyTorch3D alternative; done means documenting the project's commercial-use status and any confirmed alternative implementation plans.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100