Hello o/

Rob W. reported to me that sIBL_GUI and sIBL_GUI_XSI_Server were’nt working from his network ( Paths like : \\Server\Workgroup ).
We fixed the sIBL_GUI launcher, it should work fine now, but I don’t manage to understand why the Server addon is not working : It’s like there is nothing in the Addon when loaded from Network path :|
To be sure it wasn’t from me, I copied the XSI Workgroup Example Server onto my Network Workgroup, restarted, and it’s the same for it too : Nothing show :wacko:

Anyone encountered this already ?

Soooo...... Nobody have a clue about this????

rob

Does’nt sounds like :| That’s really annoying :[

[quote=Kel Solaar;19901]Does’nt sounds like :| That’s really annoying :[

Have you tried switching the UNC path into a shared drive?

no, and you shouldn’t… Shared drives are evil....... ;-p

rob

[quote=Rork;19915]no, and you shouldn’t… Shared drives are evil....... ;-p

Are you looking for a solution or a Holy grail?

I’m missing the ;-) at the end of the sentence......

[quote=mslaf;19908]Have you tried switching the UNC path into a shared drive?

Yeah basically I’m working with Shared Drive at home when working on Windows, it works for me, but unfortunatly pipelines are different and not the same for everybody and in every studio.
Some Windows Pipelines are working with UNC Paths, and currently it seems that XSI / DotNet don’t mix very well together at this point, even making some XSI provided features not working anymore in this case.
I think Rob and Me are looking for a solution but where UNC paths are considered in :)

KS

I’m aware of your goal but if something doesn’t work, it’s usually good to check the other solutions, just to find out where is the problem.

Using the mounted drive is always the first step. If you’re absolutely sure that XSI accepts UNC paths for plugins/workgroups then the next step would be to check the permissions on the shared folder.

Yes Mounted Drive work ( Said it above ) :)
From what I understood, Rob and his studio are working with UNC paths, and it’s working fine except for those DotNet plugins that don’t seems to load.
I’ll check at home for the permissions tihing, but currently only DotNet plugins seems to not work, Javascript, Python load correctly.

[quote=Kel Solaar;19966]Yes Mounted Drive work ( Said it above ) :)
From what I understood, Rob and his studio are working with UNC paths, and it’s working fine except for those DotNet plugins that don’t seems to load.
I’ll check at home for the permissions tihing, but currently only DotNet plugins seems to not work, Javascript, Python load correctly.

You forgot to mention about the managed code application before. The managed code requires special permissions, that allows application to be executed from the network share or a mounted drive. These are the different permissions that those applied to the network share or to the AD published resources. Ask the IT staff to do deal with it.

To test it, create a simple ‘hello world’ executable in the manage code and try to run it from the network share. If it works then, the XSI’s plugin should work as well. If the plugin won’t work, it means that it still requires additional privileges - like privilege to write to the network share etc - so the best (it terms of making things to work), would be to grant all possible privileges at start.