Hi, It is easy to parent an object (typically a sphere with normals Inside for fog/Scattering Medium) Inside Octane Standalone using ascendent links and a Position node shared by the camera and the sphere, but is there a way to extract transform data from the camera of an Alembic node ?
Below, just to remember, how to parent the sphere to a regular camera :
How to extract Camera Transform out of an Alembic node ?
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
- Attachments
-
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
You should be able to click on your render target, select camera, then click where the name is (or somewhere around there I think), copy and past to your node graph. I was doing this with other things last night. It will give you a node with all that data. Worked with kernel settings when I was testing.
Intel quad core i5 @ 4.0 ghz | 8 gigs of Ram | Geforce GTX 470 - 1.25 gigs of Ram
@Kavorka : When a camera (I need an alembic camera because it is animated) from an alembic node is used, position node is not present in the Render Target ! 
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
I think the only solution right now is to write a script that creates a copy of the camera node internal to the scene node graph and reads out the animation and sets it as a regular animation. I will give it a try tonight.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Thank you Abstrax. As you may know, I am totally hopeless with scripting.
Currently, the solution I can see for fog is to parent the medium sphere to the camera inside Blender, and export an alembic file including the sphere and the camera, or two alembic files. But I may have to work on an alembic file given by someone else, and in such case I have to parent the sphere inside Octane.
So in this case a script solution would help. I also asked in the plugin section (not got yet an answer) if the alembic exporter could add an output pin for the camera transform.
Cheers,
Philippe.
Currently, the solution I can see for fog is to parent the medium sphere to the camera inside Blender, and export an alembic file including the sphere and the camera, or two alembic files. But I may have to work on an alembic file given by someone else, and in such case I have to parent the sphere inside Octane.
So in this case a script solution would help. I also asked in the plugin section (not got yet an answer) if the alembic exporter could add an output pin for the camera transform.
Cheers,
Philippe.
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
Ok, here is a script that creates an animated "bubble" (actually a box) the moves with the camera. In contrast to the camera in scene node graph, the animation of the bubble will be saved in the .ocs file.
It turned out to be a bit more complicated than initially thought, because the size of the box needs to be adapted to the amount of movement the camera does in each frame, to make sure that it stays completely in the box during the shutter interval. As a consequence, if you changed the shutter time, you will need to re-run the script. The script is also limited to thinlens cameras right now.
I guess, in version 2.x we will provide a material/medium pin on the camera to specify the start medium around the camera. Then this workaround will not be necessary anymore.
Let me know if there are any issues.
EDIT: Make sure that you run the script in version 1.52 or higher since older versions crash when you delete a temporary root node graph.
It turned out to be a bit more complicated than initially thought, because the size of the box needs to be adapted to the amount of movement the camera does in each frame, to make sure that it stays completely in the box during the shutter interval. As a consequence, if you changed the shutter time, you will need to re-run the script. The script is also limited to thinlens cameras right now.
I guess, in version 2.x we will provide a material/medium pin on the camera to specify the start medium around the camera. Then this workaround will not be necessary anymore.
Let me know if there are any issues.
EDIT: Make sure that you run the script in version 1.52 or higher since older versions crash when you delete a temporary root node graph.
- Attachments
-
- Create Animated Cam-Bubble.lua
- (10.94 KiB) Downloaded 120 times
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
this is is a great idea marcus and it will be surely very usefulabstrax wrote: I guess, in version 2.x we will provide a material/medium pin on the camera to specify the start medium around the camera. Then this workaround will not be necessary anymore.
ciao beppe