_FluidDepthTexture not found

[asimofu_ok]

When I play the Obi Fluid example scene, it makes this caution.

CommandBuffer: temporary render texture _FluidDepthTexture not found while executing Render fluid (SetGlobalTexture)

Some of examples seems not rendering fluid particles(MultiphaseFluidBuoyancy.unity and SimpleFluid.unity)
And in all example scene, its not rendering fluid particles in Scene View.
I use Unity2018.2.5f1 with Win10.

[josemendez]

When I play the Obi Fluid example scene, it makes this caution.

CommandBuffer: temporary render texture _FluidDepthTexture not found while executing Render fluid (SetGlobalTexture)

Some of examples seems not rendering fluid particles(MultiphaseFluidBuoyancy.unity and SimpleFluid.unity)
And in all example scene, its not rendering fluid particles in Scene View.
I use Unity2018.2.5f1 with Win10.

Hi,

Make sure you're not missing any shader from your installation. Try completely removing the /Obi folder and re-import the package.

[asimofu_ok]

Hi,

Make sure you're not missing any shader from your installation. Try completely removing the /Obi folder and re-import the package.

Thx for repling.
I tried import only Obi Fluid at new project.
After importing Obi Fluid I got this errors.



And I got this errors when I play example scene.
Also it didn't render fluids in scene view.


is my PC environment something wrong?

[josemendez]

Thx for repling.
I tried import only Obi Fluid at new project.
After importing Obi Fluid I got this errors.



And I got this errors when I play example scene.
Also it didn't render fluids in scene view.


is my PC environment something wrong?

After reimporting a native plugin, you need to restart Unity. Native libraries are only loaded by Unity at startup.

Fluid will not render in the scene view, as Unity only applies image effects (and fluid rendering, being a screen-space method is one of them) in the game view. You can still see particles in the scene view for debugging purposes by enabling the "render" checkbox in the emitter's ObiParticleRenderer. See:
http://obi.virtualmethodstudio.com/tutor...ering.html
http://obi.virtualmethodstudio.com/tutor...ering.html

[asimofu_ok]

After reimporting a native plugin, you need to restart Unity. Native libraries are only loaded by Unity at startup.

Fluid will not render in the scene view, as Unity only applies image effects (and fluid rendering, being a screen-space method is one of them) in the game view. You can still see particles in the scene view for debugging purposes by enabling the "render" checkbox in the emitter's ObiParticleRenderer. See:
http://obi.virtualmethodstudio.com/tutor...ering.html
http://obi.virtualmethodstudio.com/tutor...ering.html

I see. The red errors are not shown after restarting Unity.

But "Command Buffer caution" is still shown when playing example scenes.
Then I deleted Obi folder to reimport. But when I restart Unity after deleting Obi folder, Obi folder revived.
Obi folder seemed to be imported automatically at restarting Unity. 
And "Command Buffer caution" is still shown.

I don't know why I can't delete Obi folder...

[josemendez]

I see. The red errors are not shown after restarting Unity.

But "Command Buffer caution" is still shown when playing example scenes.
Then I deleted Obi folder to reimport. But when I restart Unity after deleting Obi folder, Obi folder revived.
Obi folder seemed to be imported automatically at restarting Unity. 
And "Command Buffer caution" is still shown.

I don't know why I can't delete Obi folder...

Make sure you're not deleting it from outside Unity. If you do, the .meta file for the folder will linger around and Unity will sometimes re-create the folder. You must delete project folders from inside Unity.

[asimofu_ok]

Make sure you're not deleting it from outside Unity. If you do, the .meta file for the folder will linger around and Unity will sometimes re-create the folder. You must delete project folders from inside Unity.

I could delete and reimport Obi Fluid.
But the caution is still appeared...

I think if this caution is not so serious, I will leave this problem.
Thank you for fast replying.