motion blur does not work right with phoenix fire

Sub forum for bug reports
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.

All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Post Reply
User avatar (Default)
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

do we have to go to the properties for vdb sim box and enable motion blur and vertex blur. Motion blur looks strange in octane with fires
output velocity is checked in phoenix itself and fire source

do we need to enable MOVABLE proxy for VDBs?
Attachments
mb noise.jpg
mb.jpg
Top
User avatar
paride4331
Octane Guru
Posts: 3809
Joined: Fri Sep 18, 2015 7:19 am

Hi coilbook,
Could you kindly make some screetshots test with motion blur and vertex blur issue separately please?
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
Top
User avatar (Default)
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

paride4331 wrote:Hi coilbook,
Could you kindly make some screetshots test with motion blur and vertex blur issue separately please?
Regards
Paride

i will. Do we need to set VDBs sims to movable proxies and check motion blur on? Or velocity channel through phoenix is enough
Top
User avatar (Default)
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

attached is the file. You can simulate yourself or use presimed vdb that is in the folder. Just go to frame 2 where box is moving fast and you can see that mb does not work for flames. Output velocity is checked. PHX Source Motion vel is also enabled, Enabled movable proxy and mb in octane properties for the sim grid. And still no difference


Enabling vertex mb makes it look all dark and strange. Like it does not work properly.

thanks
Attachments
OCTANE MB ON.jpg
OCTANE MB OFF.jpg
OCTANE VERTEX MB ON.jpg
octane mb bug .zip
(1.87 MiB) Downloaded 200 times
Top
User avatar (Default)
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

maybe it does work with vertex mb enabled but why so many grainy particles are created when vertex mb is enabled. is this how fire looks at high speed
Attachments
mb noise.jpg
mb vertex 2.jpg
Top
User avatar (Default)
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

here mb and vertex mb are ON looks strange but maybe that's how mb looks for flames?? Flames are traveling away from camera at high speed
Attachments
pixelated.jpg
Top
User avatar
paride4331
Octane Guru
Posts: 3809
Joined: Fri Sep 18, 2015 7:19 am

Hi coilbook,
I checked your issue, made a report and sent it to developers.
About "pixellated" effect, it would be a question about density (screenshot)
did you try to adjust it by changing volume medium density value and phoenixFD grid too? (I know you asked this in another post and I'm investigating it around).
Regards
Paride
Attachments
den.jpg
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
Top
Post Reply

Return to “Bug Reports”