Indigo 1.1.16

[enterprise]

win 32 bit:
http://www.indigorenderer.com/dist/indigo_v1.1.16.zip

win 64 bit:
http://www.indigorenderer.com/dist/indi ... 1.1.16.zip

linux 32: (requires wxGTK 2.8 )
http://www.indigorenderer.com/dist/indi ... .16.tar.gz

linux 64: (requires wxGTK 2.8 )
http://www.indigorenderer.com/dist/indi ... .16.tar.gz

1.1.16
* nice error message instead of crash on master buffer alloc failure.
* Fixed missing tri bug for kd-tree
* fixed GUI resume not working.
* catching more memory alloc failures on init and during tonemapping.
* made network client reconnect on connection drop even with -h switch
* fixed bug where network rendering with scenes containing media did not work.

Sorry if this is a dumb question, but just want to be sure before I install this version.

I have just had my desktop computer reformatted, I am running XP, I am about to "load" it up again, I have Sketchup 6 and want to run Indigo and Skindigo. Is this version a stable version or am I best to use an earlier version?

Thanks
Philip

[Borgleader]

Its not labeled as stable but tbh Id say use this one anyway.

[enterprise]

Its not labeled as stable but tbh Id say use this one anyway.

Thanks Borg.

Am getting it now in preparation..

[Borgleader]

Its not labeled as stable but tbh Id say use this one anyway.

Thanks Borg.

Am getting it now in preparation..

Np, personnally I always get the latest version thats out. and i dont remember the last time it caused me any problems (if at all)

[enterprise]

Its not labeled as stable but tbh Id say use this one anyway.

Thanks Borg.

Am getting it now in preparation..

Np, personnally I always get the latest version thats out. and i dont remember the last time it caused me any problems (if at all)

I have now downloaded Indigo 1.1.16, Am I right in assuming that I now need Skindigo version 1.1.16 to match the version of Indigo?
if so where would I find it, I have looked everywhere but can't find it?

Thanks

[Zom-B]

I have now downloaded Indigo 1.1.16, Am I right in assuming that I now need Skindigo version 1.1.16 to match the version of Indigo?

Yes, you assume right enterprise, thats the general version idea behind the exportes!

But... since there is no exporter relevant changes from Indigo 1.1.15 to 1.1.16, Skindigo 1.1.15 should work nice too...

Keep an eye open on the Indigo changelog, so you will see in the future if a exporteris compatible to a higher Indigo version... maybe it just don't support new features or stuff, but in some cases the workflow will stay flawless

[crojack]

I have now downloaded Indigo 1.1.16, Am I right in assuming that I now need Skindigo version 1.1.16 to match the version of Indigo?
if so where would I find it, I have looked everywhere but can't find it?

Thanks

http://www.indigorenderer.com/joomla/fo ... m.php?f=17

2nd post down

[enterprise]

Thanks crojack, and ZomB for your quick replies,

Getting SK 1.1.15 now will try these out on my laptop until I get the desktop up and running again..

[Big Fan]

been trying out network rendering and I found that it will not halt on samples
I have no idea when this might have become an issue or if it is usually like this -
used my old P2.66 as a master(UImode) and new duo @3.8ghz as slave(console mode)
at predetermined samples the master recognises the halt and says its quitting but doesnt- it just keeps saying that
I would have thought it would quit the slave as well but..
here is a screenie of the ongoing quit cycle

Edit: there seems to be another issue -
with the IndigoUI when you change the white balance menu (and actually it doesnt seem to read in the .igs setting anyway but..) - in that a change permanently upsets the exposure at that point - it seems like you need to set the the master gain at 0.5 to compensate for the change but it doesnt ever reset to the loaded value internally - or thats my experience and take on it HTH

[Zom-B]

I can confirm the issue described in your screenshot... I also already reported it to Ono, hopefully its on his list

[kellpossible]

i'm having a problem with indigo 1.1.15 upwards not sure about 1.1.13 to 14 but anyway, these versions won't start on my desktop computer and give of an error (doesn't even start indigo, just gives off one of those end now errors and send information to Microsoft ones) i'm probably going to reinstall windows anyway (it's a computer i inherited so to speak!) but i was wondering whether this might be an incompatabilty with hardware or something in these versions, compared to 1.1.12 downwards (which work)... anyway, if this is too hard to answer then don't bother, i'll just report in more detail if it still doesn't work on a clean version of windows xp.

[CTZn]

SSE2 might be required for these versions, but the issue can be something else...

[kellpossible]

that's probably it!, thanks, well it's an old computer and i'm probably going to replace most of the parts soon anyway... and this is just one more reason why i should!

[SATtva_]

Here's another problem. Starting 1.1.16 on the scene (exported with Blendigo 1.1.14) I get this obscure error message:

Warning: failed to decode texture '../textures/metal/scratches_bump.jpg'.
Error: IndigoDriverExcep: SceneLoaderExcep: Failed to load texture '../textures/metal/scratches_bump.jpg' (In element 'texture', around line 75, column 13): ImFormatExcep: Error while reading JPEG file: Bogus message code %d

However 1.1.15 on the same scene with the same texture file works flawlessly (well, except for black triangles). I've attached texture file below.

Anyone else experiencing this error?

SATtva: please try opening and saving the JPEG file in another image editor, and see if Indigo gives the same error.

Ono, I'm sorry for not responding for so long. I've tested several other JPEG images from different sources, with different dimensions and compression settings, and every time Indigo stopped with the beforementioned error. I'm on Linux 64-bit version.

[SATtva_]

And to be clear that wasn't I messed something up : even Blendigo materials preview function not working because it uses JPG texture. Error message is the same.

The only solution I came to was to convert JPEG textures to PNG -- they work without a hitch.