remKa wrote:That's so weird... Yes I did several times.
Could it be an option in the Octane Preferences Tab ?
Hi remKa,
Thank you for your scene.
That's strange, it works fine for me too..
I tried with Phoenix FD 5.01 and 4.00.
With Phoenix FD 5.01, I just had to change the Output path to the aur files folder, and it worked.
With Phoenix FD 4.0, I had to restart the simulation, but it also worked.
As far as I could see, I tested with the same settings as you, octane 2021.1.6 - 12.26, max2023, phoenix 5... but can't reproduce the issue.
It's not related to the Preference settings; I could use yours too; and the settings in Render setting's Support tab are fine too..
So that's quite a mystery..
I can see in your screenshot Primitives/Meshes/Voxels: 12/2/654360, where I have 12/2/1308720, (that's 654360 for the volume vdb + 654360 from phoenix grid), so the grid from Phoenix seems completely ignored.
So it doesn't seems to be an issue of channel names or scale..
Could you open the Octane node viewer (with the octane icon in the octane viewport), and select the node 'Vol-PhoenixFDFire01', as in this screenshot :
You'll probably have 0 x 0 x 0 voxels .. instead of 82 x 105 x 76. Could you post a screenshot ?
Also, could you check the 'Extended node info' for PhoenixFDFire01 in Octane object's property (right click on PhoenixFDFire01 to open the context menu), and see if you have the same as this:
I installed phoenixFD_adv_50100_max2023_vray5_x64.exe, but I don't have vray installed.
If you have vray 5 or 6 installed, could you try to install a phoenix that DO NOT MATCH the vray version ? (phoenixFD_adv_50100_max2023_vray6_x64.exe with vray5, or phoenixFD_adv_50100_max2023_vray5_x64.exe with vray6) ...
I will release an updated version shortly with Phoenix 5 SDK instead of the current 4. It shouldn't change much, but that could help.. let's see how it goes..
[EDIT : 2021.1.6 - 12.28 :
viewtopic.php?f=80&t=80710]
Thanks.