9.2 and network paths for Content Directories

[Sondar9]

Is anyone else having an issue using 9.2 with network paths for the content directory?
Whenever Lightwave 9.2 loads, I get the error "The Output directory specified does not exist. Select alternate now?" whenever I use a network path for the content directory.
If i use a local folder, I don't get the error. If I use any type of network path either mapped drive letter or unc path, I get the error.
At first it seemed like a minor nuisance since I can still render locally no matter where the content is. It remembers wherever I set the content directory when I use the edit menu. The problem is when I network render. 9.0 doesn't give me this error, and the same scene renders fine over the network with 9.0.

[stib]

Yep, me too. Perhaps post it as a bug.

[Silkrooster]

Do you have a folder called images in your content directory?
Silk

[stib]

I don't render to my content directory. I have a separate network drive with all my animation media (including After effects and combustion renders etc) that I call Renders.

[Silkrooster]

Try Edit>Path Options... At very bottom is Output directory, try setting that to your renders folder and see if that takes care of your error.
Silk

[stib]

yeah, that's where I've been setting the path. He no worky. He very broken.

[Sondar9]

Thanks for the replies, I thought I was going crazy.
I reported that bug a couple of weeks ago. I was just wondering if anyone else was having the same problem.
Silk rooster, I tried the edit paths option too, it still didn't work. It sounds like you're not having this problem, am I right? If so it might be a configuration issue. Are you running lightwave on a Mac or Windows box?
I'm running on a PC (IWILL ZMAXDP) with windows xp pro. The content folder is on a Linux/Samba Server.
Hopefully Newtek will fix this problem soon. I just started on a new project, and I really need to use all of my machines. I'm too spoiled to go back to 9.0 :)

[HanJobSoSlow]

same here

[Silkrooster]

Thanks for the replies, I thought I was going crazy.
I reported that bug a couple of weeks ago. I was just wondering if anyone else was having the same problem.
Silk rooster, I tried the edit paths option too, it still didn't work. It sounds like you're not having this problem, am I right? If so it might be a configuration issue. Are you running lightwave on a Mac or Windows box?
I'm running on a PC (IWILL ZMAXDP) with windows xp pro. The content folder is on a Linux/Samba Server.
Hopefully Newtek will fix this problem soon. I just started on a new project, and I really need to use all of my machines. I'm too spoiled to go back to 9.0 :)
To be honest with you I have not had to use screamernet in awhile. So it still could be a bug issue. If I recall setting up before I had to specify the directory via the network path, not an absolute directory path.
This may depend on whether you are using mapped drives or following Matt's tutorial on setting up screamernet.
Silk

[svintaj]

Is anyone else having an issue using 9.2 with network paths for the content directory?
Whenever Lightwave 9.2 loads, I get the error "[B]The Output directory specified does not exist.
Yes I also have this problem! :bangwall:
The chosen save dir is ignored when I'm trying to net-render, and sometimes even when using F10.
/ Svante

[svintaj]

I found a workaround, to be able to render with ScreamerNet.

Open the scene file in notepad and locate the string:
"SaveRGBImagesPrefix"

It should be set to something like:
SaveRGBImagesPrefix P:\MyFolder\MyPicure

Just change it to:
SaveRGBImagesPrefix P:\\MyFolder\MyPicure

Do this before you add the scene to the ScreamerNet list.
It works for me right now! :)

/ Svante

[stib]

Have you posted this solution to the bug fixers? Seems like there a very simple bug that is causing it to add one slash too few.

[Sondar9]

Svante,

Thanks for the fix. You're a lifesaver!

-Rich

[Sondar9]

stib,

I'm not sure how to post the solution to the bug fixers. The last time I tried to edit this bug, I couldn't, I just ended up posting it a second time. I guess I'll just do that again. And, other people can post it too, that way it might get more attention and get fixed sooner!

-Rich

[Sondar9]

Just found out there's a new open beta program for 9.2 patch realease 1.
I think they fixed this bug. I'll try it out tomorrow.

-Rich

[tektonik]

svintaj trick didn't work for me...



I found a workaround, to be able to render with ScreamerNet.

Open the scene file in notepad and locate the string:
"SaveRGBImagesPrefix"

It should be set to something like:
SaveRGBImagesPrefix P:\MyFolder\MyPicure

Just change it to:
SaveRGBImagesPrefix P:\\MyFolder\MyPicure

Do this before you add the scene to the ScreamerNet list.
It works for me right now! :)

/ Svante

[StevenDS]

I'm seeing this problem also. It seems that in Layout there are TWO places you can set output paths for your renders. I understand that you should point to the folder you are saving to via Network Places - Entire Network - etc...

Is having two spots for the destination of the renders choking the network renderer?

[BloodQuest]

I posted this in the 9.2 Discussion section the other day...

Here's a temporary solution for anyone getting bugged to death by the Warning dialog:

The Output directory specified does not exist. Select alternate now?

1. You need to check (tick) "Use custom paths"

2. Select the save path

3. Quit LightWave

4. Open your LW9.cfg file in a text editor.

5. Find the OutputDirectory entry (line 4) and ADD A BACKSLASH

This works whether you want to use a directory or a seperate drive.

If, for example, your Content Directory is N:\Content, the following would all work.

OutputDirectory N:\Content\Images\

OutputDirectory N:\Content\Renders\

OutputDirectory R:\\

The last one is for using a different drive.

Simon

[StevenDS]

Thanks for that!

I got the network renderer to save the renders strictly by text editing the layout file.

We should'nt have to be editing the layout files to get network rendering to work.

*cough* I hope this gets fixed in the 9.2 PR1 Open Beta. *cough*

[stib]

seems to be sorted in build 1193.

[StevenDS]

I wasn't sure we could talk here about the Betas, but, I've tried network rendering with 1193 and had the same problems with the network renderer refusing to save any renders from any render-nodes, unless I edit the Layout file just prior to running the Network Render Layout as suggested by BloodQuest. Though the only thing I change/edit is the OutputDirectory in the layout file. I don't doubt others success with 1193 ScreamerNet. I will keep trying.

[BloodQuest]

Set paths as before then quit out of Layout.

Now go to your LW9.cfg config file and change this:

AutoDirectoryUpdate 1

to this:

AutoDirectoryUpdate 0

Should sort you out!

Simon

[pva]

This is happening to me with the 9.3 version, any fix for this?