OTOY Forums

vray metal is converted as clear material

Any ETA or chance for an hotfix regarding the material editor update bug? I usually render other scenes with a second instance of 3dsmax and can't open a second render video just to set up materials.

Otherwise I just will go back to 4.39..

I mbetke,
I reported that issue some days ago, I will ask about ETA.
I suppose they are working hard to release a new 3dsMax plugin 3.07 SDK with fixed issue too.
Regards
Paride

coilbook wrote:For some reason fire particles in Phoenix FD do not work in version 4.40 They are not rendered

Hi coilbook,
you could try to set Group Index 0, it seems to work fine.
Regards
Paride

coilbook wrote:vray metal is converted as clear material

Hi coilbook,
could you share your vrayMtl?
Regards
Paride

I know I mentioned before but OMG

A scene is using only 2.4gb of vram.

We have 3 unique phoenix fire grids in the scene. Scene evaluation time is 1 min 40 seconds.

If we make a copy of those grids (TOTAL 6 grids, only 150 mb of vram increase) and in phoenix input choose the same sim files but with different start time evaluation time goes to 6 min.
It seems octane does not like copies of phoenix grids that use the same folder containing sim files. It needs unique folder for each sim grid to be fast at evaluating. I think it is a bug. Each fire sim is only 50 mb per frame.


_______________UPDATE__________________

I did some tests with loading times/evaluation with multiple Phoenix grids only. Not sure why it takes so long. Each grid has its own folder with sims


5 grids: 3 min 20 seconds to open viewport. Scene size 1.25 Gb of vram

3 grids: 1 min 40 seconds

1 grid: only 20 seconds. File size 0.6 gb. So 5 grids should be evaluated in 1 minute not 3 min 20 sec.

Hopefully otoy can fix this bug with multiple grids and evaluation times. Because 5 grids total of 1.25 gb open about 6 times slower than one large grid that is 1.25 gb in size.

And we use SSD storing sims so they should load quick to the memory

Thank you !

why do pflow sparks motion blur looks strange. I thought it was fixed

even using mesher does nothing like this old post said viewtopic.php?f=81&t=55639

and we do use DELETE event to kill off the particles

Hi coilbook,
MB seems to work with mesher too. Maybe I'm wrong about your issue, could you share your test?
Regards
Paride

paride4331 wrote:Hi coilbook,
MB seems to work with mesher too. Maybe I'm wrong about your issue, could you share your test?
Regards
Paride

HI Paride
here is the scene with wrong mb direction Thank you

it seems when saw moves horizontally sometimes it works sometimes it does not. Sometimes pflow works and mesher does not .

Also some frames it works and some frames it does not. Frame 371 it works and frame 372 it does not. Delete operator messes with pflow

Hi Paride
could you tell otoy about slow load times of multiple phoenix grids. Thank you