Indigo Renderer Forum

Posted: **Thu Jul 10, 2008 8:42 pm**

Indigo 1.0.9

Master : Ubuntu

Computer name : lo-desktop
Sharing rep on master : indigo_render

Slave : Xp

computer name : xp_ordi

On my master trying :

wine indigo_console.exe //lo-desktop/render_indigo/test_cube1.igs -n m

And i have got this problem message :

Indigo Renderer v1.0.9, Windows 32-bit Release build.
Failed to open scene file '//lo-desktop/render_indigo/test_cube1.igs' for reading.
Fatal Error: Failed to open scene file '//lo-desktop/render_indigo/test_cube1.igs' for reading.

I think it's a network problem.

Posted: **Thu Jul 10, 2008 11:57 pm**

I got the same thing when I tried it last week although I was using XP on my desktop and Vista on my laptop. I might give it another go now that I have Vista on both....maybe magic will happen.

Posted: **Fri Jul 11, 2008 12:57 am**

I'm haven't any clue about Linux, but after 1001 successful Windows based network rendering approaches I can say that for least @ a windows system the port you want to connect is important too (maybe for wine too!?)!

Master

Code: Select all

cd indigo_v1.1.5

START /B /LOW indigo.exe \\hauptrechner\netrender\netrender.igs -n wm -p 7777

Slave

Code: Select all

cd indigo_v1.1.5

START /B /BELOWNORMAL indigo_console.exe \\hauptrechner\netrender\netrender.igs -n s -h hauptrechner:7777

wm my the way starts a master that also do rendering

Posted: **Fri Jul 11, 2008 1:30 am**

Nah port isn't important if you don't define it.

The problem is that UNC paths aren't supported in a command line.

Mount that \\lo-desktop\ directory manually to something like /mnt/indigo-render/ and then pass /mnt/indigo-render/default.igs to wine'd indigo (there's a Linux release of v1.0.9 btw)

Posted: **Fri Jul 11, 2008 5:02 am**

Only x64 for linux for 1.0.9_3 indigo render... i used x32 here ;(

i do what you say, all is ok... but can't connect from windows xp, problem reading...

Posted: **Fri Jul 11, 2008 11:06 am**

?

So now your xp machine can't see the exact same file that was working before?

Maybe try copying the .igs and all related textures to both sides locally and forget the UNC path.

Posted: **Fri Jul 11, 2008 7:21 pm**

zsouthboy wrote:?

So now your xp machine can't see the exact same file that was working before?

Maybe try copying the .igs and all related textures to both sides locally and forget the UNC path.

Can't find my share rep on windows xp console...

SO i tried a linux version and then another problem :

Code: Select all

lo@lo-desktop:~/telechargement/indigo_linux_v1.0.9_2$ ./indigo_console /mnt/render_indigo/test_cube1.igs -n m  
Indigo Renderer v1.0.9, Linux 32-bit Release build.
Starting server on port 7777...
Using base Indigo directory path '.'.
Scene file path: '/mnt/render_indigo/test_cube1.igs'
Using working directory path '/mnt/render_indigo'.
Loading Scene '/mnt/render_indigo/test_cube1.igs'...
Using Reinhard tone mapping with pre_scale=4.000000, post_scale=1.200000, burn=6.000000
Instruction illégale (core dumped)

Posted: **Sat Jul 12, 2008 12:03 am**

ok... then i succed some stuff..

1 - I made my share rep on my ubuntu, with my igs_file.igs for me :

/home/lo/telechargement/render_indigo ( right clik and share..)

2 - I mount acces to this rep

first a little test

Code: Select all

:~$ smbclient -L lo-desktop
Password: 
Domain=[LO-DESKTOP] OS=[Unix] Server=[Samba 3.0.26a]

        Sharename       Type      Comment
        ---------       ----      -------
        print$          Disk      Printer Drivers
        iP4300          Printer   Canon iP4300
        render_indigo   Disk      
        IPC$            IPC       IPC Service (lo-desktop server (Samba, Ubuntu))
Domain=[LO-DESKTOP] OS=[Unix] Server=[Samba 3.0.26a]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        LORESEAU             LO-DESKTOP

then mount on mnt my share rep with root access :

Code: Select all

~# smbmount //lo-desktop/render_indigo /mnt/render_indigo -o username=lo
Password:

Then run indigo with indigo_console :

the master (on console on my ubuntu) :

Code: Select all

 wine indigo_console.exe  /mnt/render_indigo/test_cube1.igs -n m

the slave (on console on my ubuntu to run first render machin) :

Code: Select all

 wine indigo_console.exe /render_indigo/test_cube1.igs -n s -h lo-desktop:7777

Then i tried to run a slave render to my windows xp on my network.

First : made windows access to my share rep on a dos console windows

i used net start :

Code: Select all

net start t: \\192.168.0.11 \render_indigo Password /user:lo

then when i made cd t: on my dos console and make dir, i see the list of my render_indigo rep with my test_cube1.igs

Then i have acces to my test_cube1.igs file and can edit it ( edit t: test_cube1.igs is ok), but when i tried :

Code: Select all

indigo_console.exe t:test_cube1.igs -n s -h lo-desktop:7777

connected to master ok then
ive got an error message, can't reading test_cube1.igs

what the problem here ?

Posted: **Wed Jul 23, 2008 2:07 am**

I still have to physically copy the igs and any associated files (images, exr's etc) to the same place on each networked machine eg. c:\indigo\workingdir\

Try this it worked for me. I don't notice the bother now I just do it.

Indigo Renderer Forum

Trying Network rendering ... many problem

Trying Network rendering ... many problem