Thank you for your quick respond and your great efforts to improve the plugin,
before getting into more detailed discussion, please allow me to highlight again the importance of the workflow I mentioned.
The plugin was not specifically designed for the workflow you are using, so you may have some challenges using it this way.
I have to say, it is NOT only a personal preference, I would say it is critical for Entire revit world, and ALL revit user, which you can not reject.
The reason I emphasis on this issue is that the advantage of Octaine enable itself great potential to becomes a powerful tool to help designers developping their design,
Octane is not only for final production rendering like traditional render engines. (before rendering to merge everthing, this is that type of thinking) It is much more powerful.
To make the potential becomes true need right workflow.
Though there is some others walking along this way already, and doing quite well, like Enscape/ Twin motion and lumion, even Vray is catching up soon,
Yet personally I do prefer Octane, which potentially can be the best, to achieve this, there is major barriers to conquer, quite a few of them I have to say which are even really painful....
Hope you read the above, and this bug is a critical one I believe you will get it resolved in a perfect way.
Thanks again and best regards,