Blendigo (for Blender 2.5x) 3.0.14.1

[Headroom]

@Dougal

I am wondering if there is a Windows specific Blender problem!!!

I copied the directory with the scene to my External Harddrive and took it home to test on my iMac. Subdivided meshes that seem to reliably crash Blender with using this latest Blendigo exporter on my WinXP 64 bit machine at work (Dual Xeon 20Gig of Memory) are no problem on my iMac. The exporter does not even hiccup once. Indigo rightfully complained about not finding an image texture, which had a path still pointing to a directory on my @work machine, but once I cleared that it rendered fine.

My UV maps are screwed up (which we were warned about) making for some interesting texturing effects but absolutely NO CRASHES.

I made sure that I am using the same official Blender version 2.58.1 r38019 on both machines.

[dougal2]

It could be a number of things - however, given that blender actually crashes hard, I'm suspecting there might be an issue with the windows release of blender itself.

With any luck, 2.59 (to be released really soon now) and Blendigo 3.0.14.2 should move us away from this instability.

[StompinTom]

So far no problems here... Blender 2.58 (tried two builds) + this latest Blendigo.

[Doug Armand]

Probably asking simple nooby questions here but how do I set network rendering options?

Apart from that it seems to be working OK

[dougal2]

Probably asking simple nooby questions here but how do I set network rendering options?

Apart from that it seems to be working OK

I haven't added those options yet - I'll put it on the TODO

[Doug Armand]

Probably asking simple nooby questions here but how do I set network rendering options?

Apart from that it seems to be working OK

I haven't added those options yet - I'll put it on the TODO

Great - look forward to it - also external materials don't seem to work?

[Headroom]

External Materials are working on my WinXP machine. Also I am working on a different project and the crashes I reported earlier happen less than 1 in 10 and these may be purely machine related as the thing is a bit older.

On my mac everything works fine incl. external materials.

[dougal2]

Probably asking simple nooby questions here but how do I set network rendering options?

Apart from that it seems to be working OK

I haven't added those options yet - I'll put it on the TODO

Great - look forward to it - also external materials don't seem to work?

What does "don't seem to work" mean? Getting an error message?

[dougal2]

Envmap needs absolute path now? Doesn't work with relative.

Well spotted, will be fixed in next release.

[Headroom]

Crashes continue with different scenes/files that work absolutely flawless on my mac.
2.58, 2.59, 64bit, 32bit. It all makes no difference. Blender just violently crashes on this machine.

The scenes are too big to send out. I've tried to remove things like larger image textures but then it starts working again., however these elements work fine in other scenes.

Otherwise Blendigo seems to work fine with 2.59 on the Windows machine.

Would love to test it on my mac but 2.59 crashes before it has started through. FRUSTRATING!

[Doug Armand]

What does "don't seem to work" mean? Getting an error message?

get this in Indigo when using an external material
'Error: Scene parsing error: Error while binding material 'DA_Gold0' to geometry 'Gold_Bar': No such material defined 'DA_Gold0''

The material in blender is named 'DA_Gold0' and the mesh name is 'Gold_Bar'. External material is called Gold.pigm and the material name inside is a simple phong and is just called Gold.

Using Blender 2.59 x64 and Blendigo 3.0.14.1 and Indigo 3.0.10

[Zlaty Lev]

What does "don't seem to work" mean? Getting an error message?

get this in Indigo when using an external material
'Error: Scene parsing error: Error while binding material 'DA_Gold0' to geometry 'Gold_Bar': No such material defined 'DA_Gold0''

The material in blender is named 'DA_Gold0' and the mesh name is 'Gold_Bar'. External material is called Gold.pigm and the material name inside is a simple phong and is just called Gold.

Using Blender 2.59 x64 and Blendigo 3.0.14.1 and Indigo 3.0.10

The Blender material name must be the same as the Indigo internal name.

So your internal name is "Gold" then your blender material must be named "Gold" too.

I think the way external material worked on 2.49 was better, Just my opinion.

[dougal2]

With external materials in 2.5x, Blendigo should be auto-renaming the material on export to match what's in the .igm.
There are currently a couple of assumptions made about pigm and igm files when reading the material names inside them. It's either possible that the igm does not conform to the standard naming convention, or Blendigo is doing something wrong.
Is the igm in question available for me to test here?

[CTZn]

It's either possible that the igm does not conform to the standard naming convention

This happens a lot, I think the forenamed convention should be displayed upfront to new users. Our bad.

It may have any name, but a good default name is the name of the IGM file without an .igm extension.

Yes like so please !

http://www.indigorenderer.com/forum/vie ... 01&start=0

[Doug Armand]

Is the igm in question available for me to test here?

sure but its just a simple phong