DEV-thread - Blendigo v0.7 - material-editor-exporter

[zuegs]

UPDATE FOR V0.7T7

Hi all, i'am just back from my easter-trip, so try to follow up all the great news here...

I published a new version of Blendigo for Indigo v0.7t7 (done by SmartDen, many thanks for your great support )

[BbB]

You guys are fast. Just trying it now. One tiny thing: If I tell the exporter to use two threads, indigo 07/7 still uses only one. No big deal as I relaunched it using a command line, but maybe sthing to look into...

[Big Fan]

edited to remove all

[jansan]

Thanks, that speed!

Gracias , que velocidad!!

[DaveC]

Zuegs, did you get round to raising the maximum exponent to >=1000000 for phong AND glossy transparent?

[dmn]

Using Blendigo, I am getting the error:

SceneLoaderExcep: The Mesh '***' tried to use the material '***', which has not been defined.

I opened up the xml and indeed the light materials have not been exported. For some reason this is only occurring with the light materials in my file. I could write them manually, and the file would work. Would be neat to have the code for each material displayed in the export window so you could copy/paste and understand what you are doing with the code, and so you can chunk it in and modify the xml if you don't want to reexport the whole thing.

[dmn]

ok, so in order to fix the xml and make it render, I had to go in and replace any 'light' material assigned to a triangle set with a "null" material. probably because the <meshlight> handles everything (explains why the light material in Blendigo is not present in the xml) and the material tag is innappropriate?

[enricocerica]

Using Blendigo, I am getting the error:

SceneLoaderExcep: The Mesh '***' tried to use the material '***', which has not been defined.

I opened up the xml and indeed the light materials have not been exported. For some reason this is only occurring with the light materials in my file. I could write them manually, and the file would work. Would be neat to have the code for each material displayed in the export window so you could copy/paste and understand what you are doing with the code, and so you can chunk it in and modify the xml if you don't want to reexport the whole thing.

I had the same problem and in my case it was due to the fact that the mesh light was part of a multi materials object. I had to separate the mesh light part using the P key in edit mode and remove any other material link in this object to get it working.

[Kram1032]

It's neither an exporter bug nor an indigo bug:
It's 'cause of the way, indigo works.
Although, it's defined as lightmat in Blendigo (ok in fact, it's defined as "light"), it's "light" in indigo. There is no possibility to da anything wit it that normal materials can:

Blending, Multimaterial (Light ALways goes over the whole shape), Alphamaping, (...) nothing like this is possible, 'cause indigo doesn't see light as material, yet.

[Pinko5]

With new Blendigo07T7 material preview don't work it search the file materialpreview.igs and not materialpreview.xml???
Pinko.

[SmartDen]

With new Blendigo07T7 material preview don't work it search the file materialpreview.igs and not materialpreview.xml???
Pinko.

That's right. You should rename it to .igs

[Pinko5]

Tnx SmartDen I try it!!
Pinko.

[zuegs]

SMALL UPDATE

- set max value for phong exponent and glossy-transparent exponent to 1000000
- finds preview scene file with new ".igs" and old ".xml" file extension

[DaveC]

Zuegs, I have a request. Yes. Me again. Ahem...

On you render settings, can you set the size dropdown to have three more options? 125%, 150%, 175% and 200%

Just a thought
Cheers. Thanks for the great exporter

[F.ip2]

Zuegs

can you also include a RGB field for values like in this thread:
http://www2.indigorenderer.com/joomla/f ... php?t=1059

I do not know which system bandar is using in the xml.

claas