(08-05-2022, 05:38 PM)Domtav Wrote: Hello,

I am currently taking my head on an effect that I do not understand.

In editor mode, I get a fluid that suits me on the color side. It's a beautiful green (with very little transparency).... a bit slim like ghostbuster if you see the thing :p
When I compile the game and launch it I end up with a sort of translucent and darker green... yuck... well, it's not ugly, but nothing to do with the expected effect.

I did several tests and the one that seems the most representative is by simply trying to make white. In editor mode I get a suberde milky white (very slight transparency) and in runtime I end up with greyish water! (very transparent and gray).

Among the different tests:

- Change the transparency parameters (alpha of the disk or of the obi particle renderer: no effect.

- Modification refraction / transparency on the obi fluid renderer, besides the fact that it impacts me all the fluids of the scene at the same time, the effect is far from ok. Play on the other parameters (reflection/metalness...) without success.

On the parameter side, in URP, I have of course the same configuration (defined by default) between the two modes. I turned off all other post-process graphical processing (volume, etc....).
I even changed the color of the skybox to have white and limit the edge effects. I also have remove all the other light sources, nothing to do... of course the directional light is white...

So my questions are:

- How do I ensure that the color in execution mode is identical to the color obtained in edit mode ("game" window) ?

- How I remove the transparency without having to play on the obi fluid renderer which affects all the fluids ?

thank you !

D.

(10-05-2022, 09:36 AM)josemendez Wrote: Hi!

This sounds like a color space issue, since fluid colors aren't purposelmodified in editor vs the build (the color buffer is just an ARGB32 render target).

What platform are you building for, and what are your build settings?

(14-05-2022, 03:02 PM)Domtav Wrote: The build setting ? There are lot of setting... You talk about color buffer, so i suppose you ask about graphics settings ?

(14-05-2022, 03:02 PM)Domtav Wrote: I add also in PJ the particleShaderURP used by the emitter (lot of error , but it's the original file provided in the asset, I didn't touch it)

(16-05-2022, 10:23 AM)josemendez Wrote: Hi!

I meant File->Build Settings->Player Settings, there you will see color space and graphics API options, which are the ones I'm interested in.


These are implicit truncation warnings, shouldn't have any noticeable impact on the end result. Different graphics APIs treat precision modes differently, so for instance assigning a float value to a half variable will result in an implicit truncation.

Also, if you could share a couple screenshots of how the fluid looks in-editor and how it looks in your build, that would be very helpful. Otherwise I can only guess!


kind regards,

(16-05-2022, 05:01 PM)Domtav Wrote: Yes yes, I know, the fluid is "strange", but unfortunately, after several hours of trying to make a real fluid that does not look like a jet of lumps, I gave up.

(16-05-2022, 05:01 PM)Domtav Wrote: NB : check the option vulkan settings srgb write mode change nothing.

(17-05-2022, 08:20 AM)josemendez Wrote: Using a particle-based engine (which discretizes fluid as small ellipsoidal particles) to simulate a thin, long, continuous fluid jet is going to be challenging for obvious reasons: increasing fluid resolution will allow the jet to be thinner (since particles are smaller), but will also make it more prone to gaps in the flow (because well, particles are smaller!) as well as decrease performance (because you need more particles to simulate the same volume of fluid).

An eulerian approach would be much better suited to this use case, imho.


Based on your screenshots, this looks like a lighting issue, not really related to color space. The gamma curve for both screenshots seems identical, but the fluid seems unlit in the standalone one. So far I haven't been to reproduce anything similar, tried both on Mac and Windows using the same settings you shared.

Only potential culprit that I can think of right now is that you're using different render pipeline settings for standalone and editor. Check that the pipeline asset you're using in the Quality for standalone builds in PC,Mac&Linux is the intended one:




If this isn't the cause either, would it be possible for you to send the project to support(at)virtualmethodstudio.com so that I can take a closer look? thanks!

(19-05-2022, 09:56 AM)Domtav Wrote: "An eulerian approach would be much better suited to this use case, imho."
That is to say ? how do we do this? Do you have examples or do you know of a typical youtube link that explains this in detail? thank you

• Eulerian = grid based.
  
• Lagrangian = particle (or body) based.
  

(19-05-2022, 09:56 AM)Domtav Wrote: By moving (and only that) the files under a single directory to facilitate the export, the behavior to change. It's still ok in runtime mode in the editor but in runtime it's now OK for white ( ??? with strange black point ) and KO for green and red. I have the impression that it increases the transparency effect (when the green flow passes in front of the white area it becomes green again).

(19-05-2022, 01:25 PM)Domtav Wrote: Thank you for these explanations.

I fear that my brain is not compatible to implement solution B :p  
I confess to not really understanding the subtleties of all this, and it was frankly not the goal I had in mind when buying the asset honestly :p

(19-05-2022, 01:25 PM)Domtav Wrote: I hope that in the light of the test project you will find the place where I messed up

(19-05-2022, 01:25 PM)Domtav Wrote: Edit: oops, so much for me, during my tests I had reactivated the checkbox on the obi particle renderer for the white simulation. But it is not suitable at all because it causes lumps. In the transmitted project, you must tick the checkbox and find the initial test.