// Error: [proc] liquidShape1: error in user init from

// Error: [proc] liquidShape1: error in user init from

g.jove
Explorer Explorer
8,921 Views
8 Replies
Message 1 of 9

// Error: [proc] liquidShape1: error in user init from

g.jove
Explorer
Explorer

I am new to bifrost and using the default Arnold Render for Maya 2018. When I try to test render the scene I am currently working on I keep getting this error "// Error: [proc] liquidShape1: error in user init from ". If I use the Arnold Render View it works but I am planning to make a simple animation using the render sequence in which I keep getting this error. Any solutions? Thanks.// Error: [proc] liquidShape1: error in user init from// Error: [proc] liquidShape1: error in user init from

0 Likes
Accepted solutions (1)
8,922 Views
8 Replies
Replies (8)
Message 2 of 9

Anonymous
Not applicable

I've been having this exact problem as well for over a month now. The only way I have been able to get around it is to delete all Bifrost components and redo them, it works for a few days and then this error comes up again.

 

In the script editor i'm getting a bunch of

 

  • "[BIFROST AI TRANSLATOR]: Liquid data {} not found"
  • "// Error: [BIFROST] Failed to load bif file 'M:/Share/Colton/Maya/StaticCartridge/cache/bifrost/MainSceneBmbbifrostLiquidContainer1/voxel_liquid/voxel_liquid_volume.0001.bif'. //
    // Error: [BIFROST] Critical condition failed: (inData->inMemoryRef != NULL) (contrib\extensions\bifrost\procedural\common\src\Implicit.cpp:297) //
    // Error: Failed to initialize implicit data on node 'liquidShape1' //
    // Error: [proc] liquidShape1: error in user init from // "

I've tried

  • Moving the Bifrost cache to a local drive
  • Recreated the cache a hundred times in 
  • Cached the mesh
  • Starting the render at different points in the timeline
0 Likes
Message 3 of 9

g.jove
Explorer
Explorer
Accepted solution
Ah yes I did the same but I already found a solution. I have used Alembic Cache instead rather than BIF Cache.
0 Likes
Message 4 of 9

Anonymous
Not applicable

I've suddenly started getting the same message.  I've been using alembic cache from the beginning without a problem, rendering without a problem, now for some reason, it won't render in Arnold and I'm getting the message.  I have no idea what I may have changed to cause this.

0 Likes
Message 5 of 9

Anonymous
Not applicable

Did you actually get this sorted. I'm having the same issue

0 Likes
Message 6 of 9

m-a-gel
Explorer
Explorer

Im getting the same, gotta love how Autodesk couldnt care enough to the point where they just mark it as solved without it being solved... BiFrost is a mess.

0 Likes
Message 7 of 9

m-a-gel
Explorer
Explorer
I did actually find sort of a solution. I have bifrost starting at frame 161, and when i tried to render frame 116 to 400 it just errored out. But when i set render sequence to start render at liquids start frame (which for me is 161), it works. Så i will have to render 116 to 160 with liquid hidden or deleted, and render 161 to 400 with liquid enabled. Theres clearly an issue with liquids "start from frame" option. Maya is probably set at always start liquid from render 1, and when you change that inside the liquid setings, maya gets confused on which input to follow and just errors out. Strange how its been 4 years and this has still not been fixed.
Message 8 of 9

amityadav1152234
Explorer
Explorer

cam you please explaine sir? i'm still struggling with this

0 Likes
Message 9 of 9

strangelaw
Explorer
Explorer

Hi there! A bit time has passed, but Im wondering HOW exactly you managed via this method? Please, if you will, explain step by step.

 

Now is Jan 2025 - and the very SAME issue exists on Maya (latest revision). Only way I got pass this was to DISABLE ("bifrostLiquid1").

 

Many thanks in advance.

0 Likes