OTOY Forums

- If you click Cancel on the missing texturemaps search folder dialog, the plugin will now ask you if you want to continue searching for missing texturemaps

hello Paul,

just opened an project with changed texture paths and the feature is not working properly.
If you first choose the "chancel" option for texture 01 and then choose "continue re-linking missing texture maps?" the program jumps back to the cannot find texture 01 dialogue, whereas it should jump to the next texture...

can somebody verify this?

best

Andreas

Andreas, this is fixed in the next release.

Paul

I have updated the installer at the top of this thread with:

3.3.1.68 (12-Jul-2016)
- Compiled with Octane 3.03.1
- Minor changes/fixes to the missing texturemaps functionality introduced in 3.2.0.67

Paul

i wonder if this is only me or is happening to everybody.

when i export Bongo animation as OCS, and opened it with Standalone, the meshes animates in 24 fps speed and the camera animates in 30 fps speed.
so if i have 120 frames of animation in Rhino / Bongo with both model movements and camera movements, i end up having 150 frames in Octane standalone with the model action ending in frame #120 as the camera keeps moving until frame #150.

i'm using the latest build of the plugin, 3.3.1.68.

when i export Bongo animation as OCS, and opened it with Standalone, the meshes animates in 24 fps speed and the camera animates in 30 fps speed.
so if i have 120 frames of animation in Rhino / Bongo with both model movements and camera movements, i end up having 150 frames in Octane standalone with the model action ending in frame #120 as the camera keeps moving until frame #150.

I think the plugin assumes the animation is running at 30fps (since there is no way to query Bongo for the actual fps), so when Octane Standalone reads the OCS/ORBX it will open the camera and mesh transform animation tracks assuming 30fps. Perhaps try re-timing the Bongo animation to 30 fps.

Paul

thanks Paul, and sorry i wasn't making myself clear enough.
so the action i have in Bongo is the fan starts opening in frame # 0, and fully opens in frame#119, while camera pulls out.
and the frame #119 is the end of the Bongo action.

when i first open the OCS file with standalone app, the fps setting says 24 fps with the frame #119 being the last frame.
here the fan fully opens in frame #96, whereas the camera keeps pulling until frame #119.

then i set the fps to 30 in standalone app, then it shows the last frame # is 149.
the fan fully opens in frame #119, whereas the camera keeps pulling until frame #149.

Thanks for the additional info. I can see in the plugin code that there are references to 24fps and 30fps - so that is not consistent, and I will fix this in the next release and that may resolve your issue.

Paul

thanks Paul, i look forward to the next release!!
so there's no workaround for this issue, right?? apart from rendering without passing OCS to standalone, which causes longer loading time in Rhino...

I have refreshed the installer at the top of this thread with:

3.3.3.70
- Compiled with Octane 3.03.3
- Resolved some inconsistencies in the fps exported from Bongo animations. All exporting functions assume 30fps.

Paul

Paul, thanks for the quick fix!!!

unfortunately it isn't making any difference in my end.
i will look through my setting and workflow once again to make sure i'm not making any mistake, but it'll be great if you can keep looking into other possible cause for this.

thanks!