Indigo 1.1.15
- joegiampaoli
- Posts: 837
- Joined: Thu Oct 05, 2006 7:12 am
- Location: San Miguel de Allende-MEXICO
- Contact:
Some further testing, using same file of the DB preview scene packed by SmartDen in his exporter, the linux version does some bizarre things, I think it's some sort of texture displacement (look at background), not sure, also I notice there is a more noticable shadow below the linux version under the DB model.... differences below:
- Attachments
-
- Windows Version
- win.png (536.49 KiB) Viewed 6143 times
-
- Linux Version
- lin.png (528.19 KiB) Viewed 6143 times
- joegiampaoli
- Posts: 837
- Joined: Thu Oct 05, 2006 7:12 am
- Location: San Miguel de Allende-MEXICO
- Contact:
It's the same scene xml file extracted on both win-lin indigos. Ono had some issues with the linux version that didn't load textures, so he fixed it, but looks like it might still be a texture issue, maybe stretching or some faces becoming inverted?
Who knows.....
EDIT: Maybe someone can do some further tests with both engines same scene with lots of textures to see what results pop out?
EDIT2: Both ini.xml's look the same
Who knows.....
EDIT: Maybe someone can do some further tests with both engines same scene with lots of textures to see what results pop out?
EDIT2: Both ini.xml's look the same
- joegiampaoli
- Posts: 837
- Joined: Thu Oct 05, 2006 7:12 am
- Location: San Miguel de Allende-MEXICO
- Contact:
No!
I mean I think indigo for linux is treating some texture mapping different than windows, but I would like some other linux users to confirm this, now could it be your exporter? Do you think it could be part of the problem? I doubt it because look at the comparison I made before on page 3 of this topic with one of the test scenes included in indigo (Antialias Test), look at the background......all black, and there's also a black bar on the ground plane on the left side of the light emmiter.
I don't hink it's your exporter, since that scene was never exported, just opened directly.
I mean I think indigo for linux is treating some texture mapping different than windows, but I would like some other linux users to confirm this, now could it be your exporter? Do you think it could be part of the problem? I doubt it because look at the comparison I made before on page 3 of this topic with one of the test scenes included in indigo (Antialias Test), look at the background......all black, and there's also a black bar on the ground plane on the left side of the light emmiter.
I don't hink it's your exporter, since that scene was never exported, just opened directly.
Can we be more informative whenever possible, please ? For instance I compared a scene containing portal, phongs and diffuses, between 1.1.13 and 1.1.15, and found no significative performance change, pretty much the same images if you ask me (I can show that). Testing now diffuse_transparent mixed with phong at 6000x4500 and... fine.
So let's see if we can get the nasty details together instead of just complaining
So let's see if we can get the nasty details together instead of just complaining
Indigo for Linux
I'll post my experience running Indigo 1.1.15 under a 64 bit Gentoo Linux, maybe this will help someone else.
I had some problems, two of them related to my system (which I have been able to solve), and other two regarding Indigo itself (which are still pending).
1 - Indigo not starting because it could not find libtiff.so.4: I had only libtiff.so.3 (couldn't upgrade to libtiff4), solution was to link libtiff.so.4 to libtiff.so.3
2 - Indigo not starting because it could not find openmp libraries: I had gcc 4.1.2 installed which doesn't support openmp, solution was to upgrade to gcc 4.2.4 (which is marked unstable for my architecture, but till now everything seems to work ok)
3 - Indigo GUI has some controls difficult to use because they can't be selected or are partially hidden by others (see gui.jpg)
4 - Launching a network render with some slaves all with Indigo for Linux 64 bit gives an image overexposed (see network_render.jpg), while launching it only locally gives the correct exposed image (see local_render.jpg)
Apart from this small problems Indigo works very well, thank you, Ono!
I had some problems, two of them related to my system (which I have been able to solve), and other two regarding Indigo itself (which are still pending).
1 - Indigo not starting because it could not find libtiff.so.4: I had only libtiff.so.3 (couldn't upgrade to libtiff4), solution was to link libtiff.so.4 to libtiff.so.3
2 - Indigo not starting because it could not find openmp libraries: I had gcc 4.1.2 installed which doesn't support openmp, solution was to upgrade to gcc 4.2.4 (which is marked unstable for my architecture, but till now everything seems to work ok)
3 - Indigo GUI has some controls difficult to use because they can't be selected or are partially hidden by others (see gui.jpg)
4 - Launching a network render with some slaves all with Indigo for Linux 64 bit gives an image overexposed (see network_render.jpg), while launching it only locally gives the correct exposed image (see local_render.jpg)
Apart from this small problems Indigo works very well, thank you, Ono!
- Attachments
-
- gui.jpg (263.15 KiB) Viewed 5810 times
-
- network_render.jpg (44.42 KiB) Viewed 5808 times
-
- local_render.jpg (165.05 KiB) Viewed 5809 times
- joegiampaoli
- Posts: 837
- Joined: Thu Oct 05, 2006 7:12 am
- Location: San Miguel de Allende-MEXICO
- Contact:
Re: Indigo for Linux
GNUdo wrote: 4 - Launching a network render with some slaves all with Indigo for Linux 64 bit gives an image overexposed (see network_render.jpg), while launching it only locally gives the correct exposed image (see local_render.jpg)
What tone-mapping method are you using?
Who is online
Users browsing this forum: No registered users and 29 guests