Blendigo (for Blender 2.5x) 3.2.0.0

[dougal2]

No light sources available when only using envmap.

I can't reproduce this here, it seems to work correctly. Can you provide a .blend file of your setup for me to test?

[dag]

Looks like only files in C:\Users\... doesn't work. Try putting it in there.
Windows UAC enabled if that matters.

[dougal2]

Looks like only files in C:\Users\... doesn't work. Try putting it in there.
Windows UAC enabled if that matters.

Still works for me with a .exr in "My Documents" and UAC on (win 7 x64)

[dag]

This one works but only when files are in 2 folders below the documents folder.
In any other user folders no light sources.

[dougal2]

This one works but only when files are in 2 folders below the documents folder.
In any other user folders no light sources.

OK, I've seen the problem now, but not sure what's causing it yet. I think it might have something to do with the output path being "/tmp\" with the .blend file on the C:

I didn't spot this before, since my testing .blend files are normally on my D: data disk.
(I also normally set my output path to either "//" or "d:\Temp").

I'll see what I can do to prevent problems with .blend on C: and "/tmp\"

[dougal2]

This one works but only when files are in 2 folders below the documents folder.
In any other user folders no light sources.

OK, I've seen the problem now, but not sure what's causing it yet. I think it might have something to do with the output path being "/tmp\" with the .blend file on the C:

I didn't spot this before, since my testing .blend files are normally on my D: data disk.
(I also normally set my output path to either "//" or "d:\Temp").

I'll see what I can do to prevent problems with .blend on C: and "/tmp\"

This issue was to do with incorrectly set working directories during export and therefore incorrectly resolved relative paths - it'll be fixed in the next release

[StompinTom]

This one works but only when files are in 2 folders below the documents folder.
In any other user folders no light sources.

OK, I've seen the problem now, but not sure what's causing it yet. I think it might have something to do with the output path being "/tmp\" with the .blend file on the C:

I didn't spot this before, since my testing .blend files are normally on my D: data disk.
(I also normally set my output path to either "//" or "d:\Temp").

I'll see what I can do to prevent problems with .blend on C: and "/tmp\"

This issue was to do with incorrectly set working directories during export and therefore incorrectly resolved relative paths - it'll be fixed in the next release

Eagerly waiting for next release! Do you think the 'proxy'/igmesh linking will be faster too?

[dougal2]

Eagerly waiting for next release! Do you think the 'proxy'/igmesh linking will be faster too?

Yes, I've removed the igmesh loading and will assume the proxy object has the same number of materials assigned as the igmesh. I've also added support for obj format meshes.

[StompinTom]

Eagerly waiting for next release! Do you think the 'proxy'/igmesh linking will be faster too?

Yes, I've removed the igmesh loading and will assume the proxy object has the same number of materials assigned as the igmesh. I've also added support for obj format meshes.

Amazing! Can't wait to throw geometry at Indigo quicker than ever.

[FakeShamus]

Eagerly waiting for next release! Do you think the 'proxy'/igmesh linking will be faster too?

Yes, I've removed the igmesh loading and will assume the proxy object has the same number of materials assigned as the igmesh. I've also added support for obj format meshes.

awesome! this will kind of change my life - thanks!

[solarray]

No one has problems with uv mapping ? Mine are totally distorted with this exporter and blender 2.60a/2.58a. The old exporter 3.0.10 works fine.

[StompinTom]

No one has problems with uv mapping ? Mine are totally distorted with this exporter and blender 2.60a/2.58a. The old exporter 3.0.10 works fine.

Now that you mention it, so am I... UVs are very messed up :S

[FakeShamus]

Yes, I have very distorted textures for all UV mapping too.

[dougal2]

I do confirm that non-trivial UV mapping is screwed. I'll try and fix it today

[dougal2]

I have a fix