3ds Max adapter error:Output path

[Anonymous]

I am rendering a drawing using backburner 2016 via 3ds Max 2016. I keep getting this error "3dsmax adapter error:Autodesk 3dsMax 18.0 reported error:Output path".

Can anyone tell me what does this mean and how to fix it

[Alfred.DeFlaminis · Accepted solution]

Hello @Anonymous,

In a general sense, it means that the location that backburner servers are trying to output frames to is invalid or they don't have permission to access it.  The most common reasons for this error are:

1) Saving to a desktop or something where C:/Users/Your User Name/...  doesn't actually exist for the render machines.  

2) The location is a network drive but only you have access, or it's a network share that isn't the same for each machine.  

3) Using a 3rd party renderer like Vray and having the Vray Frame Buffer pointed to the right place, but the "Save File" on the common tab set to an invalid location.  Some plugins may even enable the f10 Common tab File location by default.  

You could try to check the output path of your backburner file by going to the following place in the monitor.  

 

I hope this helps point you in the right direction.  Please hit the "Accept as Solution" button if my post fully solves your issue or answers your question. This lets me know that I was effective in helping you, and thank you for doing so.

Best Regards,

[Anonymous]

Thanks for that info. I am happy with the response, but how do can I change the path?

[Alfred.DeFlaminis]

Hello @Anonymous,

You can change the path by pressing F10->Common Tab->Files.  By default it's gray until a path has been entered.  If you find that is the case for you, chances are that you may be using Vray or another 3rd party renderer, in which case the path is part of the Vray Frame Buffer dialogue.  (F10-Vray Tab-Frame Buffer)  Another thing that may be happening is some of the render elements have a manually entered path that is invalid.  I have a screenshot below that is hopefully more helpful.  Please let me know if you have any other questions, I am happy to help.

[Anonymous]

That's all well and good to change the path for something that is not on the network and accessible to all machines.
But the Alternate Path is automatic, how do you change that!

[Alfred.DeFlaminis]

Hello @Anonymous and welcome to the community,

That's just your project folder.  Shouldn't stop anything from rendering or cause any problems.  You can change the project folder on the File menu, but usually not necessary.  Are you getting errors?  Which renderer are you using?  Perhaps that renderer has a custom output area (such as Vray Frame Buffer) where the path is incorrect.  Thanks for any extra information you can give me.

Best Regards,

[Anonymous]

Thanks for the reply!
I think the issue i am receiving is that 2 machines have the same user
logged in. So what happens in backburner is one pops up. Starts rendering,
gives an error then disappears from bakburner and the other machine pops up
and then errors out. Really strange. They both jave different ips and
computer names but the username and password is the same.
Either way i am unable to use both to render. Just one at a time otherwise
they conflict and neither renders.

[Alfred.DeFlaminis]

Hello @Anonymous,

Does it work when you use two different user names?  (1 on each machine?)  Are you getting any error messages in backburner?  Lastly, did you recently install the Creator's Update?  I may move these posts to a new thread as this seems maybe like a different issue than OP.  Thanks for the information.

Best Regards,

[Anonymous]

I just tried. 2 usernames still give the same issue. I am running an
install of max 2018 on half of the machines and 2016 on the other half (the
machines we are working on not the slaves) and all are working other then
these 2 conflicting...

[Alfred.DeFlaminis]

Are they all running the same version of backburner @Anonymous?  The 2016 machines are running 2018 backburner?

Best Regards,

[Anonymous]

Half the room (5 pcs) are been used by artists and are running max 2016
with the backburner installed with max 2016.
The other half of the room (6pcs) are been used by project managers or
vacant using max 2018 with the backburner installed from 2018. The Manager
is using max 2016 with the installer for max 2016

They have all been rendering fine. Just those 2 machines are having issues
out of the 12 we have...

We are using Corona to render

[Alfred.DeFlaminis]

Thanks @Anonymous.  Typically all the computers need the same version of backburner.  If your manager is BB2016 and those two computers are running BB2018, that could cause issues.  Which version of backburner are those two machines with issues using?  

Best Regards,

[Anonymous]

They both have 2018. But as mentioned. The others also have 2018 and are
working fine

[Alfred.DeFlaminis]

Hello @Anonymous,

What is the error you get?  Do they have the same mapped network drives and drive letters?  

Best Regards,

[Anonymous]

[image: Inline image 1]
It comes up with this warning and then it drops. Whichever of the 2 was
turned on first happens to be the one that has the error when the second
comes on.​​

[Alfred.DeFlaminis]

Hello @Anonymous,

For some reason your image didn't take.  Can you please re-attach?  Thanks!

Best Regards,

[Anonymous]

In our case the mapped network drive wasnt labeled with the same letter across all servers. Once they were remapped with the same letter the errors stopped. Is it possible to specify a UNC path to avoid this issue?

[Alfred.DeFlaminis]

Hello @Anonymous and welcome to the community,

Yes, open the Asset Tracker and right click on the texture names and click "Resolve Paths to UNC location".  I have a screenshot below.  It's grayed out because the texture wasn't on a mapped network drive, but if yours is it won't be.  Can you please try that for me?  If you want we can start a new thread so we're not hammering Matt's 

Best Regards,

[Anonymous]

thank you sir . you solved my problem