Octane in Game Mode Tweet

[FahadA92]

Hello,
When reading the release notes for latest version, I see that Game Mode is supported but I can't get Octane to work. Whenever I enter game mode, octane unloads, and if I try to load it, it just shows a "stopped" viewport.

[Xhed]

You'll have to restart the render target after loading Octane in play mode, the same way as you would do normally.

[jalley]

And what about Octane-specific node parameters. In between reloads of Unity Play mode and consequently Octane, some parameters seem to be lost in between. Is there a way to save such info so we do not need to manually tune it each time you load Octane. For instance render target enviroment tuned parameters are lost in between save and reload. There is a recent post thread discussing the environment problem, but there are many others happening e.g. with object RenderLayerID, of a GameObject, etc. Quite time consuming ...

Thanks!

[ChrisHekman]

In the upcomming build we have updated switching to play/game-mode and octane will now stay loaded.

In the meantime, If the properties have been changed via the rendertarget component gui, you should get a save prompt after pressing the play button. If you save, the changed properties should hold.
If they dont, please do tell us which properties have not been saved.

[jalley]

Hi Chris and OctaneRender Team,

First of all, let's say we acknowledge your great effort in opening this plugin. Thanks for your hard work.
Going to the point. We provide here two examples of two things that are failing and bothering us in our work.

Two examples of modifying Octane Node exclusive parameters, that after entering and exit Play mode are not save among executions. Or worse, even if you save de Unity project and load it again, they are also lost. So we did not find a proper way to not having to repeat this work, every time we need to produce a render.

Case 1. RenderLayerID assignment.

There seems to be some sort of bug for which some objects retain properly the assigned LayerID, but others don't. We tried adjusting them again and re-saving, but these changes are not stored for some reason. It seems like from our set of objects some work well and some don't. Weird.

Case 2. Enviroment Settings.

Similarly, we want to store a certain configuration of an HDR enviroment. But each time we save specific Octane Node parameters, they are forgotten the next time we repone the Unity project or even just reload Octane. Again weird.

I enclose in this post two pictures of the changes and the final result after Octane Reload (equivalent if you reopen the Unity scene/project).

Thanks again for you work, we hope you can find the problem. It will save lots of time for us, so we can double our bid on using Octane SW.

Best,
jalley

[ChrisHekman]

On the environment settings.
We do not fully support changing settings from the Octane GUI and recommend using the Untiy RenderTargetComponent interface. Some settings will be saved, others -like textures- are only saved when set via the Unity interface.

On the renderlayerID.
This is fixed in our current mainline and will be part of the next build

[jalley]

Hi Chris, all

Thanks for your reply. We are happy to hear that some of those problems are already fixed. It would be extremely useful to get other Octane-GUI parameters exposed and saved as well.

For the sake of completion, we have performed more tests on other attributes we need (these ones exposed through the Unity interface) but that are not being saved as well:

1) We set the color attribute and/or bake id to ObjectA; 2) In object B we set different values. We save the project ... open again ... Object A appears with values of Object B. We do not know why. Reason could be related with the fact that they were both instances of the same prefab in Unity, but at least in Unity, this is not the expected behavior (as we never press the apply to all instances button)

Are those parameters included in the "bug fixed list"? Can we expect this to be fixed in the next release as well?

Thanks so much,
jalley

[Xhed]

Thanks for finding the bug Jalley. It is still present currently, so we'll look into it.

[ChrisHekman]

Hi Chris, all

Thanks for your reply. We are happy to hear that some of those problems are already fixed. It would be extremely useful to get other Octane-GUI parameters exposed and saved as well.

For the sake of completion, we have performed more tests on other attributes we need (these ones exposed through the Unity interface) but that are not being saved as well:

color_and_bakeid.png

Are those parameters included in the "bug fixed list"? Can we expect this to be fixed in the next release as well?

Thanks so much,
jalley

I found the underlying issue. It seems that when copy is made of a PBRInstanceProperties component (By duplicating/copy-pasting a gameobject for example) they will share the same underlying data. Which explains why changing object B changes object A
I fixed this. It should also repair scenes that have this data-sharing issue.

Would it be possible for you to confirm this is the underlying issue?

[jalley]

Would it be possible for you to confirm this is the underlying issue?

Hi Chris,

I guess you are asking Xhed about this, but obviously we can only verify/confirm that it is fixed when we gain access to the latest release. Could you share an estimate about when that date should be?

Thanks both for putting your effort on solving this issue,
jalley