-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
Export to external rendering software. #174
Comments
There is multiple layers to this, I will try to separate them.
|
@mwestphal Thank you for the explanation. I agree that any general export scene work should be done after libf3d complete. As for RIB specifically, it is already in implemented from what I read. Cheers |
Good point I missed that. I'm still interested in your actual usecase. |
@mwestphal I realised I can't formulate a strong use case. Initially, I was thinking of using F3D because it pulls in many scientific and engineering assets for viewing and so I can use it to perform offline render out 8k, 16k high resolution renders for posters etc but I see that F3D can already do that via OSPray. I was also pursuing external render because if I can hook up the future libf3d API to e.g. 3Delight, I can leverage the rendering power of cloud computing easily. I will think about this more in the coming months and track the libf3d API development. Cheers |
the libf3d now permits to use an external render window, in the testing directory you will find examples for glfw anf Qt. Let us know how it goes ! |
Is your feature request related to a problem? Please describe.
I would like to be able to generate very high resolution rendered images suitable for posters.
Describe the solution you'd like
Ability to export a file from f3d for offline rendering in another software e.g. Pixar RenderMan, DNA 3Delight
Describe alternatives you've considered
Overload the --output option and detect the filename and if the filename ends with *.rib, call some exporter code. I am new to the code base so some of the questions I have would be (1) was such export a design consideration of f3d originally ? (2) is there an entry point where I can walk the entire scenegraph to iterate through all the geometries, textures/material, lights and cameras ?
Contribution
I have some familiarity on the RenderMan/3Delight side.
The text was updated successfully, but these errors were encountered: