Indigo Renderer Forum

Hey there,
I wondered if it is possible to reference an external PIGS, like an external IGS.
I prepared the IGS with deleting render-, camera- and environment settings, changed <scene> to <scenedata> and packed that file.
Will that work?
Thanks in advance!!


Gesendet von iPhone mit Tapatalk

I always giggle when I think how new users react to topics like this. External PIGS??? Is this some kind of animal rights movement or what?

To get back on topic - have you tried if it works?

Hehe!
No, it doesn't work. It would be very handy for easy asset exchange over non-uniform-name-mapped network drives etc...

zeitmeister wrote:Hehe!
No, it doesn't work. It would be very handy for easy asset exchange over non-uniform-name-mapped network drives etc...

If it is handy it will be done, we have some great techs!

I have something like that.

It is just a tiny software who remove the header, camera, settings, and add <scenedata>....</scenedata>

I ask to my team if we can share it, but honestly it's not a "big" stuff.

Earlier, I have recommanded to save as "include" and use a layer managment directly in the Indigo software but unfortunatly this is not in the goals of Glare technology.

Hey jay, we have such a nifty little Tool too!
But it would be great if the devs could simply implement that... shouldn't be a big deal.


Gesendet von iPhone mit Tapatalk

I am totally agree!

Even for the lighting condition, such as materials, obtain the possibility to "save as" should be awesome.

Long time request... and very easy to implement and read for the exporters, too.


Gesendet von iPhone mit Tapatalk

Hi,
I could make the <include> tag be able to reference .PIGS files directly, is that what you mean?
I don't really see why that would be helpful. To load PIGS files Indigo just unpacks the file to a temp location anyway.

OnoSendai wrote:Hi,
I could make the <include> tag be able to reference .PIGS files directly, is that what you mean?
I don't really see why that would be helpful. To load PIGS files Indigo just unpacks the file to a temp location anyway.

Indeed, but all textures do have the correct filepath on every machine which unpacks it.
I'm a little bit on network usability here: a pigs can easily be used on many machines in a network, even if the network drive name mappings differ. Absolutely hastle-free for non-distributed network rendering.


Gesendet von iPhone mit Tapatalk

Ok added support for this for the next build.
It will just load the first .igs found in the PIGS file.

If you have settings and background material and camera in the sub-PIGS file, what's happens exactly?

If i understand well, if you have a master PIGS, wiht an IGS, including a sub-PIGS then Indigo take the first igs of this sub-PIGS and avoid all settings/camera/background materials info.

What's happens to the UIDs in that such a case? Especially for emitting materials/model2 or IES files integration?

It behaves pretty much like if you extracted the contents of the PIGS file manually, then linked to the first IGS yourself.
Note that the ordering of the extracted files is somewhat arbitrary, so it will be best to just have one IGS file packed in each PIGS.

oh!
So in case when render an animation (1 PIGS with lot of .IGS with <scene> full of includes) may have some trouble?

To my knowledge, actually the order is define by the sens of reading of the "mainscene igs", top to the bottom.
The first include's line take 1000000 + UIDs, the second 2000000 + UIDs etc.. so it is not so arbitrary.

Because the actual workflow with a "mainscene" then full igs for scene construction is something that very usefull. The only triks is to place the include with the "luminous materials/model2" somewhere where the UIDs don't change, or use the "offset_uids"...

(Notice that there is troubles in the Indigo4Max exporter and new PISG generation from an correct PIGS here)

Why not use PIGQ?