Announcement

Collapse
No announcement yet.

Issue Loading Irradiance maps after precalc with backburner

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Issue Loading Irradiance maps after precalc with backburner

    Hey I wonder if someone can help me, as I'm pulling my hair out!!!

    I've been using V-Ray now for about 12 years, and just recently I have been producing more animations with moving objects. Before I had been whacking up the settings and rendering frame by frame they have been acceptable, but a little noisy and flickery.

    I'm starting a new project with lots of moving objects and I want to use the animation Pre-calc workflow, the trouble is, back burner is really driving me nuts with errors to do with not loading the individual irradiance maps. It's very erratic, works on some render nodes some of the time, and never on some others.

    With the few frames I have managed to render the results look good, the workflow is straight forward and the render times are acceptable. I just need to sort out this reoccurring errors.

    I don't typically have any issues accessing textures, models, files over my network, all the nodes communicate with a NAS where all the files are stored. So I don't understand what is so special about the IR files, that backburner can't see them?

    This is the error in the log "Error message: 3dsmax adapter error : Autodesk 3dsMax 16.0 reported error: [V-Ray] Could not load irradiance map."

    Any ideas......
    Last edited by Virtual_Living; 10-04-2018, 05:46 AM.

  • #2
    I found the issue, here it is for future reference if anyone else discovers this.....

    It turns out that one of my render nodes had not saved the irradiance maps during precalc (it didn't report this in backburner however), so every 5 frames or so I had a dropped (missing) IR map. I'm not sure why yet. This explains why the issue seemed intermittent, as back burner was trying to use different render nodes to try and complete the erroneous task during the rendering pass. Looking at the folder containing all the IR maps this wasn't immediately obvious at all as there was over 200 of them (minus the missing 20 or so). And I only discovered this by trying to copy all the IR maps locally, which is when I discovered the first missing file, because everything was rendering fine until it hit the first missing IR map. Then Eureka!


    Back-burner was reporting that there was an issue 'loading the map', but it would have been much more useful if it had reported an error that there was 'no map'!! In retrospect it's the same thing, but if the computer is saying it's having difficulty trying to load a map, it suggests there IS a map.

    Comment

    Working...
    X