Version 2.1.5

• On Unity 2023.2, when using HDRP and DX12 graphics API, there’s a chance of crash

  • You can temporarily switch to DX11 (assuming you are not using ray tracing)

• On Unity 2023.2, when using HDRP and DX11 graphics API, visualize SDF in smoke will ignore depth buffer

  • It doesn’t prevent you from using visualize SDF, so you can safely ignore this issue

• Depending on certain project settings and the presence of other render related render components and/or packages, liquid/smoke rendering may be flipped upside down on Android and/or iOS builds

  • To work around that, you can add/remove usage of “FLIP_BACKGROUND_TEXTURE” and/or “FLIP_NATIVE_TEXTURES” material keywords in the plugin’s code
  • Enabling rendering downscale with minimal scaling (e.g. .99) can solve the issue with flipped textures. With the performance tradeoff

• When using non uniform scale with Neural SDF, it will be skewed

• On URP, you may get the following error:

  IndexOutOfRangeException: Index was outside the bounds of the array.

  UnityEngine.Rendering.Universal.ScriptableRenderer.SetupNativeRenderPassFrameData (UnityEngine.Rendering.Universal.CameraData& cameraData, System.Boolean isRenderPassEnabled) (at ./Library/PackageCache/[email protected]/Runtime/NativeRenderPass.cs:113)

  • This error is triggered when you exceed the maximum number of allowed URP render passes
  • To work around it remove or disable unused render features in URP settings

Version 2.1.4

• When using non uniform scale with Neural SDF, it will be skewed

• When the manipulator’s scale has a 0 value on any axis, it will break the simulation.

• On URP, you may get the following error:

  <aside> 🚨 IndexOutOfRangeException: Index was outside the bounds of the array. UnityEngine.Rendering.Universal.ScriptableRenderer.SetupNativeRenderPa ssFrameData (UnityEngine.Rendering.Universal.CameraData& cameraData, System.Boolean isRenderPassEnabled) (at ./Library/PackageCache/[email protected]/Runti me/NativeRenderPass.cs:113)

  </aside>

  • This error is triggered when you exceed the maximum number of allowed URP render passes
  • To work around it remove or disable unused render features in URP settings