-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Able to give the resource that generates the renders? #5
Comments
Funny you should say that, because I've started work on a "Material Explorer" using threejs that will hopefully be on the site sometime in the future. Sneak peek here (viewport size is broken atm): https://physicallybased.info/threejs/ |
Thats pretty kewl. Can't wait to see it all working. |
Sorry I forgot to answer your question about releasing the render ball scene. I have plans to do just that. I need to clean it up and do some further testing to make sure it works consistently (as possible) across different render engines. |
Just a little update; the USD Assets Working Group is working on a standardized render ball that I most likely will update to when it's ready. It's based on the same render ball I've used on the website. Here you can read a little bit more about it: https://docs.google.com/document/d/1Xeg646DNUm9KWXN71BFSFLW1L5_Ed8_2DawT6NdEhTQ/edit# This is the repository where it should be available when they release something: https://github.com/usd-wg/assets |
Saw an article about this library on twitter & i'm trying to see if I can replicate the results using threejs. So far I haven't been able to get it working right. Curious if the environment map, the model, lighting setup, etc that is being used to generate the renders can be released to try to replicate the results as close as possible. If successful, maybe its something that can be added to the site itself.
Here's the article in question & my attempts to replicate the blood pbr.
https://twitter.com/SketchpunkLabs/status/1557063158027657224?s=20&t=uJMEMXkr5tt_mzySet2NgA
The text was updated successfully, but these errors were encountered: