I was watching the Entagma H18.5 tutorial,in the video the pyro solver works almost in real-time on a RTX 2080. But when I test it for myself,the pyro solving is still pretty slow even after I turn on minimal opencl solve/opencl solve in H18.5. I have 2x RTX 2080Ti btw.

Did I miss anything?

my PC spec:

AMD TR2990wx
corsair 16g*4 3200
rog ZENITH EXTREME X399
rtx 2080ti *2

Hi Tony! If you log a bug with your hip file, we could check it out. Otherwise, if you post your hip file maybe a fellow Houdini user in our community can help you out.

How to log bugs and rfes for Houdini
https://www.sidefx.com/forum/topic/15603/ [www.sidefx.com]

TonySuen
I was watching the Entagma H18.5 tutorial,in the video the pyro solver works almost in real-time on a RTX 2080. But when I test it for myself,the pyro solving is still pretty slow even after I turn on minimal opencl solve/opencl solve in H18.5. I have 2x RTX 2080Ti btw.

Did I miss anything?

my PC spec:

AMD TR2990wx
corsair 16g*4 3200
rog ZENITH EXTREME X399
rtx 2080ti *2

Make sure you are using the same card for simming as for 3D view/monitors. The second card should not be used for maximum performance.

We have been trying the minimal pyro solver and it is not working for us.

We don't get any errors in the shell or anything, but if we toggle Minimal OpenCL Solve on, the solver simply does not work.

Any ideas on how to debug this? We are on NVIDIA 450.80.02

Thanks,
Sean

I was getting the same problem where my sim just disappeared when I enabled the Minimal Solver.
Turns out it was because Houdini had set my internal GFX card as the Main OpenCL device and not my Geforce so there wasn't enough VRAM to even start the sim.

EDIT:
While this worked in a simple scene with a sphere, I can't get it to work for my current project sadly.
Been testing it out more and my scene is setup with a start frame of 1001, where the sim doesn't work.
When I set the start frame to 1 though it works fine. Been trying to change the sim setup to go from 1001 in case it didn't recognize it automatically as the start or something but nothing works.

EDIT EDIT:
Friend had no problem with using a different start frame than 1. He was on a newer daily build and suggested I do the same.
Works perfectly now. Production build must have a bug.