Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] I need help! => Topic started by: mraw on 2016-05-08, 21:06:39

Title: mapping drive failed
Post by: mraw on 2016-05-08, 21:06:39
I'm doing something wrong with the drive mapping- I usually work with UNC paths only, so this is the first time I used the drive mapping. So probably I'm doing something really stupid.
The rendernode doesn't find the assets in DR rendering, although I mapped the network drive.
This is how the mapped drive looks like in the windows explorer:
v(\\Computername)(V:)
as you already guessed I'm trying to map the V: drive. Does this look correct to you?
thanks in advance....


PS: Excuse me for posting this here, because it is not exactly Corona related.Feel free to move or kick this thread.
Title: Re: mapping drive failed
Post by: Juraj on 2016-05-08, 21:52:33
Did you map the drive on the render node as well ? If so the path should simply look like this only "V:\.."

To me it looks like you're trying to reach directly network path (with mapped drive there perhaps, but that doesn't matter).
Title: Re: mapping drive failed
Post by: maru on 2016-05-09, 14:55:34
Does the node see V:? Even in the windows explorer.
Title: Re: mapping drive failed
Post by: mraw on 2016-05-09, 23:24:39
thanks guys for getting back to me. Greatly appreciated.
Juraj, excuse me, but I don't understand. But I'm sure that's why it is not working.
What do you mean by 'map the drive on the render node as well'?
I mapped it only there.
Maru: Yes, the nodes has the mapped drive. If I unfold 'Computer' the mapped V-drive is there and not
under 'network'.
It says v(\\Computername)(V:), but If I click, copy and paste the address line of the Windows explorer I got: 'V:\'
So the Render node think it has a local V: drive.  This is how it is supposed to be?
Wrong thinking?
Title: Re: mapping drive failed
Post by: Juraj on 2016-05-10, 00:12:01
When you open 3dsMax on your node (directly or through remote access), and open material browser, click on any material (even empty, on new scene), and click bitmap loader, can you see the mapped network drive ?

Depending on your Windows, 3dsMax could possibly have elevation rights issues with network drives, if you run 3dsMax in elevated mode ("run as admin"). There is easy registry solution to this, but this is just shot in dark, it's probably something much easier.
Title: Re: mapping drive failed
Post by: mraw on 2016-05-10, 23:05:51
Yes, I can. It takes Max/(windows?) a strange long time(like 20,30 seconds) to connect, but afterwards I am able to apply a bitmap from the mapped V:drive.
I turned off UAC on this node and a look in my user account tells me that I am admin.

The strange thing is that the node starts to render- the max scene is on the V:drive as well! I don't understand why it is able to load the maxscene, but can't reach the assets(textures, alembics etc.)

Title: Re: mapping drive failed
Post by: mraw on 2016-05-10, 23:13:11
So Corona will always connect the clients through UNC? The node loads the scene from networkpath and the fails to load the mapped drive paths.

I have another node with an identical data set on its local V:drive. This one works. It is a matter of disk space why I want the other node to load assets through network/mapped drive.
Title: Re: mapping drive failed
Post by: Juraj on 2016-05-10, 23:28:37
Yes, I can. It takes Max/(windows?) a strange long time(like 20,30 seconds)

Looks like some network issue.. sorry, not good in diagnosing these things, can always be so many culprits behind.

What happens when you open that scene on the node ? Does it also fail to reach assets ? Or does it take simply much longer to open ? If the latter, it could be some time-out issue on Corona's DR because of network issue. If the former, the issue is your setup.
Title: Re: mapping drive failed
Post by: rambambulli on 2016-05-11, 12:36:17
I have the same problem. In my case it is/was a right problem I guess. Somehow the 3ds max command line hasn't got the rights to open the links.When a node has all administrator rights it works. This works for me but I don't know if this is the proper solution.
Title: Re: mapping drive failed
Post by: mraw on 2016-05-11, 14:16:03
although my user-account calls me 'Admin', I still have to rightclick-'run as admin' the DrServer.
So I guess it is not true what my user-account says. I will have a another look in the evening.
Thanks guys.
Title: Re: mapping drive failed
Post by: Juraj on 2016-05-11, 14:36:50
although my user-account calls me 'Admin', I still have to rightclick-'run as admin' the DrServer.
So I guess it is not true what my user-account says. I will have a another look in the evening.
Thanks guys.

Are you running 1.3 or latest daily ? Either of this solved this DR behavior. It should now always run elevated I believe.

Otherwise that is default Windows behaviour, being admin doesn't by default run stuff in elevation. Which on 8/10 caused issues with 3dsMax not seeing network paths because file explorer is elevated. This can be solved by simple registry addition('EnableLinkedConnections' DWORD=1)
Title: Re: mapping drive failed
Post by: maru on 2016-05-11, 15:02:48
Yes, if it's any post-1.3 Corona version then there is no need to run in admin mode, if it's 1.3. then the following fixes can be applied: https://coronarenderer.freshdesk.com/support/solutions/articles/12000002048
Title: Re: mapping drive failed
Post by: mraw on 2016-05-11, 21:20:59
I'm on 1.3. Sorry, I didn't know about that issue. It's working now.
thanks a million, guys