OTOY Forums

Hi,

Sorry again for this issue. Are you working with the latest 2018.1.2.1 or 4.04.0.2 plugin builds? They include my latest attempt to try to resolve this weird issue that I've never been able to reproduce here, but that hopefully should be fixed in these latest builds:
viewtopic.php?f=102&t=71420
viewtopic.php?f=102&t=71372

Thanks,
-Juanjo

Hi juanjo,

Thanks for your fast answer !
At the time it was houdini 17 with Octane 4.0.1. So i haven't try the last build.
I will make some more test on a personnal project but i can't take the risk to test in a commercial project.

I will try to find the scenes but will send them by PM because i can't share them on a public forum, as it is client work.

Cheers
E

Since the release of these latest builds, I have no news about users that have reported this problem again, so in any case, please update your Octane build to them. I'm not sure if a repro scene is going to help, I have several scenes from other users here, but I've never been able to reproduce the problem.

The fixes included in the latest Octane plugin build should be theoretically enough to be sure that in no case the scene data is altered in any way from the plugin side, at least from all the data I have from the HDK docs and the SideFX help, although nobody knows exactly how something like that was possible in the older Octane plugin builds ... I mean, it could be a bug in an HDK function, but now the plugin is not using any function that could change the scene spare parmeters, that is the source of the problem.

Thanks,
-Juanjo

Juanjo i haven't test last build yet, but i can add the fact that this problem only appear with Octane 4.0 release.
I have use 3.07, 3.08 on lot of projects and so far i haven't encounter any major issue with those version.

Yep, it seems that it only affects the builds after the introduction of the custom attributes and other new features. Can you please try the last builds available? Could be great to confirm if this problem has been fixed on it.

Thanks,
-Juanjo