IndigoMax 0.50 error message
Posted: Mon Apr 24, 2017 5:41 am
Rendering a glass material with IndigoMax 0.50.
If one renders inside the Max frame buffer, no problems.
However, if one decides to export the scene instead to Indigo standalone (which I prefer), the following message appears:
I have tried all the different settings for a glass material; switching to single face, arch glass, changing the precedence - nothing seems to work.
Strangely, applying a glass material the first time to an object, and then rendering - it works. But if you stop the render, and then try again, then the above error message comes up. Looking at the .igs file, the first instance when it works, the following appears (which is correct):
But then stopping the render, and then trying again, the igs file is incomplete:
So something is not right in the way IndigoMax is exporting the materials. It seems to be stripping away the data referring to the internal medium. Constantly modifying the .igs file manually, is just too time-consuming with a complex scene. Will this be fixed? Can this be fixed?
Pretty miffed also (as a paid user of Indigo) that four emails explaining this problem to support@indigorenderer.com, have not been answered. As a Max user, is it worth actually my valuable time supporting a renderer of which the Max exporter always has been sub-par?
If one renders inside the Max frame buffer, no problems.
However, if one decides to export the scene instead to Indigo standalone (which I prefer), the following message appears:
Code: Select all
Scene parsing error: Node with UID 8 was not a medium node.
Strangely, applying a glass material the first time to an object, and then rendering - it works. But if you stop the render, and then try again, then the above error message comes up. Looking at the .igs file, the first instance when it works, the following appears (which is correct):
Code: Select all
<material>
<uid>7</uid>
<name>Material #27</name>
<specular>
<internal_medium_uid>8</internal_medium_uid>
<transparent>true</transparent>
<arch_glass>false</arch_glass>
<single_face>false</single_face>
</specular>
</material>
<medium>
<uid>8</uid>
<name>Material #27_Medium</name>
<precedence>5</precedence>
<basic>
<ior>1.5</ior>
<cauchy_b_coeff>0</cauchy_b_coeff>
<max_extinction_coeff>1</max_extinction_coeff>
<absorption_coefficient>
<constant>
<rgb>
<rgb>0 0 0</rgb>
<gamma>1</gamma>
</rgb>
</constant>
</absorption_coefficient>
</basic>
</medium>
Code: Select all
<material>
<uid>7</uid>
<name>Material #27</name>
<specular>
<internal_medium_uid>8</internal_medium_uid>
<transparent>true</transparent>
<arch_glass>false</arch_glass>
<single_face>false</single_face>
</specular>
</material>
Pretty miffed also (as a paid user of Indigo) that four emails explaining this problem to support@indigorenderer.com, have not been answered. As a Max user, is it worth actually my valuable time supporting a renderer of which the Max exporter always has been sub-par?